> Is it better to generate a different XML files for each of the
> different trees I want to build, or load all of the data in one XML
> file and let flex split up the data into the different pieces.
I wouldn't do either. First I'd make an XML file that is a simple
view-independent list of sermons, in any order such as
<sermons>
<sermon date="..." speaker="..." book="..." chapter="..."/>
...
</sermons>
Next I'd write AS3 code that can filter and sort this XML on various
fields.
Then I'd write AS3 code that can transform a filtered, sorted list into
a hierarchy such as
Genesis
Ch. 1
4/1/2007
4/9/2007
Ch. 7
3/4/2007
Exodus
...
Then I'd write UI to let the user enter the filter criteria, choose a
hierarchy, they like and display it in a Tree.
- Gordon
________________________________
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Bjorn Schultheiss
Sent: Monday, April 09, 2007 3:51 PM
To: [email protected]
Subject: Re: [flexcoders] Most Efficient Design Question
Put it all in one.
Let Flex do the work.
On 09/04/2007, at 10:49 PM, lncdeveloper wrote:
I am looking into building a Flex application for my Church.
They
have a tape/CD library of sermons over the past 15 years.
The data is in a database, but for my first version I will be
generating XML files to use as the data source.
I would like to have several different view states where they
could
look at the data differently
e.g.
View by speaker
View by book/chapter of the bible
View by date
With a tree control for navigation
e.g
Genesis
1
2
3...
Exodus
Leviticus
...
So, my question is:
Is it better to generate a different XML files for each of the
different trees I want to build, or load all of the data in one
XML
file and let flex split up the data into the different pieces.
