TG2 changes in process
Mark Ramm
materials out of pylons and into TG2 this week -- after much
discussion. There are several reasons for this:
1) They are there to emulate TG1 behaviors so it makes more sense for
us to own them
2) They are likely to change on the TG2 release schedule -- not the
TG1 schedule.
3) It has been somewhat awkward maintaining them in pylons, since TG2
commiters want to fix/update things and can't because they don't have
commit access to pylons.
We will still strive to make these features usable in plain pylons,
but they will need to be imported from TG2 into pylons, rather than
the other way round. Seems like the right aproach to everybody here,
so hopefully it makes sense to everybody.
Anyway, unless serious objections are raised we'll finish this process
by removing these classes from Pylons on Monday.
--Mark
gas...@gmail.com
I'd like to say ToolBox2 is also updated to work as a live example
with tg2+pylons+dbsprockets trunk.
you could "easy_install TooBox2" from pypi.
Now there are 5 gadgets available:
* info (similar to tg1's)
* tg2 api (epydoc generated api doc)
* toolbox2 api (epydoc generated api doc)
* admin (dbsprockets, to replace tg1 catwalk)
* design (project browser)
Some of gadgets are in early phase though, but you'll got solid idea
of how they work.
--
fred
percious
gadget in the next week.
We really need to get a widget browser up for the twForms stuff. Is
anyone interested in doing this work?
-chris
Jonathan LaCour
> We moved the ObjectDispatch mechanism, decorators, and related
> materials out of pylons and into TG2 this week -- after much
> discussion.
Good move Mark. I actually think this was holding us back more than
anything else, and it was a nice idea to have it be within Pylons,
but in the end, having inside TG makes a lot more sense, and will
let us manage the project in a cleaner way.
--
Jonathan LaCour
http://cleverdevil.org