Re: release preparation and JIRA, next release version

[Vitaly Baranovsky <vi...@gmail.com>]

> You can edit portlet defaults with the Portlet Application Manager
> This is the equivalent of "configure" mode PLT.A.2

It's not useful. Because non-technical users (such as marketing people or
sales manager) can't understand Portlet Application Manager. They don't know
names of preferences and they don't know ID's of portlet entities (they must
to read psml files to know ID's of portlet entities).

As far as I understand, no one (even programmers) can know ID's of portlet
entities without viewing psml files.


> I think that your requirements would fit in nicely with PLT.A.3
> "edit_defaults" mode
> And yes, lets work on this for the next release

Ok, it will be great!

2007/2/20, David Sean Taylor <da...@bluesunrise.com>:
>
>
> On Feb 20, 2007, at 2:03 AM, Vitaly Baranovsky wrote:
>
> >
> > There is "edit-defaults" custom portlet mode described in JSR-168.
> > This
> > means admins can edit defaults preferences thru graphical interface of
> > portlet in "edit-defaults" portlet mode, and other users can
> > overwrite this
> > preferences in "edit" mode (if they have appropriate permissions).
> > I think
> > it is a good use case. I've posted JIRA recorded once:
> > http://issues.apache.org/jira/browse/JS2-634
>
> You can edit portlet defaults with the Portlet Application Manager
> This is the equivalent of "configure" mode PLT.A.2
>
> I think that your requirements would fit in nicely with PLT.A.3
> "edit_defaults" mode
> And yes, lets work on this for the next release
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>


-- 
With best regards,
Vitaly Baranovsky