burtonator wrote:
>
> Rapha�l Luta wrote:
> >
> > burtonator wrote:
> > >
> > > Mukul Paithane wrote:
> > > >
> > > > I like the idea for edit. I am not sure I understand the purpose of logging
> > > > in for being able to maximize ...
> > >
> > > Yes. I agree. I will put this code into CVS for getAllowEdit into
> > > AbstractPortlet.
> > >
> >
> > I disagree. This should be implemented in the PortletControl.
>
> I see your point. But a Portlet should be able to specify that it
> cannot be edited. The Control will just provide the UI for this.
>
Agreed, but I feel presenting the user with a cutomize button only if he's logged
in is part of the UI logic, not the portlet logic.
If you put this in the portlet, you're just tying all the components together
because the portlet depends on a spcific UI design, etc... (Actually, I don't
even think it's good to have getAllowEdit() in the portlet interface).
Beware on not building a too monolithic app.
> I really want to take the logic out of the Portlet interface and put
> this into PSML. This would remove both arguments.
>
Yes and no. I think it's good to find this in PSML but it bothers me that
if a Portlet REALLY doesn't want to be edited, the administrator will be able
to override this in PSML.
Another issue is that if we implement our plans of "shared" PSML files you
need to specify who can edit a given PSML.
"Editable" is an access right and should be defined in an ACL-type PSML element.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
