> > > I guess one area of confusion right now is what the role of > the various > mapper choices are. It would be great to have some form of > unified api > for the core components IMO, like being able to use identity > with > similar calls, so that if somebody starts using a tutorial on > session/identities/widgets, whatever, they can count on it > "just > working" with nothing more than a difference in what they > import. > > huh? how can you have the same api for two totally different > components?
Take identity for example. Is there any reason not to have a set of methods and a table structure that look identical to the user for things like adding and removing a user to a permission group? At the moment with SO we use group.addUser(user). No reason the exact same syntax couldn't be supported in SA by adding an addUser method to the group class. SA is so flexible in this regard that I don't see why we couldn't do that sort of thing quite a bit. Iain > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
