There's been talk about a tg-dev package, which would contain tools for developing turbogears projects. The thought behind this is
1) tg-dev would allow the dev tools to update more frequently than the core TurboGears project. The core should be as stable as possibe, but the dev-tools should continue to grow and evolve much more quickly. 2) It would allow server-installs to skip a bunch of dependencies. We would make the tg-dev package the thing which we tell people to install on the TurboGears.org page, and it would of course depend on TG directly. As I was thinking about this last night it seemed that the following items that are currently in the core should move to dev: 1) the quickstart command and the new-project template code. You don't need this on a server, and it really is a dev tool. 2) the crud command and templates. We may also want to move the Toolbox2 code into the tg-dev package. My thinking here is that the Toolbox 2 gadgets should continue to be separate packages but it makes sense to put the code that hooks it all together into the "core" dev package. Just the removal of the paster templates will make the tg core package about significantly smaller, and should hopefully make the core more stable and easier to understand. If there is some agreement that this makes sense, I'll go ahead and create the package when I get my laptop back from the shop (or I break down and setup a dev environment on this borrowed machine. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
