I'll try and look at it today. I'm in the middle of figuring out why some bitmaps aren't showing up in the tests.
Thanks! --peter On 8/27/12 2:09 PM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> wrote: >Gonna play a game of see if the exchange server strips my attachments... >----- >Ok I've worked on it a bit here and there. I rolled it up to a class to >make it easier to implement. By far the regex was the longest pieces. >For those who want to know, the Regex in actioscript is the same flavor >as javascript. Can use this website to fiddle with it without having to >complile http://jsfiddle.net/ > > > >//Create an instance of the class. >var oArgs:ArgManage = new ArgManage(); > >//Toss in the argument string. >oArgs.StringArugments = sMyExistingArgumentsString; > > >//Run any of the stock functions to add/update/remove arguments. >//The AddStaticArg is for strange things like "-debug" having no value >assignment. >public function AddArg(sName:String, sValue:String):void; >public function AddStaticArg(sName:String):void; >public function RemoveArg(sName:String):void; >public function UpdateArg(sName:String, sValue:String):Boolean; > >//Get your new combined string back out. >sMyExistingArgumentsString = oArgs.StringArugments; > > >Possible things left to do: >-Change arraylists to vectors. >-Take a little redundancy out of the code. >-Change variable/function naming convention to some actionscript standard. >- > >-----Original Message----- >From: Peter Ent [mailto:p...@adobe.com] >Sent: Monday, August 27, 2012 13:30 >To: flex-dev@incubator.apache.org >Subject: Re: Getting Mustella to work. > >Sure, I can work it in and give it a try. > >Thanks. >--peter > >On 8/27/12 1:26 PM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> >wrote: > >>Peter, did you want to test the argument handler test code today? >> >>-----Original Message----- >>From: Peter Ent [mailto:p...@adobe.com] >>Sent: Thursday, August 23, 2012 11:56 >>To: flex-dev@incubator.apache.org >>Subject: Re: Getting Mustella to work. >> >>Certainly appreciate the help. Here's a typical one when running >>Mustella: >> >>-debug -define=CONFIG::skaha,false >>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont >>Man >>a >>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager >>-source-path=/Users/pent/apache/flex/mustella/Assets >>-includes=ExcludeFileLocation -includes=SetShowRTE >>-includes=SaveBitmapFailures >>-includes=datagrid_properties_lockedColumnCount_mxml >>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid >>/Da >>t >>aGrid_SparkSkin/Properties --allow-source-path-overlap=true >>-includes=SendResultsToRunner -includes=ExitWhenDone -source-path=. >>-source-path=/Users/pent/apache/flex/mustella/../frameworks/ >>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella >> >>Try changing my path, "/Users/pent/apache/" to something like >>"/Users/pent/apache with spaces/" to get a better example. >> >>What happens in the code is that groups of these options may be coming >>from the environment, so you might find "-debug >>-define=CONFIG::skaha,false" being added as a single entity. Then code >>turns what it has at the moment into a String[] and passes that to >>another 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 back into String[]. >> >>But if you can make something that will convert the args into an >>acceptable String[] it would be super-helpful. >> >>Thanks! >>--peter
