There are pros and cons for both options. I don't know at this point which one is the better. Will have to try / test.
Maurice -----Message d'origine----- De : Kessler CTR Mark J [mailto:mark.kessler....@usmc.mil] Envoyé : mercredi 18 décembre 2013 13:33 À : dev@flex.apache.org Objet : RE: Flex showcase Well I was thinking of not having one large xml root file with everything. Instead having the app listing with icons and lead in short description. Then having the large descriptions, pics, url to owner page, app store url if any stored in the sub-folder ... -Mark -----Original Message----- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Wednesday, December 18, 2013 7:20 AM To: dev@flex.apache.org Subject: Re: Flex showcase Why not just a simple catalogue? <root> --- <items> -- <Showcase Item 1> ---- <Image> ---- <Description> ---- <Title> ...... On Wed, Dec 18, 2013 at 7:15 AM, Kessler CTR Mark J < mark.kessler....@usmc.mil> wrote: > Ok, so flex app loading an xml list from the server. So the last part > is really about how to organize the data on the server. Folder for > each app in the showcase with a pics and another xml file that has the > detail description with the pic file listing. > > -Mark > > -----Original Message----- > From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] > Sent: Wednesday, December 18, 2013 6:16 AM > To: dev@flex.apache.org > Subject: RE: Flex showcase > > I am not sure we could have BlazeDS equivalent on the apache web site. > So maybe text data (info on apps) could be stored in a simple xml file. > Even with hundreds of apps it shouldn't be that large. > And the images (screenshots) would be available as static resources, > as it is today, and loaded on demand by the flex app. > AFAIK, javascript can also parse remote XML files, so data storage > would be independent of the implementation (js or flex). > > WDYT? > > Maurice >
