I agree.<br><br>UI for editing PAU is complex form anyway (for non-technical users). And it can't be universal enough to include into a framework, but only into CMS. Manage groups for users - from group's context - is universal but not convenient and not widely usable. Instead of this, manage groups for users - from user's context - is usable but its implementation highly depend on implementation of users' storage. And etc.<br>
<br>So configure PAU in setup-install handlers (or z3c.configuration adapters). And then write your custom needed form for manage groups for users.<br><br><div class="gmail_quote">2010/9/16 Baiju M <span dir="ltr"><<a href="mailto:baiju.m.mail@gmail.com">baiju.m.mail@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Thu, Sep 16, 2010 at 7:33 AM, Christopher Lozinski<br>
<<a href="mailto:lozinski@freerecruiting.com">lozinski@freerecruiting.com</a>> wrote:<br>
> One of the great ideas from the Plone world is that each user can self<br>
> register, they then have their own folder, where they can add content,<br>
> to be indexed by the ZCatalogs, and displayed as needed.<br>
><br>
> I need that whole chunk of software. Users can register themselves,<br>
> they can then log in and go to their folder, add content, and do the ZMI<br>
> thing of renaming content, deleting it, copying it, cutting it and<br>
> pasting it.<br>
<br>
</div>I am afraid, BlueBream can provide functionalities of a full fledged CMS.<br>
But there are some components which be used to build these functionalities<br>
like zope.pluggableauth: <a href="http://pypi.python.org/pypi/zope.pluggableauth" target="_blank">http://pypi.python.org/pypi/zope.pluggableauth</a><br>
You may also look at Part 4 of our tutorial to get started with authentication<br>
related things:<br>
<a href="http://bluebream.zope.org/doc/1.0/tutorial4.html" target="_blank">http://bluebream.zope.org/doc/1.0/tutorial4.html</a><br>
There is a self-registration community package:<br>
<a href="http://pypi.python.org/pypi/gocept.registration/0.3.0" target="_blank">http://pypi.python.org/pypi/gocept.registration/0.3.0</a><br>
<div class="im"><br>
> I know the ZMI has been removed from bluebream. I downloaded<br>
> ice.control. But it does not have the full folder capabilities. It<br>
> took me as a developer a while to understand it. It is really very developer centric.<br>
> What I need is the user interface for end users. Add Edit and delete content objects. It<br>
> seems to only have delete and rename. Not the other functions. So here<br>
> are some tools that might help me.<br>
><br>
> There is zope.app.undo<br>
><br>
> There is the zodb browser<br>
><br>
> There is p01.zmi<br>
><br>
> There is ztfy.zmi<br>
><br>
> THere is zope.app.basicskin<br>
><br>
> There is z3ext.portal, but it looks like the maintainer has taken a full time job in the US.<br>
<br>
</div>There is ZAM also:<br>
<a href="http://svn.zope.org/zam.demo/" target="_blank">http://svn.zope.org/zam.demo/</a><br>
<div class="im"><br>
> I think grok may have some of this stuff, I am not sure.<br>
><br>
> Is there any write up about how to go down this path. Do I need to go<br>
> to each site, review their limited docs, download and install and test<br>
> each interface. Surely there must be a better way.<br>
><br>
> I guess when I download BlueBream a whole bunch of decisions have been<br>
> made for me, but someone decided to yank the very useful ZMI. Makes me<br>
> question the other decisions which have been made.<br>
<br>
</div>Actually old ZMI is not removed, it is not enabled by default.<br>
If you want to add it back, include "zope.app.zcmlfiles"<br>
from "etc/site.zcml".<br>
<div class="im"><br>
> It would also be great if there were documentation somewhere about the<br>
> major architectural decisions made in designing BlueBream, ZTK and the<br>
> other ZTK based apps.<br>
><br>
> So what do I use for a basic ZMI? Really for content management?<br>
<br>
</div>BlueBream encourages file-system based development. So, the<br>
functionalities provided by various ZMIs are limited. For<br>
real content management, it is better to use a CMS system like z3ext<br>
or develop another on top of BB/ZTK.<br>
<br>
It looks like ZAM (<a href="http://svn.zope.org" target="_blank">http://svn.zope.org</a> - search for 'zam') provides<br>
a plugin architecture. You may extend it to add new functionalities<br>
to ZMI.<br>
<br>
The old ZMI design has some flaw, it register all views to "default" layer.<br>
And it has so many registrations which may not be required for all<br>
developers.<br>
<br>
Regards,<br>
<font color="#888888">Baiju M<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
bluebream mailing list<br>
<a href="mailto:bluebream@zope.org">bluebream@zope.org</a><br>
<a href="https://mail.zope.org/mailman/listinfo/bluebream" target="_blank">https://mail.zope.org/mailman/listinfo/bluebream</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ilshad R. Khabibullin<br><a href="http://astoon.zwiki.org">http://astoon.zwiki.org</a><br>+7 922 600 56 06<br>