On 07/25/2012 12:01 PM, panyasan wrote: > One use case comes to my mind: Imagine I want to move the trunk of my Dialog > contrib from sourceforge to github (as I actually do --- BTW sorry that the > trunk of this contrib is still buggy). Looking at the sf SVN, there would be > no way of knowing this, and keeping the wiki updated is a nuisance (I am so > lazy), and people wouldn't necessarily have a look. > > If, however, the config.json file just contained a reference to the name of > the contrib, and the central repository would know from where a particular > version of the contrib can be downloaded, this would avoid a lot of > confusion, rid the contrib users from having to deal with URLs etc.
Maybe you have forgotten about the new design [1], but that's exactly the plan. T. [1] http://qooxdoo.org/contrib/qooxdoo-contrib2.0 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
