If this is not a priority of the qooxdoo devs, maybe we should move ahead and agree on a standard format to publish contribs as npm modules? That would be my personal favorite. Technically, this is very easy, since one can install them using npm and then in config.json point to the location of the Manifest file.
To insure discoverability of the contribs, we could agree on a common prefix of the npm modules (for example "qx-contrib-"). What do others think? Sorry to promote the fragmentation of the contribution architecture, but I don't see anything happening and I don't want to use the current system anymore. C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586165.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
