Hello, > This application I'm developing has many window instances. Each of these > instances is used to display a tabbed form, and there are many different > forms involved, some sharing the same tabs. At what level should I be > pooling widgets at to optimize widget creation/destruction as much as > possible? By that I mean should I be pooling entire window instances, forms, > or individual tabview pages? I would say that depends on what kind widgets you can reuse. The bigger the blocks you can reuse, the better.
> I lean toward pages since I could lazy load the model for the page and > render them as they are accessed to avoid having to create tons of form > field instances. This also would allow easier pooling of page instances that > are shared between forms. One example is a tab that contains a widget for > uploading and attaching photos. The most common use case for these forms is > to only work with a small number of tabs, and I believe that the lazy > loading of individual tabs is preferable to loading a monolothic form model > and rendering fields that won't be used. That sounds good but you can still add the pooling of widows instances as well. Just remove the content and you can pool the window itself. > However, I know the documentation suggests pooling the "largest" widget you > can, which would be at the window level. This is why I feel I need advice on > the matter. Thanks. As you said, its only a suggestion and if pooling the pages fits more, go ahead and get that done. I think doing pooling the right way with smaller widgets is still better than doing it with the largest widget and wrong. And in any way, its most of the time better than not doing it. ;) Regards, Martin ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
