The browser should (and does) cache images so the second time around stuff should be faster...but I can't trust that it will be seamless. The other part of this is that in a lot of cases nothing will change in the xml except for the selected option having a selectedState="true" attribute. In cases like hat all I need to do is change the option's visual state.
The interesting thing about the images for each option is that they are actually defined in a seperate xml file I am mapping to the unique IDs returned by the tool. So if I know that nothing changed in a given node then I'll just skip over it, skipping reloading the image, updating any rollover description, etc. Its the options that get added or dissapear that I am concerned about. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Julius - XK Sent: Sat 6/10/2006 11:11 PM To: Flashcoders mailing list Subject: Re: [Flashcoders] XML diff Doesn't the browser cache images? I've never had a problem with performance reloading anything. Have you tried just letting it all reload? Another thing you could do is just check to see if the path is the same as the previous, if it is then skip loading a new image.. ----- Original Message ----- From: "Howard Nager" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" <[email protected]> Sent: Saturday, June 10, 2006 4:30 PM Subject: [Flashcoders] XML diff I have an upcoming project and am trying to figure out how to do what would best be described as a diff on a xml file. For example, here would be the initital xml: <root> <optionsA> <group> <option ... /> <option ... /> </group> <groupB> <option ... /> <option ... /> <option ... /> <option ... /> </group> ... </root> The way the system works is that all of the logic is handled server side. So when the user selects an option it hits the server and gets back another xml file with an updated price and more or less options depending on whatever rules came in to play. The front end was originally an html page which would redraw itself with every interaction. If I were to just emulate that model I would grab the new xml and redraw the menu within my flash movie with every selection. The issue with that is that each option has an associated thumbnail image loaded externally and redrawing hte menu would mean reloading all of those. I would rather look at the new and old xml files side by side and see what changed so that I could leave anything that didnt change alone. Any ideas on this? -------------------------------------------------------------------------------- > _______________________________________________ > [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 _______________________________________________ [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 _______________________________________________ [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
