Phillip G. Apley wrote:
> I am writing some scripts which can be integrated into the build process 
> and will generate .png files for each .swf file in the system as a first 
> step towards rasterizing components for use in DHTML. I want to be able 
> to keep track of which .png files were created manually and are 
> therefore not to be replaced by the automated png generator. I had some 
> baroque thoughts about managing a database pf pathnames. Then I thought 
> to put the generated .png files in a special (automatically generated) 
> subdirectory of the directory in which the swf appears 
> (legals/.../autopng). The compiler would look for a hand-generated or 
> approved .png in the same directory as the swf. Then, if there is none, 
> the compiler would look for a png in the autopng subdirectory. Max 
> suggested it might be better to name the files resourcename.swf.png to 
> show they were autogenerated, and avoid creating unnecessary 
> subdirectories, but to me it seems that parsing and tracking the double 
> file type is more complicated than just putting the autogenerated files 
> in a separate subdirectory. Thoughts?

The main reason I suggest avoiding a separate subdirectory is for ease 
of use for LZX developers and the designers working with them.  I think 
most designers would prefer to save a file with a different extension, 
rather than have to create a new directory.  Using extensions may be 
more work for us and the compiler, but I think it's ultimately nicer to use.

-Max
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to