Matt, Thanks for the answer!
I made experiments, and I decided to use "auto" creationPolicy, I will optimize my mxml and I think it will work fine. Best regards Stanislav On 2/13/06, Matt Chotin <[EMAIL PROTECTED]> wrote: > With the queued policy you may want to specify the creationIndex to > further control things. A creationPolicy of "all" will do all of the > work at startup which will mean that the app is slow to initialize but > will be fast afterward. Is that preferable? > > These are the tradeoffs, I'm not sure that you can really get creation > going without the UI slowing somewhere. When you do the default policy > things we spread it out. When you use queued you get to see some > visible progress but you only get to watch, it's hard to interact. When > it's none you get to control it entirely on your own and you can tune > however you want. > > It seems like you just need to experiment to find the tuning that works > for you. > > Sorry, > Matt > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Stanislav Zayarsky > Sent: Friday, February 10, 2006 4:17 AM > To: [email protected] > Subject: [flexcoders]How to create Heavy interface properly? > > Hello Flex Developers, > > I have next problem: > > Context of the problem: In my application I have little main page with > text info, and after mouse click user goes to next page where is > accordion placed with 5 childrens inside and every of this children > load some data from server and then show it, using different > components(dataGrid, List, etc...) this childrens are quite heavy. I > know it is possible to optimize them, but let's assume that they are > optimized to maximum. > > Problem: When user goes to accordeon, he needs to wait some time(1-3 > sec) before accordeon child initializes, load data and finally show > it. > First aspect of the RIA is Seamless, and it doesn't work here! > > Solutions: > 1. I tried to use creationPolicy="auto" on accordion and it works, but > still user need to wait while active child initializing and load data. > > 2. creationPolicy="queed", but in Accordion it didn't work properly, > it creates just top container of the childrens and that's all. > > 3. Using creationPolicy="none", I developed my own little solution > and now childs initializes one by one properly, i.e like > creationPolicy="queed" should work. > BUT... the application freezes, while other childs initializing in > the meantime and load data, so user can't interact with interface. > > Ideal WorkFlow: User read data on first page, in the meantime > accordion initializes, load data and place it properly. And > application doesn't freeze! > When user goes next screen everything is working without delays. > > So the question is: How I can achieve this Ideal Workflow and > especially how I can avoid freezing application? > > Thanks in advance. > > Best regards > Stanislav > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > > > > > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
