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 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. 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. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Need-advice-on-the-best-plan-for-optimizing-window-instances-tp6395297p6395297.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
