Hi Mark, This is very useful.
I filed tickets for 1, 2, and 3. I've never used Pylons, SA, TG, etc before (or even Python for that matter), or I'd file patches rather than just tickets. It all looks clean, so sonce I learn a lot more, I hope I'll be able to contribute some. 5 is definitely key to get right. I've managed sites with tens of millions of registered users and being able to stage and test DB upgrades (not to mention actually run them on production sites without interrupting things) while still having APIs that keep it easy for developers to develop using their own machines in non-trivial. Migrate + some commands to run the create from scratch would be a good starting point. For 6: The model dir should make it clear whether model objects on in __init__.py or in their own files (I know there's some choice, but good defaults would be great). Likewise, controller/root.py might have a commented out import to show how to cleanly reference model objects there. (I know this is minor, but it's great when new frameworks expose things that experienced users would take for granted). This will become less necessary when there are more sample TG2 projects. For 7: Ok, just wanted to make sure I'm not missing anything. Hopefully when identity is there, it will include easy ways to plug a registration page into your site and for that registration to support sending an email that asks you to click a link to confirm as well as stuff like "I forgot my password". I hate re-writing all that stuff in every project I do... (I may add some tickets for 'wishlist' features as well--my #1 would be that ToscaWidgets wraps the Dojo toolkit.) Thanks again. On Aug 26, 1:34 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote: > Could you open trac tickets for 1, 2, and 3? I'd hope we can get > those taken care right away. > > 7 is a known issue (Identity has not been ported...) > > and could you also explain 6 a bit more so that I can understand what > youre looking for? > > As for 4, I thought there was some work done by Fred on this, but I'll > take a look at the current code and see what's happening. > > 5 is definitely a known issue, and we're trying to work out how the > command line tools ought to work on the pylons mailing list. > > --Mark > > On 8/26/07, Neighborhood Org <[EMAIL PROTECTED]> wrote: > > > > > > > I'm trying out Turbogears for the first time and figured I'd start > > with TG2. It looks very promising. > > > I suspect these are known issues, but I didn't see most of them in > > Trac, so I figured it would be useful to report/ask (and please feel > > free to follow up if I'm wrong): > > > ------ > > > 1) It looks like SAContext is deprecated in SA 0.4 and that TG > > shouldn't be using it in lib/database.py > > > /opt/local/lib/python2.5/site-packages/SQLAlchemy-0.4.0beta4-py2.5.egg/sqlalchemy/ext/activemapper.py:24: > > SADeprecationWarning: SessionContext is deprecated. Use > > scoped_session(). > > self.context = SessionContext(*args, **kwargs) > > > -- > > > 2) From the Pylons 0.96 upgrade, helpers has moved: > > > /Users/dlgould/tg/tutorial/tutorial/lib/base.py:9: DeprecationWarning: > > The pylons.helper module has moved to pylons.controllers.util; please > > update your imports. > > from pylons.helpers import abort, etag_cache, redirect_to > > > -- > > > 3) Likewise: > > > /opt/local/lib/python2.5/site-packages/TurboGears2-2.0a1dev_r3399-py2.5.egg/tg/controllers.py:41: > > DeprecationWarning: pylons.h is deprecated: use your project's > > lib.helpers module directly instead. Your lib/helpers.py may require > > the following additional imports: > > > from pylons.helpers import log > > from pylons.i18n import get_lang, set_lang > > > Use the following in your project's lib/base.py file (and any other module > > that > > uses h): > > > import MYPROJ.lib.helpers as h > > > (where MYPROJ is the name of your project) instead of: > > > from pylons import h > > > pylons.h.error_for=error_for > > > -- > > > 4) This is in Trac, but it doesn't seem to automatically install Elixir > > > -- > > > 5) This is in Trac, but it's no obvious how to create a database. > > > It looks like folks want to use migrate. Will this ship with the > > distribution (and be callable from paster)? Is this how we should > > create tables? In the meantime, should we d/l it ourselves? > > > --- > > > 6) It's not super-obvious where/how to create your model and reference > > it in the controller. > > > -- > > > 7) Saying you want identity doesn't seem to do much. Also, from the > > identity docs, it's not clear how you register a new user (and then > > have it set them to logged it). Ideally, registration would support > > email auth, etc. > > > Keep up the good work & Thanks! > > -- > 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 [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 -~----------~----~----~----~------~----~------~--~---
