Thanks for the proposals; especially the one involving JSFL was
actually new to me :-)

Another idea (which we like pretty well) is to publish the file to a
different filename/path each time a new version is released, i.e.,
myFlashApp/myApp_v1.swf for the first release, myFlashApp/myApp_v2.swf
for the second release, and so on. To avoid having to change the Flash
Publish Settings each time, this could be achieved with a script that
copies the SWF from the development server to the webserver. As the
website that allows to launch myApp is created dynamically, it can
always link to the myApp*.swf with the highest number. Within the SWF
the version number could then be accessed through the globally
accessible variable _url. This would furthermore have the advantage
that whenever a new version got published on the webserver, clicking
on the myApp link on our (dynamically created) website leads to an SWF
with a new URL (i.e., one that is surely not cached in the browser or
on a proxy server).

stefan.



On 12/1/06, Yehia Shouman <[EMAIL PROTECTED]> wrote:
I think the JSFL offers a great solution if you can have a command to
publish which will alter a variable __DATE__ (perhaps a counter) on the root
of the swf before calling publish document. Not sure if this is possible,
but thats how I'd think of it theoritically

Y Shouman

On 12/1/06, Michael Stuhr <[EMAIL PROTECTED]> wrote:
>
> Stefan Thurnherr schrieb:
> > Hi flashcoders,
> >
> > I am looking for an easy way to indicate an SWF's version on the stage
> > (i.e. via a textfield). I guess the easiest way would be if there was
> > a compiler literal like __DATE__ (indicating the time/date of
> > compilation) available within ActionScript. But I couldn't find any
> > such thing neither in the livedocs, nor with the help of the almighty
> > G.
> >
> > I'd prefer a solution that also works offline (i.e., not involving a
> > call to a server-side script that gives the SWF access to its own
> > time/date of creation).
> >
> > How do other flashcoders solve this problem?
> >
>
> i've created a not-even-near-perfect serial-builder with jsfl.
>
> i'd always wanted to make this an os-version, but haven't had the time to
> do this.
>
> but before offering you my crappy code, i'd like to hear what others do
> have.
>
>
> micha
>
> _______________________________________________
> Flashcoders@chattyfig.figleaf.com
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Reply via email to