Re: [Asunit-users] Providing library assets

[Octavian C. <oct...@gm...>]

On 10/25/07, Boysenberry Payne <boy...@ha...> wrote:
>
> I'm using Flash 9 and AS3 so I could try writing slick document classes
> that allowed me to swap when testing.
> That will be my first course of action, the quicker route.  In long run it
> sounds like my best choice would be to
> get into MTASC.  After looking it over a bit I notice its only for
> compiling AS2.  Maybe I'll have to wait.
>

If you are writing AS3 you have a pretty good command line compiler in the
free Flex SDK. It doesn't need swfmill for resources anymore, you can write
Embbed tags in your code and it will simply embed the resources that you
need.

The only reference I found for how to write an Embed tag is
here<http://livedocs.adobe.com/flex/15/flex_docs_en/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Flex_Documentation&file=00001060.htm>
.

Vivi.

After searching a bit I found Haxe which seems to have an AS3 version
> setting, but all of its examples are
> centered around AS2 and I'm not sure about how well it implements the
> Authoring Tools version of AS3.
>
> The Document Class setting seems to have done the trick, so I start there
> and continue to research the
> compilers.
>
> Thanks,
> Boysenberry
>
>
>
> On Oct 25, 2007, at 5:45 PM, Luke Bayes wrote:
>
> This is definitely a difficult issue.
>
> There are two approaches that we have used in the past, I'd be interested
> in hearing what others have done.
>
> a) Use MTASC and SWFMill - or-  MTASC for code and Flash Authoring for
> only symbol creation.
>
> This is most certainly the recommended approach for developing Flash
> Player lite, 6, 7 or 8 content.
>
> This approach allows you to create and reference two different 'main'
> documents. One for running your test suites and one for running your
> production application. Each of these are very, very thin classes and can
> easily include your library SWF whether you create it with SWFMill or Flash
> Authoring.
>
> b) Use Flash Authoring, but #include a different main document depending
> on whether you're going to production or test suites. What this really means
> is that you don't put anything meaningful on the main timeline of your FLA,
> other than maybe a preloader and the #include statement that gets switched.
> It might looks something like this:
>
> #include "Main.as"
> //#include "MainRunner.as"
>
> You just swap which one is commented and each of these included documents
> just attachMovie with a different MovieClip or instantiate a different Main
> class.
>
> This isn't really recommended, but neither is using Authoring as a
> compiler, so if you can't move to MTASC, and you're stuck with Authoring,
> this is the way we've done it in the past. I'd be interested to hear what
> others have to say. This would conceivably work with the latest version of
> Authoring by changing the 'Document Class' reference. I just can't imagine
> going back to non command-line compilation at this point, so I would highly
> encourage you to look into the first approaches.
>
> The one thing that you absolutely, positively do not ever want to do, is
> create two different FLA files and start trying to manually synchronize the
> library from one to the other. This will not help you. These two FLA files
> will inevitably fall out of sync and your test harness will be using a
> fixture that does not match your production environment. This is very, very
> bad.
>
>
> Hope that helps,
>
>
> Luke Bayes
> http://www.asserttrue.com
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>
> http://get.splunk.com/_______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>


-- 
Octavian Costache
http://www.vivi.ro