At 07:48 01/30/01, David Sean Taylor wrote:
>After several reads, it is taking me some time to understand this, but I get
>the overall concept, but Im a little fuzzy in the details.
>
>I've also been looking at the new Turbine Pull Service.
>You can find it in the cvs head at org.apache.turbine.services.pull
>Also see: http://java.apache.org/turbine/pullmodel.html
>It appears a little thin, but I like the concept very much.
>
>The pull model, in my interpretation, is a way to bring an object model
>directly into template pages.
>This will allow designers to access, or pull, objects and their attributes
>directly in a template page, whether it be Velocity, WebMacro, JSP,...
What I'm worrying about is that the work of web designers get mixed up with
those of progammers: A web designer shouldn't really have to care about
programming and everything that the toolbox provides needs to be hidden
behind a *very* simple interface (like JspTags). It has to be made sure
that no business logic find it's way into the templates. All business logic
should be executed by actions that put their results in the template
context, the templates should only care about reading and rendering these
results and about the "page flow". I.e. there should be only a very spartan
"API" with e.g. methods to lookup/generate/rewrite appropriate links, but
it shouldn't provide "a way back" into the portal (e.g. no methods to
access the user object or other "mighty" objects).
>A Toolbox is a collection of application tools. Im not sure if this is a
>hierachy of tools, like java classes, or simply a Map
>
>Application tools remind me of beans in JSPs...
>It not clear how the lifetime or state of these tools will be managed.
>
>The important thing that I get from this is Jetspeed will provide
>application tools that can be 'pulled' into layouts (template pages), such
>as panes, layout and window managers, links and actions. I assume these
>tools will work in JSP as well as Velocity.
>
>****************************************************************************
>******
>The 'Portlet API'
>
>I haven't seen much activity in this area lately...
Thomas Boehme has been working on it. I should commit the JavaDocs by
tomorrow, probably earlier.
>How does the Layout system relate to the work being done on the portlet api?
Not so much I think. The API offers interfaces that portlets can implement
in order to offer modes for configuration, edit or help. The window manager
will use this to decide which (window) buttons are to be displayed.
Furthermore, there is an interface to notify the portlet that it has been
minimized, maximized, closed, etc. which will of course have an impact on
the portlets rendering.
As a third thing, the client mode/request type/client capabilities will be
accessible by the portlet in order to deliver the type content that the
client requested.
However, the portlets shouldn't care about how they are arranged by the
layout, how there skin looks like, if and what navigation bars are
displayed or wether they are alone on a page or with many others. So this
won't be reflected by the portlet API.
--> The layout system will ask the portlets through the Portlet API to
generate their output and the portlets will have the possibility to access
services trough the portal API. These services are provided by the portal
(engine), but not really the layout part of it.
>Should the portlet api be accessible in the toolbox?
>Perhaps not the entire api, but just the relevant parts, or is it something
>entirely different.
>
>****************************************************************************
>******
>
>It would help to make some comparisons and contrast:
>
>Is a Window Manager something like a 'control'?
>Is a Layout Manager something like a 'controller'?
>Is a Configuration like a psml resource(s)?
>Is a Pane roughly equivalent to a colection of portlets that may be grouped
>onto a layout, like the jetspeed:ecsscreen tag in the current impl?
>Its not clear what a screenlet is.
>
>
>
>
>
>
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Search: <http://www.mail-archive.com/[email protected]/>
>List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
