Hi Richard, but have you ever tried creating a contribution this way? In my opinion, the skeleton should be for the developers who create contributions, and no-one that works with a modern DVCS (which is probably the vast majority of devs) creates versions in subfolders anymore. You've explicitly remodeled the contribution system to cater to people who host contribs at GitHub or similar sites, and there it doesn't make any sense to separate versions this way.
I've updated the "TokenField" contrib to use the skeleton [1] and at the moment, automatic download does not work because the Manifest is not directly below the top-level folder. This is confusing. I don't think removing the skeleton is the right way to go. I've said this before, but I really urge you to provide a uniform way for devs to create contributions. Anything else results in confusion, lack of automatability and even fewer contributions. There hasn't been a new contrib for a long time, or did I miss anything? My (a bit frustrated) 2 cents. [1] https://github.com/cboulanger/qx-contrib-TokenField -- View this message in context: http://qooxdoo.678.n2.nabble.com/create-application-py-t-contribution-and-trunk-folder-tp7586114p7586124.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
