Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.39 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 23 Aug 2012 09:01:17 -0700
Subject: Re: Getting Mustella to work.
Thread-Topic: Getting Mustella to work.
Thread-Index: Ac2BR7+MoIb6bEmwTeOVwKN7BvciJQAAMeuG
Message-ID: <CC5BA1DD.4515B%aharui@adobe.com>
In-Reply-To: <CC5BC966.1FB6%pent@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

It might be better to figure out how to quote those entries.  Why was it
hard to do that as the command line gets built up?


On 8/23/12 8:55 AM, "Peter Ent" <pent@adobe.com> wrote:

> Certainly appreciate the help. Here's a typical one when running Mustella=
:
>=20
> -debug -define=3DCONFIG::skaha,false
> -compiler.fonts.managers=3Dflash.fonts.JREFontManager,flash.fonts.AFEFont=
Mana
> ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
> -source-path=3D/Users/pent/apache/flex/mustella/Assets
> -includes=3DExcludeFileLocation -includes=3DSetShowRTE
> -includes=3DSaveBitmapFailures
> -includes=3Ddatagrid_properties_lockedColumnCount_mxml
> -source-path=3D/Users/pent/apache/flex/mustella/tests/components/DataGrid=
/Dat
> aGrid_SparkSkin/Properties --allow-source-path-overlap=3Dtrue
> -includes=3DSendResultsToRunner  -includes=3DExitWhenDone -source-path=3D=
.
> -source-path=3D/Users/pent/apache/flex/mustella/../frameworks/
> -source-path=3D/Users/pent/apache/flex/mustella/as3/src/mustella
>=20
> Try changing my path, "/Users/pent/apache/" to something like
> "/Users/pent/apache with spaces/" to get a better example.
>=20
> What happens in the code is that groups of these options may be coming
> from the environment, so you might find "-debug
> -define=3DCONFIG::skaha,false" being added as a single entity. Then code
> turns what it has at the moment into a String[] and passes that to anothe=
r
> function that might add more arguments. If that function does, it will
> turn the String[] back into a String, add the arguments, then turn it bac=
k
> into String[]. =20
>=20
> But if you can make something that will convert the args into an
> acceptable String[] it would be super-helpful.
>=20
> Thanks!
> --peter
>=20
> On 8/23/12 11:44 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>
> wrote:
>=20
>> String.split(regexpattern)  can match pretty much anything.  Definitely
>> would be able to comeup with a pattern to match embedded dashes.
>>=20
>> I'll see if I can come up with something that can properly strip down a
>> completed command with arguments.  If you would give me a more complex
>> command line that would be great.  I can test against it.
>>=20
>> Currently my setup uses few command line arguments and instead adds to
>> the "-load-config+=3Dmycustomconfig.xml"
>>=20
>> -----Original Message-----
>> From: Peter Ent [mailto:pent@adobe.com]
>> Sent: Thursday, August 23, 2012 10:52
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Getting Mustella to work.
>>=20
>> I tried something like that, but there are options like: -source-path=3D
>> with a hyphen in the option and a couple that begin with double hyphens.
>> I started to switch over to String.split(" -") to break apart on the
>> space+dash but then ran into this mysterious problem of mxmlc not liking
>> the arguments it was given, even though, as far as I can tell, it was
>> getting the same ones in the same order. Obviously that wasn't the case,
>> but had trouble tracking it down, so it is on hold for now while we get
>> the tests to run, unless someone else wants to take a stab at it.
>>=20
>> --peter
>>=20
>> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>
>> wrote:
>>=20
>>> I'm not sure what Mustella is written in, but would something generic
>>> like this work?
>>>=20
>>> If a string needs to be turned into an array then maybe... Use the "-"
>>> as the first delimiter to break apart the options and use a temp array.
>>> Then use the "=3D" to break out the names from the values.
>>>=20
>>> Keeping two arrays with the same number of elements.  One array stores
>>> the argument name and the second argument value.
>>>=20
>>> //Declare arrays/string
>>> string [] saNames =3D {"Option1", "Option2", "Option3"}; string []
>>> saValues =3D {"My value with spaces", "test2", "test 3"}; string
>>> sCombinedOptions =3D "";
>>>=20
>>> //Loop through all elements in arrays
>>> for (;;)
>>> {
>>>   //Combine names / values.
>>>   sCombinedOptions +=3D saNames[currentItem] + "=3D""" +
>>> saValues[currentItem] + """ "; }
>>>=20
>>>=20
>>> //Add the command line and options.
>>> "path\mxmlc.exe" + " " + sCombinedOptions;
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: Peter Ent [mailto:pent@adobe.com]
>>> Sent: Thursday, August 23, 2012 9:33
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: Getting Mustella to work.
>>>=20
>>> That ought to work, but does not. The Mustella code pieces together a
>>> large string with all of the options on it, then turns the string into
>>> a String[] by using space as the delimiter. Thus
>>>=20
>>> -source-path=3D"C:\Program Files\Common Files\Microsoft
>>> Shared\MSInfo\MSInfo32.exe"
>>>=20
>>> turns into
>>> [] =3D -source-path=3D"C:\Program Files\Common [] =3D Files\Microsoft [=
] =3D
>>> Shared\MSInfo\MSInfo32.exe"
>>>=20
>>> And it does this several times (turning the array into a string,
>>> inserting other args, back to an array) to build up the argument list.
>>> Ultimately, the array of options is passed over to mxmlc to execute, so
>>> it does need to turn into an array of options. I was working on putting
>>> everything into an ArrayList but more and more code needed to change
>>> and then I was getting errors from mxmlc saying parameters were being
>>> mixed which I didn't understand since it was getting the same
>>> parameters in the same order.
>>>=20
>>> So I have to re-think the approach.
>>>=20
>>> --peter
>>>=20
>>> On 8/23/12 6:59 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>
>>> wrote:
>>>=20
>>>> I know this may sound silly, but windows deals with the spaces in path
>>>> using quotes around the whole path.  Is there something similar with
>>>> Mustella?
>>>>=20
>>>> So a windows command prompt example, I could do something like the
>>>> following...
>>>> "C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>>=20
>>>>=20
>>>> Whereas the old non spaced dos style naming convention would do this
>>>> without quotes..
>>>> c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>>=20
>>>>=20
>>>> r/s
>>>> -Mark
>>>>=20
>>>> -----Original Message-----
>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>> Sent: Wednesday, August 22, 2012 9:20
>>>> To: flex-dev@incubator.apache.org
>>>> Subject: Re: Getting Mustella to work.
>>>>=20
>>>> I have not have luck solving the problem. It is much trickier than I
>>>> anticipated. I am going to jump back into getting more tests to run
>>>> and think more about the problem. Operating systems have allowed
>>>> spaces in file names for many, many years and you'd think would be an
>>>> easily solvable problem (or not even a problem at all).
>>>>=20
>>>> --peter
>>>>=20
>>>> On 8/21/12 11:12 PM, "Justin Mclean" <justin@classsoftware.com> wrote:
>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> If the space path issue was fixed you have more to add. Any luck with
>>>>> that yet?
>>>>>=20
>>>>> Justin
>>>>=20
>>>=20
>>=20
>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui