splict
02-12-2004, 07:09 PM
I'm trying to give forms (screens) and these data/ui components a try. I've got to build a CMS and I have a short deadline so I was hoping this could help. I am using the XML connector and the datagrid to display some (real estate) listings.
Everything goes okay in a new (otherwise blank) form document. Once I move this into my app I get an 'abort this script?' alert because its too slow :mad: The rest of the file is just a few screens and a few components with no functionality. The data is only 11 listings with about 12 attributes each (neighborhood, beds, baths, etc). If I click not to abort the script everything finishes up fine and the data is parsed properly.
Is XML parsing with the built in components really that bad? I obviously can't tell clients "Oh, its cool. Just click 'no' when it freezes up and asks you if you want to abort." Am I doing something stupid (besides using the v2 components :p ) I'm nowhere near adding all the functionality that the file will use and I certainly want it to be scalable. Plus I paid extra for pro, and here I can't use the stuff that comes with it. How does Macromedia plan on pushing these v2 stuff to larger companies if they are too slow to do basic stuff? btw I am only on a 1.13GHz PIII but I expect that thats not that far behind the average.
Hopefully I am doing stuff wrong - if you tell me that this is uncharacteristic behavior then I will keep at it and try other things like different structures for my xml file etc. I just don't have the time to make things more complicated than they need to be. Thats why I thought these components might be okay to use in this situation.
-splict
Everything goes okay in a new (otherwise blank) form document. Once I move this into my app I get an 'abort this script?' alert because its too slow :mad: The rest of the file is just a few screens and a few components with no functionality. The data is only 11 listings with about 12 attributes each (neighborhood, beds, baths, etc). If I click not to abort the script everything finishes up fine and the data is parsed properly.
Is XML parsing with the built in components really that bad? I obviously can't tell clients "Oh, its cool. Just click 'no' when it freezes up and asks you if you want to abort." Am I doing something stupid (besides using the v2 components :p ) I'm nowhere near adding all the functionality that the file will use and I certainly want it to be scalable. Plus I paid extra for pro, and here I can't use the stuff that comes with it. How does Macromedia plan on pushing these v2 stuff to larger companies if they are too slow to do basic stuff? btw I am only on a 1.13GHz PIII but I expect that thats not that far behind the average.
Hopefully I am doing stuff wrong - if you tell me that this is uncharacteristic behavior then I will keep at it and try other things like different structures for my xml file etc. I just don't have the time to make things more complicated than they need to be. Thats why I thought these components might be okay to use in this situation.
-splict