… 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 t
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 m
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
sub
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 hav
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
+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.
c
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 portle
