On 08/19/2011 07:18 AM, linucos wrote: > Hi, > I just use parts tech to speed up my application when the web page is > loaded for the first time. > But from my pratice, a "hello world" application has a 500KB size. My > questions are : > 1. Is that the proper size?
Yes. > 2. Is not all the component in? What do you mean with component? If you refer to classes, then no, not all possible classes of the framework are in, only the needed ones. > 3. If not all component in it, how to load a component in runtime? Again I'm not sure what you mean with component. Are you referring to parts here? The call to load a part is qx.io.PartLoader.require(), but that's all in the docs. > 4. Can we reduce this "boot" part size using qx's toolchain? Well, depending on your application you could create a non-GUI class as your main application class which is loaded with the boot part. The non-GUI class would then load further parts. You could display a "busy" image during this time. The question is whether you need user interaction in the boot part. > 5. Other tool to recude the size or speed up when loaded? See the many postings on this mailing list concerning this topic. > From my view, parts tech is used to reduce the load time for a whole BIG > APPLICATION. > But, in the web , we need a fast load for the first page. Try to think about which classes you need when. Maybe you don't GUI classes at all?! As you say "in the web" in contrast to rich internet applications (which are also "in the web" ;), maybe the low-level layer of qooxdoo is enough for you?! T. ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
