Hi Christian, you bring up some valid points. Please copy your proposition and paste into a feature request in qooxdoo’s bugzilla, just to make sure it doesn’t get lost.
We’ll take it definitely into consideration. Best, Andreas Am 27.04.2014 um 23:11 schrieb panyasan <[email protected]>: > Just an idea that occurred to me today: The qooxdoo sdk is quite big and > contains a lot of code that is not needed in the (or at least in my) normal > development workflow. I would assume that typically, only the "framework" > and "tool" folders are actually used. I go to the qooxdoo website for > everything else: API viewer, playground, Widget browser, instead of building > it locally. > > I wonder if it wouldn’t make sense to move the „components“ and the > „applications“ to the contributions. This would have several advantages: > > - the SDK becomes slimmer (if not much in code size, then at least in > complexity) > - this would add some top-quality contributions, increasing the value of the > registry on the whole > - the core devs would have a bigger incentive to use the contributions > infrastructure themselves, thus insuring that it well-maintained and > functional (for example, concerning dependency management) > > To be sure, this would mean that the process of adding the contributions > back to one’s development environment must be easy to ensure that they are > actually used. In a related proposal [1], I have suggested that adding and > removing contributions should be possible without manually adapting the > config.json, using the command line. This could be done with the > applications and components, using the generator as well, for example, like > so: > > ./generate.py contrib-install playground > > or something like this to download and install the playground as a > contribution. > > Of course, these contributions wouldn’t be „libraries“ in the sense that > they would be part of the main application. Instead, they would have to be > downloaded and built in separate subdirectories. > > As I said, just an idea, but in a longer perspective, it seems to make a lot > of sense to remove the components and applications from the „SDK“ and put > them into an infrastructure for modular pieces of code that works with the > core framework code. > > [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=8285 > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/qx-Website-Move-SDK-components-and-applications-as-contributions-tp7585590.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
