Rapha�l Luta wrote:
<snip>
>
> Maybe in the US, but I have a very nice Nokia GSM Phine with a large screen ;P
The are getting nice... http://www.nokia.com/phones/9110i/
<snip>
> Actually, in the PSML users don't deal with controllers, they deal exclusively with
> PortletSets. The controller is just a property of a specific set.
Yes... but the point is that this isn't really want the user cares
about.. They want to see how that set is rendered.
> > - User wants to add PortletX to a section on his screen.
>
> so far, so good
>
> > - At this point the Customizer where in the PSML document to place the
> > Portlet. It can't go by using the currently selected Portlets name/ID
> > because this may have been added twice within the document.
> >
> I don't understand these sentences, some words are missing or my English is
> failing me.
Maybe if I used proper English... must have been late. Let me rephrase:
- At this point the 'Customizer' needs to know where in the PSML
document to place the Portlet. It can't determine this by using the
currently selected Portlets name/ID because this may have been added
twice within the document.
> > This is why we need to use named sets (even if we just use numbers).
> > When the user selects a Portlet I can have it also select a set. This
> > way when the user selects 'Add Portlet' the Customizer knows correctly
> > what set he needs to add this to. The problem is that since PSML can
> > have theoretically nested <portlets> we can't figure this out without a
> > kludge :(
> >
>
> I'm not sure I understand you, but if we have a Portlet GUID system, since
> PortletSet are subclasses of Portlet, you can get a direct reference to a PortletSet
> whatever the nesting level...
ug.. yes. That would be correct. But if we use Cocoon to XSLT this
from PSML to a UI (which is what I wanted to do), Cocoon will never see
the PortletSet because it is in Java and not XML. It needs to be global
across XML and Java..
<snip>
> I'm waiting on your markup example to comment on this. I can think I can picture
> a way to write a Customizer covering most cases with the current PSML but if your
> solution is simpler it may be worth it, as long as we don't lose any functionality.
I looked at it... Everything seems to match up correctly. Do we need
<layout position="1"> (I mean just the position attribute). Can't we
just use the way it appears in the DOM?
This seems to bind layout to the set. I would rather just assume the
default.
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
