Em Sábado 22 Abril 2006 14:52, jvanasco escreveu:
>
> Someone said that there are upcoming changes - are these in SVN trunk
> now, or are they forthcoming.  I'm wondering what i should be patching
> against.

Always against the trunk.  Specially because there's no stable release that 
includes identity yet.

> it seems to me like thats the thought process behind a lot of whats in
> Identity - its very much tailored to a specific app, and not abstracted
> enough into a general app

That's weird because Jeff Watkins -- the author of Identity -- don't know 
anything about my apps and don't even know how many I've written.  Other 
people seem to have no problems with it as well.

> And what I'm saying is that we should reduce TG_User as much as
> possible, so everyone just extends it ( which 9/10 people will already
> do )

Could you show the representativeness of these numbers?  Where did you get 
"9/10" from?  This list has more than 1500 users and I haven't seen, for 
example, 9/10 of them disagreeing with the current implementation.

(Your quotation is very messy, please take care not to attribute something to 
the wrong people...)

> You get 2 tables : your table - useraccount , and the default tg_user.
>  to bypass the NotNulls, you can md5_hex(emailaddress)[0:16] into a
> userid , or "[EMAIL PROTECTED]" % (username) into an email.  personally,
> i hate that.

You don't need to do that if you don't like it.  There are docs explaining how 
to create your own classes and there are options at the configuration files 
to use them.  Just do it (do I have to attribute it to Nike? ;-))

> i just want to make this simple because right now, its not.  identity
> should be as lightweight as possible then be extended.  the current
> design basically says "either use this model or learn a whole lot about
> our internals to hook your own classes into it".

The current design is a suggestion that the author thought would be useful.

There are step by step docs showing how to create a new model.  You found that 
you needed to go further to use them?  What did you missed from them?

The current module is very flexible and allows alternative providers -- for 
LDAP, SSO, SQL, etc. -- so that it can be used together with other projects 
or tied together with other technologies.

I still believe that you're lacking reading more about how TG work and how 
each of its parts work.  Unfortunately, to get where we are now, there were 
lots of changes and the development pace was very fast so docs are starting 
to become available now.  The source is your best bet to get up to date docs.  
This will be changed soon, fortunately.


-- 
Jorge Godoy      <[EMAIL PROTECTED]>


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

Reply via email to