Re: [Framework-Team] PLIP 244: Portlet management improvements
… incremental improvements to plone.app.portlets. We'd like to propose this for Plone 3.3: http://plone.org/products/plone/roadmap/244 Good discussion and voting on that one. Thanks. I'd love to see greater flexibility and ease of use, it's (debatably) very difficult for newcomers to get their heads around management of portlets. I think it needs not only: * new way(s) of achieving the desired result, with _plenty_ of user testing but also * pruning some of the more traditional/complex approaches and/or documentation. -- and the latter would break a 3.x rule. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 244: Portlet management improvements
On Thu, Oct 16, 2008 at 17:35, Martin Aspeli <[EMAIL PROTECTED]> wrote: > Ricardo Alves has been working (with me providing some guidance) on some > incremental improvements to plone.app.portlets. We'd like to propose this > for Plone 3.3: > > http://plone.org/products/plone/roadmap/244 +1 from me. -- Martijn Pieters ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 244: Portlet management improvements
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
Re: [Framework-Team] PLIP 244: Portlet management improvements
Martin Aspeli wrote: Hi all, Ricardo Alves has been working (with me providing some guidance) on some incremental improvements to plone.app.portlets. We'd like to propose this for Plone 3.3: http://plone.org/products/plone/roadmap/244 +1 on the topic as such. But as Wichert and Alex have pointed out the control of blocking/inheriting might need some further discussion to figure out how to get it right. I too would prefer if we wouldn't introduce too many different ways to effectively do the same things over time just because the first attempt falls short in some way. To Jon's remark: of course this would be a great feature and if Ricardo and Martin could get that supported this would be truly great. But let's consider what we have now first. There will always be room for improvements. Raphael The key suggestions are: - Create a "site wide" portlet category for portlets that should show on all pages (unless blocked). 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. - Improve the contextual "manage portlets" screen so that you can see what portlets will disappear/appear when you block/unblock. - 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. 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 ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 244: Portlet management improvements
Previously Martin Aspeli wrote: > - Create a "site wide" portlet category for portlets that should show > on all pages (unless blocked). 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. This feels like a workaround for the fact that you can not selectively block portlets. I would prefer a method where you can both block individual portlets, and block only for the current object is, similar to how you propose a flag to only show a portlet in the current object. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 244: Portlet management improvements
+1 from me The way I understand the proposed changes they are not breaking backwards compatibility, but simply make it easier to achieve already existing functionality. also +1 on the idea of making portlet assignments browser layer dependant. that's a feature i often find a need for. cheers, tom On 16.10.2008, at 17:35, Martin Aspeli wrote: Hi all, Ricardo Alves has been working (with me providing some guidance) on some incremental improvements to plone.app.portlets. We'd like to propose this for Plone 3.3: http://plone.org/products/plone/roadmap/244 The key suggestions are: - Create a "site wide" portlet category for portlets that should show on all pages (unless blocked). 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. - Improve the contextual "manage portlets" screen so that you can see what portlets will disappear/appear when you block/unblock. - 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. 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
[Framework-Team] PLIP 244: Portlet management improvements
Hi all, Ricardo Alves has been working (with me providing some guidance) on some incremental improvements to plone.app.portlets. We'd like to propose this for Plone 3.3: http://plone.org/products/plone/roadmap/244 The key suggestions are: - Create a "site wide" portlet category for portlets that should show on all pages (unless blocked). 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. - Improve the contextual "manage portlets" screen so that you can see what portlets will disappear/appear when you block/unblock. - 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. 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
