Hi, as you might have gathered from the wiki page, the idea of packages has been carried further. The lingo has shifted a bit, the basic construct is now called a 'part', but the fundamental idea has been retained, as it is expressed on the 0.7 manual page: To split out parts of the application into own packages that can be loaded on demand.
As you have migrated your application to 1.x, you already have a config.json in your application directory. This is the main tool to configure your application's build process. The main key for you to integrate is the 'packages' config key [1]. [2] has an overview of the part documentation, and [3] is probably what you are looking for. It is also necessary that you modify your class code to load parts in the appropriate situation during run time (explained in [3]). Have a look at the standard Feedreader application [4], which uses parts in a straight-forward way, and has corresponding configuration features. HTH, T. [1] http://qooxdoo.org/documentation/1.1/tool/generator_config_ref#packages [2] http://qooxdoo.org/documentation/1.1#specific_topics [3] http://qooxdoo.org/documentation/1.1/parts_using [4] http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/tags/release_1_1/qooxdoo/application/feedreader/ On 05/10/2010 01:31 PM, Qoo Goo wrote: > Hello, > > After a migration from a complex application based on Qooxdoo 0.7 to > 1.x, we are now trying to figure out how to reimplement our plug-ins > mechanism. > > We were using our own mechanism server-side and in client-side we based > our plugins architecture in the contents of the article in > http://qooxdoo.org/documentation/0.7/split_up_application. Fortunately > this mechanism to inject code at runtime still works, but the problem we > are facing now is the building process for those extensions. > > The building instructions on that page do not work any more, and we've > been trying to build this extensions with now success until now. > > Are there some guide to build something that is not a whole standalone > application, but just an extension for an existing application? > How would you build a sort of classes without including those code > already used in main application and including resources as needed? > > Thanks in advance. > > Al > > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
