Hi Christian > The main reason is discoverability and version management. Of course, you
I don’t agree that npm is better at version management than Git - IMHO it's the opposite. What do you mean by discoverability? The user still has to “discover" the contrib on a webpage somewhere to find out that they want to use it. The only advantage I can think of is if you want to automatically make sure that your app is using the latest version of all contribs - however this can be dangerous because of potential compatibility issues (esp as many contrib authors do not keep their contribs up to date with current Qooxdoo releases). Personally, I would rather update them individually. How many contribs do you use? I use 6 publicly available ones, 4 of which I maintain myself and at least one other I may not even need any more. Regards John On 10 Sep 2014, at 12:04, panyasan <i...@bibliograph.org> wrote: > Hi John, > > > John Spackman-3 wrote >> But why do we need a new mechanism? As opposed to just a web page and a >> Git/SVN url? >> >> As I understand it, the need for a custom contrib mechanism was only >> because there was (is?) a goal to not require the developer to have Git, >> SVN, or any other kind of VCS installed - but Qooxdoo has no problem with >> having other prerequisites (e.g. python, node and npm) so what’s the >> problem with one more? Especially as many devs will have Git or SVN >> installed already. > > can use any location you want as long as there is a zip file that can be > downloaded. You can also inform through this list that you have published a > new contribution or updated an existing one. But not everybody is a > subscriber, and not everybody wants to touch their config.json each time a > small bug is fixed. There is a state of the art for central registries and > version management and it is implemented in systems like bower or npm. They > take care of these things and they are simple to use - that is why they are > so successful. All you would need to do is to integrate them into the > contrib registry, for example, and get rid of the cloning and pull request > stuff. I would shut up and be happy. > > Cheers, > C. > > > > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586173.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 ------------------------------------------------------------------------------ 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
