Hello, I had a similar problem trying to implement plugins via the parts architecture. I've been told that this was not what the parts system had been designed for, so it is kind of a hack. But it works:
Since the part loader system depends on static code analysis, you need to name the parts explicitly in your config.json <https://github.com/cboulanger/bibliograph/blob/master/bibliograph/config.json> , and in the class that contains the part loader <https://github.com/cboulanger/bibliograph/blob/master/bibliograph/config.json> . So you need to keep those files updated manually. Third parties then can provide libraries. I use a shell script to create plugin skeletons <https://github.com/cboulanger/bibliograph/blob/master/bibliograph/tool/create-plugin.sh> to make that easier. Hope that gives you some ideas. I wish it was not a hack, but supported out of the box by qooxdoo! Best, Chrsitian -- View this message in context: http://qooxdoo.678.n2.nabble.com/How-to-make-parts-independent-tp7587856p7587857.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
