Neeme Praks wrote:
<snip>
> > We are still in a place where this isn't totally possible. We need to
> > build in the 'introspection'/profiler support.
>
> how about defining a strategy in code and leave the actual
> implementation of the strategy to XSLT stylesheet? Then could select
> appropriate stylesheet depending on media. I believe Rapha�l already
> mentioned something like this?
I see what you are saying.... it won't really work:
If the user connects with a uplevel client IE/Netscape they can
configure their uplevel portal. In this situation there is NO reason
they can't also configure their WAP version too. 'Preview' wouldn't
really work but they could sure configure a Portal :)
If we just used XSLT to provide a single PSML file we can't provide
multiple media Portals. Jetspeed will use Cocoon and for each media it
will use another stylesheet and this will write a PSML file specific to
the current device. When they connect with another device they won't
have a correct Portal layout. In this config we need to support
multiple devices within one PSML file.
<snip>
> well some more food for thought: let's say that I have several top level
> portletsets that represent different services:
> * email
> * contacts
> * calendar
> * alerts
> * events
> * etc...
>
> In html, I render a toolbar for these services at the top:
> email | contacts | calendar | alerts | events | etc...
I wanted to do this with application="true" and the Turbine
navigation... later to be sitemap.
<snip>
> <media>WAP</media>
> ....
> </portlets>
> <portlets name="taskpad">
> <media>WAP</media>
> ....
> </portlets>
> </portlets>
> (BTW, how about renaming <portlets> tag into <portletset>? It would be
> more consistent with the code.)
+1... That or set. I will add this in TODO for 1.3
<snip>
> But besides checking portlet capabilities, there should also be a way of
> checking what the user wants. If he wants to see this set of portlets in
> his phone or not. You cannot just assume that the user will want to see
> the same portlets as in HTML, use contexts are very different.
Yes... I know. But by default we might want to allow this if it
supports both media. Then when they see this they can remove it.
> [snip]
>
> I have also been thinking about WML issues lately, I'm putting together
> a XML schema for our own site that would describe the page layout in a
> media-scalable way: so we could afterwards generate array of media
> formats from this: HTML, WML, Flash, etc.
So you can have Xdevice and Xmedia layout... seems like a good idea.
Does it scale well?
> (This is also the reason why I have been quite quiet lately, I still
> have on my TODO list some replies to this list... But probably they will
> happen next week...)
OK..
<snip>
--
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]
