flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Getting Mustella to work.
Date Thu, 23 Aug 2012 15:54:53 GMT
I don’t think the attachments came through.

On 8/23/12 8:11 AM, "Carlos Rovira" <carlos.rovira@codeoscopic.com> wrote:


how could we do when images differ like in the attached screenshot?

The created image differs from the one that is rendered what is really weird...

2012/8/23 Peter Ent <pent@adobe.com>
I tried something like that, but there are options like: -source-path=
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.


On 8/23/12 10:43 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>

>I'm not sure what Mustella is written in, but would something generic
>like this work?
>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 "=" to break out the names from the values.
>Keeping two arrays with the same number of elements.  One array stores
>the argument name and the second argument value.
>//Declare arrays/string
>string [] saNames = {"Option1", "Option2", "Option3"};
>string [] saValues = {"My value with spaces", "test2", "test 3"};
>string sCombinedOptions = "";
>//Loop through all elements in arrays
>for (;;)
>   //Combine names / values.
>   sCombinedOptions += saNames[currentItem] + "=""" +
>saValues[currentItem] + """ ";
>//Add the command line and options.
>"path\mxmlc.exe" + " " + sCombinedOptions;
>-----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.
>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
>-source-path="C:\Program Files\Common Files\Microsoft
>turns into
>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>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.
>So I have to re-think the approach.
>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>
>>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
>>So a windows command prompt example, I could do something like the
>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>Whereas the old non spaced dos style naming convention would do this
>>without quotes..
>>-----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.
>>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).
>>On 8/21/12 11:12 PM, "Justin Mclean" <justin@classsoftware.com> wrote:
>>>If the space path issue was fixed you have more to add. Any luck with
>>>that yet?

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message