Rapha�l Luta wrote:
>
> burtonator wrote:
> > >
> > > Still not really sure what your point is. I believe you are saying that once a
>user
> > > has chosen a Portlet there's no easy way for the customizer to let him chose
> > > where he wants to put it. I thought my step by step process or XSLT transformed
>GUI
> > > described in my first reply would be enough.
> >
> > There are multiple PortletSets within a give PSML document... how can
> > the customizer figure out which one without some type of ID/name? :(
> >
>
> There's definitely a need for an ID, I agree.
Yes... I want to see this happen. I am going to write up a PROPOSAL
for a GUID/ID system within Jetspeed.
> > >
> > > Well, XML <portlets> <=> Java PortletSet just as XML <entry> <=> Java <portlet>,
> > > I don't see why we can't write the GUID in the PSML.
> >
> > I think we need to change <portlets> to <portletset> and <entry> to
> > <portlet>
> >
> > Thoughts?
> >
>
> The names were chosen because it avoided class name conflict in the code. If we
> have a <portlet> element Castor will create <package>.Portlet class which will be
> ambiguous to org.apache.jetspeed.portal.Portlet and thus we'll need to use
> the fully qualified names, which is a real pain. (Java doesn't seem to recognize
> "shortcut" import statements anymore)
yes... this is a good point. It is the same for PortletSet though...
This is a problem.
> > Also. If a human chooses the GUID it can't really be a GUID. We don't
> > have enough randomness for 128bit uniqueness :(
> >
>
> Why should a human chose a GUID ? When a PSML is first loaded any element without
> GUID can be assigned a GUID which'll be stored in the file...
OK... This isn't that bad. We will have to work out a mechanism that
will imediately write out this PSML if it doesn't have a GUID.
Also, Castor doesn't have PrettyPrint functionality just yet. Thus all
of our PSML will look terrible and you can't really edit it by hand :(
<snip>
> >
> > Yes. This is a good point. ug.
> >
> > It would be redundant. But maybe we can solve this by keeping the
> > layout and just using may different sets. Each for different layout and
> > different controllers to use.
> >
>
> I'm still waiting for your complete markup example, otherwise I can't really comment
> on its merit.
Give me until tomorrow or Wednesday.
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]
