Chris Miles wrote: >> Yes toolbox could be in a separate egg but also in the set of eggs >> present in the setup.py file so it is installed at the same time >> as TG if the user gives the option... >> >> so +1 for separate eggs from me :) > > +1 from me too. > > Toolbox is of most value to new users. It should be available to > them out of the box. Maintaining toolbox components as separate eggs > will help delegate responsibility to those who are interested in > developing them, without effecting the core.
To me, the toolbox was the beginning of the end of TurboGears 1.0 being a small, lightweight collection of great tools for building web apps, and the beginning of TurboGears becoming bloated. I really feel strongly that the Toolbox should be a separate egg, and not a requirement for the standard TG 2.0 install. To me, a required dependancy is as good it being a part of the core, which it clearly doesn't need to be. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
