Cool!  I'll be happy to set it up and give feedback once it's committed.

FTR, I'm also working on improving the repoze.who docs so they don't suck quite
as much:

http://plope.com/static/misc/sphinxtest/intro.html

A section which documents repoze.who and various other repoze libs/middleware
will go up on repoze.org as soon as we figure out how to collapse all the
individual package docs into something that can be shown as a single thing.

- C


Florent Aide wrote:
> Hi Mark, Hi Chris, Hi all,
> 
> I have a working repoze.who plugin that at least works for checking
> permissions and usernames against the TG1 identity tables.
> I have also a demo tg2 app that is configured to used the said plugin.
> 
> Where do you think that I could check this code in our SVN. I propose
> to check this in projects under
> 
> tgrepoze/trunk
> 
> For the demo application I am not sure this is a good idea to put it
> in the SVN... I could send it to some wiki page + some info on how to
> configure your own tg2 app to use this repoze plugin.
> Once we get this settled I'd like some comments from Chris because I
> am sure I hacked through the code like a barbarian and did some bad
> things.
> 
> Now we will have to choose something else: is it possible to have a
> quickstart template with identity activated (so has to create a repoze
> enable quickstarted app). If so just give me infos where I could hack
> this and I'll make sure our users can quickstart repoze protected
> apps.
> 
> And sorry for the delay, I intended to finish this sooner, but real
> life is such a pain sometimes... I'm sure you know that too :)
> 
> Florent Aide
> 



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

Reply via email to