To stay on topic, what about renaming SecuredResource to
SecuredController?
The former should still work but will issue a deprecation warning,
that's just to keep thing in a coherent state across TG since we are
using *Controller for every other thing.

Ciao
Michele

Jorge Godoy wrote:
> Alberto Valverde <[EMAIL PROTECTED]> writes:
>
> > Couldn't the login and logout methods from the quickstart
> > controllers.py template factored out into separate controllers? These
> > could be imported and attached so the initial code isn't bloated with
> > methods that might not be needed. I think it will be better for
> > beginners because it's less code to try to figure out what it means
> > in the initial skeleton.
>
> I prefer having things explicit.  Why not adding a doc string to those saying
> that they are there for indentity and can be used as is, overriden or even
> supressed if the user doesn't need it.
>
> > When you need this methods you could:
> >
> > from identity import LoginController, LogoutController
> >
> > class Root(...)
> >      login = LoginController()
> >      logout = LogoutController()
> >
> > or even a mixin-class that provides these methods:
> >
> > class Root(RootController, LoginLogoutController):
> >     ....
> >
>
> If some change is made, I definitely prefer the "widget-like" first option
> instead of the "mixin-class".  It has the same syntax that other controllers
> -- and fastdata -- have.
> 
> -- 
> Jorge Godoy      <[EMAIL PROTECTED]>


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to