Hi Raphael,
I have been looking at the Page api and so far it looks great. The one concern I have
is I see some mention of a skin registry. IMOHO, I don't think we need a skin
registry. In fact I did away with it in my custom J1 implementation and replaced it
with a theme/skin combination very similar to IBM WPS.
The Theme controls the style sheet that is used and also contains its own centralized
repository of resources like images, flash, html and has a built-in look up mechanism
for finding these resources. The theme also contains its own set of controls
(jsp/velocity templates) for tab layouts, menu layouts, along with a "default"
template with is the actual encompassing page's HTML. The theme designer can easily
add fragments to his or her custom theme without having to modify the default
fragments that come with Jetspeed.
Lookups are done in a most-specific to most-general manner using a modified version of
the template locator from J1. This means that the themes are entirely localized and
can be easily made to support multiple content-types by simply having fragments and
resources in the correct folders.
You can also define images and fragments within the base "themes" "themes/en" and
"themes/en/html" directories which will be used by the lookup mechanism if the
resource(s) could not be found in a specific theme.
Example directory structure for a theme.
themes
|
|--html
|
|--en
|
|--theme1
|
|-Style.css
|-default.vm
|-images
|
|-maximize.gif
|-minimize.gif
Skins work essentially the same way except for the fact that they "should" use as much
information provided by theme as possible, like the images for action buttons, etc.
What is really nice is that a theme can define resources for the skin(s) to use so
that the skin always match the color scheme/look and feel of the "enclosing" theme.
For example, if you have a title bar background image for your skin called
skin1bkimage.gif. A theme with a green color scheme could contain a skin1bkimage.gif
that is green and another theme with a blue color could have a skin1bkimage.gif that
is blue. At this point the skin fragments retrieve the image resource named
"skin1bkimage" from the theme that encloses it so you can easily have skins that
always match the current theme by simply creating the right images and putting them
into the respective theme.
Let me know what you think.
*===================================*
* Scott T Weaver������������������� *
* Jakarta Jetspeed Portal Project�� *
* [EMAIL PROTECTED] *
*===================================*
�
> -----Original Message-----
> From: Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]
> Sent: Sunday, August 03, 2003 10:25 AM
> To: '[EMAIL PROTECTED]'
> Subject: [J2] New Page API committed to CVS
>
>
> I've just committed a new simplified Page object model API
> to the Jetspeed 2 API.
> The goal of this object model is to replace the current PSML
> API to have a somewhat more programmer friendly API, simpler
>
> to implement in a SQL format and with proper separation
> between page description and customization and portlet
> customization.
>
> I'm going to finalizee/refine a PageManager service with
> an XML and OJB implementation in the few coming days.
>
> I'd value any feedback on the object model, especially an
> shortcomings in the interface.
>
> --
> Rapha�l Luta - [EMAIL PROTECTED]
> Vivendi Universal Networks - Paris
>
> **********************************************
> Vivendi Universal - HTTP://www.vivendiUniversal.com:
>
> The information transmitted is intended only for the person or entity
> to which it is addressed and may contain confidential and/or privileged
> material of Vivendi Universal which is for the exclusive use of the
> individual designated above as the recipient. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
>
> this information by persons or entities other than the intended recipient
>
> is prohibited. If you received this in error, please contact immediately
>
> the sender by returning e-mail and delete the material from any computer.
>
> If you are not the specified recipient, you are hereby notified that all
>
> disclosure, reproduction, distribution or action taken on the basis of
> this
>
> message is prohibited.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
