My suggestion would be to create the file with dummy data, and run
some processing tests on it on machines of various speeds.
My guess is that you'll find it to be pretty slow unless your
processing code is very clever. I have a project with a 250KB
external XML file as content and certain sorting and filtering
options do take a while. Another which is 210KB has similar problems.
If your app will tolerate it, you could do processor-intensive
operations across multiple frames and present an hourglass to the
user or something.
If performance is super imporant, you might try organizing your data
in a tabular format, which will be a much larger file, but should be
quicker to process and sort.
Or perhaps you could do it in Flash 9 and take advantage of E4X in AS3.
If you know everyone running it will be on super fast machines, then
maybe you don't have anything to worry about.
-josh
On Mar 11, 2007, at 10:34 AM, Hairy Dog Digital wrote:
Hi all,
I have a project that I have spec'ed for developing in Flash MX 04
(or Flash
8) along with Director MX 04. The project has a large amount of
data that
will be read into the program. I'm trying to determine whether
there are any
practical limitations to using XML with Flash. The data lends itself
beautifully to XML, and would be an easy conversion to XML from the
source
documents provided by my client. However, there is a considerable
amount of
data, consisting of 5000 records in a structure with nodes nested 7-10
levels deep, such as:
----------------------------------------------------------------------
+ family
+ subgroup (1 to n levels of subgroups, varies by family)
+ subgroup
+ subgroup
+ subgroup
+ part-type
+ part
x part-number
x part-description
+ item
x item-type
x item-filename
x item-label
----------------------------------------------------------------------
+ NODE (0 or more of each) x TBD: ELEMENT or ATTR of parent element
----------------------------------------------------------------------
The data will not require sorting. Data will be presented in the
sequence
contained in the XML file. In addition, searching will only be done by
*part-number* with optional filtering by *item-type*.
So, I have approx. 5000 *item* records and prefer to do this with
XML. The
project is CD-based, not an online application. Is it practical to
read/parse that much XML into a single XML object in a Flash
application
running from CD?
_______________________________________________
[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
