On 16 okt 2008, at 17:35, Martin Aspeli wrote:
- Create a "site wide" portlet category for portlets that should show
on all pages (unless blocked).
Then how do you unblock them? If I have such a global portlet and at
some point a folder blocks the portlets and redefines them and in a
subfolder you want to have that global portlet showing up again, how
do you do that? Is it suddenly an addable portlet while it used to be
a global portlet?
Currently, people have to use contextual
portlets at the root of the site for this, which gets cumbersome since
if you block them in one folder, you need to re-add all portlets in
subfolders.
As wichert stated, this the argument here is that only the option to
block all the portlets is actually causing the cumbersomeness here.
For role-inheritance you see a similar thing but there the reason is
security related and with a bit of though you will realize it is the
only way to do it. I'm not convinced that you can't have a scheme of
blocking portlet on an individual basis. Perhaps with a few UI tweaks
this is easy to use. Like when you remove a portlet in the manager you
will be asked to remove it everywhere (up that chain) or just here.
- Improve the contextual "manage portlets" screen so that you can see
what portlets will disappear/appear when you block/unblock.
Sounds good. At least.. if you mean that you can see which portlets
are there but blocked. (I'm currently working on a design for the
sharing page that also does this properly).
- Add a setting (actually, an annotation) to each individual portlet
assignment that determines whether it is shown in subfolders or not.
This will probably need to default to true, at least for migrated
sites,
but may be better off as defaulting to false.
I'm not sure what the default would be. Initially I'd think default to
True.
Anyway, this setting lessens the need for a way to block individual
portlets a little bit. It's not the same though.
This will solve the
problem of "I want this portlet in this folder, but not all
sub-folders". Currently, you need to go and block contextual
portlets in
each sub-folder, which is a pain.
Each of these could be implemented separately, although they do go
hand
in hand.
Cheers,
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
