> central server but I would rather not do that. I might resort to the > JSON/XML approach which was one of the options we were looking at but > when the editors need particular views it might not be as appropriate. > Is there a standard way for providing third party plugins?
It depends somewhat on what you are thinking of. Is there a standard way how somebody could provide qooxdoo code that others can use in their applications? - Yes, just use a normal skeleton. Every skeleton establishes a qooxdoo library, even if it only contains a single class. This library (in its source form) can be passed around and used by other qooxdoo apps. All you have to take care of is that the library's name space doesn't collide with something existing in the target environment. Still, for the receiving application, all those libraries have to be around when you generate the target app. There is no possibility to add a plug-in to an already built application. HTH, T. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
