I've done in the past something as Rakos says and i think it could be a good choice. If you really have to go for the xml, i'd say:
- wherever possible, try to use attributes instead of nodes to avoid unnecessary nesting. - wherever possible, split the xml files so you can read exactly what the user needs and not everything. Good luck : ) On 3/12/07, Rákos Attila <[EMAIL PROTECTED]> wrote:
A while ago I had problems with parsing and processing a large XML. It was too slow even after utilizing some tricks and optimizations, so I decided to convert the XML into an ActionScript source file containing "constant" arrays and objects. This AS file was then compiled into swf, loaded into the main movie and it became much more faster, there was no noticable processing time. Since on CD you will not need an editable XML, maybe you can try such way, too. Attila _______________________________________________ [email protected] 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
-- Juan Delgado - Zárate http://zarate.tv http://dandolachapa.com _______________________________________________ [email protected] 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
