Re: [tg-trunk] TG namespace things
I like this idea, actually. It encourages people to use the tg namespace when possible. I am normally against monkey-patching, but this is one time I can agree with it easily. Looking at the docs updates that I need to do for this release cycle, I don't know if I will be able to review this branch until the next one (2.1.3). They're extensive, but we really need these changes for 2.1.2. After reading the recent comments in the "What Would It Take" thread, I almost think I should have waited on 2.1.1 to have these docs done. I *will* review this later, Alessandro. I want to see this sort of change. You and Mark are right, it's the best choice for pushing us forward. I just don't know if I will be able to review for 2.1.2. On Sat, Jun 25, 2011 at 3:30 PM, Alessandro Molina < alessandro.mol...@gmail.com> wrote: > On Wed, Jun 22, 2011 at 2:48 PM, Mark Ramm wrote: > >> 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/formencode/etc into implementation details. >> >> > When talking with Mark about the idea of exposing everything through the tg > namespace instead of the pylons one he suggested the idea of monkey patching > pylons to report a deprecation warning to people accessing pylons.something > instead of tg.something. > > I think that this might be a great idea to help people migrate their apps > to the tg namespace, but as it involves quite some changes, before merging > it into the development branch I think it needs a bit of review and real > world tests from others. > > The changes are available in the nru_depr_warn branch. > > > https://sourceforge.net/p/turbogears2/tg2/ci/7826dbfdd6147227311c4023f5361362a2915025/ > > Still missing monkeypatching of i18n related things and caching, most of > the other things should be there. > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- Michael J. Pedersen My IM IDs: Jabber/peder...@icelus.tzo.com, AIM/pedermj022171 Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
On Wed, Jun 22, 2011 at 2:48 PM, Mark Ramm wrote: > 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/formencode/etc into implementation details. > > When talking with Mark about the idea of exposing everything through the tg namespace instead of the pylons one he suggested the idea of monkey patching pylons to report a deprecation warning to people accessing pylons.something instead of tg.something. I think that this might be a great idea to help people migrate their apps to the tg namespace, but as it involves quite some changes, before merging it into the development branch I think it needs a bit of review and real world tests from others. The changes are available in the nru_depr_warn branch. https://sourceforge.net/p/turbogears2/tg2/ci/7826dbfdd6147227311c4023f5361362a2915025/ Still missing monkeypatching of i18n related things and caching, most of the other things should be there. -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
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/formencode/etc into implementation details. --Mark Ramm On Tuesday, June 21, 2011, 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 > later". > > On the surface, the idea sounds good, I'm just not sure it's the way for us > to go forward. Thoughts from anybody else? > > On Tue, Jun 21, 2011 at 1:17 PM, Alessandro Molina > wrote: > Most of the pylons things used by TurboGears are accessible from the tg.* > namespace directly.I think that this is indeed good as it keep an high level > of abstraction from pylons itself and gives use more freedom for future > evolutions. > > > I was thinking to take a look around in the documentation, look of each > pylons.something function used inside the doc and migrate it to > tg.something.Also if in the process I discover something that isn't available > inside the tg namespace I woud expose it inside tg itself. > > > What is others opinion about this? Any one against doing this? > Alessandro > > > > -- > > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > > > -- > Michael J. Pedersen > My IM IDs: Jabber/peder...@icelus.tzo.com, AIM/pedermj022171 > Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com > My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen > Twitter: pedersentg > > > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- 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 turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
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. btw, >> for now, tg.varname is a direct line to this var over in Pylons, but that >> can change later". >> >> > I feel that the opposite might be worse as it would mean claiming: "For now > to do this in TG you have to rely on Pylons and in the future you might have > to rewrite things if we decide to change that". > Sorry, great internet connection of the hotel caused the email to be sent two times -_- -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
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 > later". > > I feel that the opposite might be worse as it would mean claiming: "For now to do this in TG you have to rely on Pylons and in the future you might have to rewrite things if we decide to change that". -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
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 > later". > > I feel that the opposite might be worse as it would mean claiming: "For now to do this in TG you have to rely on pylons and in the future you might have to rewrite things if we decide to change that". Anyway, I'm also posting it here to hear others voice :) -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] TG namespace things
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 later". On the surface, the idea sounds good, I'm just not sure it's the way for us to go forward. Thoughts from anybody else? On Tue, Jun 21, 2011 at 1:17 PM, Alessandro Molina < alessandro.mol...@gmail.com> wrote: > Most of the pylons things used by TurboGears are accessible from the tg.* > namespace directly. > I think that this is indeed good as it keep an high level of abstraction > from pylons itself and gives use more freedom for future evolutions. > > I was thinking to take a look around in the documentation, look of each > pylons.something function used inside the doc and migrate it to > tg.something. > Also if in the process I discover something that isn't available inside the > tg namespace I woud expose it inside tg itself. > > What is others opinion about this? Any one against doing this? > > Alessandro > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- Michael J. Pedersen My IM IDs: Jabber/peder...@icelus.tzo.com, AIM/pedermj022171 Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
