> So, we definitely don't want our own ORM, or template system, and we > probably don't need our own authentication middleware, but I'd doubt > that a user-registration module would be worth making framework > neutral, since it will have to have templates, depend directly on the > ORM, and it would be very hard indeed to abstract all of that away. > And I doubt that the component would really grown non TG2 users. So, > it's all something that we have to deal with for each component we > create.
Hmm, this sounds very similar to a problem I had to solve in DBSprockets to make it work the way I wanted. Maybe I should release a toolset which makes it possible to abstract concepts like Provider (ORM), Widgets, Validation, etc. I'd love to see Authority running on ZODB. -chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
