Re: [tg-trunk] Request For Feedback
On Sat, Nov 19, 2011 at 12:37 AM, Carlos Daniel Ruvalcaba Valenzuela clsdan...@gmail.com wrote: I'm quite interested on the hooks and the pluggable apps, I was doing a small cms structured in a similar way as drupal, as there was no clear way to provide tg backed extensions mechanism, I rolled my own, but I rather use something from core, is there docs on this already (in dev branch)? For pluggable apps there is nothing available yet, for the hooks you can take a look at http://sourceforge.net/p/turbogears2/tg2docs/ci/d529b6eda32ba59792818938f8e6aac5e7b91b24/tree/docs/main/Config.rst (Search for Hooks) The app wide hooks will be available only from 2.1.4, but the controller hooks have always been there. I used them for tgext.debugbar, so you can take a look at https://bitbucket.org/_amol_/tgext.debugbar/src/589ca2137ce0/tgext/debugbar/initialize.py for an example. -- 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] Request For Feedback
Am 18.11.2011 21:06, schrieb Michael Pedersen: First up: Python 2.4. I've said it in the past few months, but it's starting to look like we must address this sooner rather than later. Other projects are dropping support for it (for instance, WebOb, as of 1.1b1, has dropped support). I'm even willing to mark the next release as 2.2 just so we can drop 2.4 support entirely, and make our minimum either 2.5 or 2.6 (I'd like it to be 2.6 personally, so that we don't have to reach a similar point in another year or two). What does everybody else say? Right. I'd say drop Py 2.4 in TG 2.2 and Py 2.5 in TG 2.3. Second up: repoze.who is at 2.0. With our current set up, we are locked in at the 1.x series. I'd like to find a way to bring 2.0 support in so that it works easily for people. We can make it so that it is not required (similar to how TW1 and TW2 are both options), but I definitely want to get all of our packages upgraded to support the latest of everything. This way, we reduce some of the issues we've had where people are managing to get incompatible versions of packages (WebOb in particular). If possible, we should move to repoze.who 2.0 in TG 2.2 or 2.3, and also consolidate the used plugins as Alessandro suggested. Unfortunately it seems I won't have enough time for working on TG2 the next two months, so sorry I cannot help out with this. -- Christoph -- 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] Request For Feedback
On Fri, Nov 18, 2011 at 3:42 PM, Christoph Zwerschke c...@online.de wrote: Right. I'd say drop Py 2.4 in TG 2.2 and Py 2.5 in TG 2.3. Now, the major question: We're nowhere near where I wanted to be for 2.2. For that, I still need to finish up hiring pond and the book that goes with it. I very much doubt that I can do both before Christmas (and I'll be pleasantly surprised if I can finish up the app before then, I've got a lot to put into it). Is it worth making the bump to 2.2 for the Christmas release? -- 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] Request For Feedback
I'm +1 for both of those. But I'll postpone them at 2.2 as suggested by Christoph and I really don't want to see anymore my app depending from 6 packages just to make auth work. After 2.1.4 I think we should freeze and start thinking at 2.2 I think that they are too big changes for 2.1.4 and I would like to release 2.1.4 this month. I really need help from a mako user by the way, because there are some pending tickets which are mako related and I don't use mako at all so I'm not the best person to solve them. My personal targets are: * 2.1.4 - Create a good and reliable hooks system for tg to make plugins easy to inject (should be already there on the dev branch) - Make fastest and easier to use tgext.admin and tgext.crud. (EasyCrudRestController is a step in the right direction, I recently been able to write a full small application without writing one single controller method using only tgext.crud and I realized some minor improvements that it might need but not many) - Ming hooks system (Sent a patch to Rick, waiting for him to approve this) - Release tgext.debugbar as an external dependency that people can start using (requires the hooks in tg and ming) - Improve sprox and tgext.admin ming support * Between 2.1.4 and 2.2 - Release tgext.pluggableapps to mount complete ready to use applications like django apps using the 2.1.4 hooks system - Improve the website, hell we don't even have a news box on the website and still the tgext.pages crashes every time I try to save an edit * 2.2 - Integrate tgext.debugbar and tgext.pluggableapps inside the standard quickstart - WebOb1.2 support - Make tw2 the default option? We still quickstart on tw1 while tw2 is at least as much stable and more maintained. - Trash away most of the repoze.who/what dependencies - Find a decent solution to dependencies management. On Fri, Nov 18, 2011 at 9:06 PM, Michael Pedersen m.peder...@icelus.org wrote: After doing the release for 2.1.3, and reading some of what's going on in the word of our packages, I think I'm looking at a couple of growing problems for TG2. One of these I wanted to bring up earlier, but the other only really hit me today as something we should consider. First up: Python 2.4. I've said it in the past few months, but it's starting to look like we must address this sooner rather than later. Other projects are dropping support for it (for instance, WebOb, as of 1.1b1, has dropped support). I'm even willing to mark the next release as 2.2 just so we can drop 2.4 support entirely, and make our minimum either 2.5 or 2.6 (I'd like it to be 2.6 personally, so that we don't have to reach a similar point in another year or two). What does everybody else say? Second up: repoze.who is at 2.0. With our current set up, we are locked in at the 1.x series. I'd like to find a way to bring 2.0 support in so that it works easily for people. We can make it so that it is not required (similar to how TW1 and TW2 are both options), but I definitely want to get all of our packages upgraded to support the latest of everything. This way, we reduce some of the issues we've had where people are managing to get incompatible versions of packages (WebOb in particular). Finally, I'd like to push the next release back to the Christmas release. We'll get Alessandro's debugbar added in, we'll get the above features added in, we'll clean up the current warnings we see when running the tests, and then we'll cut that as our next release. What do you all think? -- 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. -- 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] Request For Feedback
On Fri, Nov 18, 2011 at 10:03 PM, Michael Pedersen m.peder...@icelus.org wrote: On Fri, Nov 18, 2011 at 3:42 PM, Christoph Zwerschke c...@online.de wrote: Right. I'd say drop Py 2.4 in TG 2.2 and Py 2.5 in TG 2.3. Is it worth making the bump to 2.2 for the Christmas release? I would prefer pushing out 2.1.4 out for november/december with as much improvements as possible to doc. I see 2.2 around February/March of the next year. -- 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] Request For Feedback
I also share the opinion that dropping support only for Python 2.4 in tg2.2, then Python 2.5 on the next. I thought that 2.1.4 was going to be released shortly given the incremental advances and bugfixes that the team has been doing, thus I think it would be good to release a 2.1.4 with usual fixes and minor additions here and there, and push back 2.2 to next year to pack it with all the new features. I'm quite interested on the hooks and the pluggable apps, I was doing a small cms structured in a similar way as drupal, as there was no clear way to provide tg backed extensions mechanism, I rolled my own, but I rather use something from core, is there docs on this already (in dev branch)? There is a bunch of interesting things (peripheral to the project) that I would like to propose, such as creating a site for turbogears users like djangopeople but for turbogears people, really, djpeople has landed me a few nice gigs in the past and would love to some day have turbogears gigs in this fashion. Regards, Carlos Daniel Ruvalcaba Valenzuela -- 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.
