On Tue, Jun 21, 2011 at 8:31 PM, Michael Pedersen wrote:
> I'm not sure, honestly. We do expose a lot, but is adding more a good idea?
> Unless we lay claim to it and say "tg.varname is how you do x. btw, for now,
> tg.varname is a direct line to this var over in Pylons, but that can change
> late
On Tue, Jun 21, 2011 at 8:31 PM, Michael Pedersen wrote:
> I'm not sure, honestly. We do expose a lot, but is adding more a good idea?
> Unless we lay claim to it and say "tg.varname is how you do x. btw, for now,
> tg.varname is a direct line to this var over in Pylons, but that can change
> late
On Wed, Jun 22, 2011 at 9:33 AM, Alessandro Molina <
alessandro.mol...@gmail.com> wrote:
> On Tue, Jun 21, 2011 at 8:31 PM, Michael Pedersen
> wrote:
>
>> I'm not sure, honestly. We do expose a lot, but is adding more a good
>> idea? Unless we lay claim to it and say "tg.varname is how you do x.
I think it's the only way for us to control our own destiny for the
future, so I'm +1 on it.And I agree that what we ultimately want
is for tg.i18n and tg.session and tg.config to be the way we tell
everybody to use tg -- that way we expose a consistent API and make
pylons/pyramid/paste/formenc
