The web pages returned from Jetspeed are essentially served by the Turbine servlet, following the Turbine framework. If you want to do more than add or remove portlets, I suggest spending some time with the Turbine documentation. Default.vm is a velocity "template" being used to render the "layout" in Turbine. What you and I see as the real content of a Jetspeed page is the Jetspeed "screen" rendered inside this Turbine layout. There are also Turbine "navigations" like top.vm and bottom.vm.
We took the route of extending the User object to include a number of additional objects for our particular implementation of Jetspeed, one of those being a style/template/skin for each user. We call it a "portal_template", and it's stored in our User table in the database backend we've hooked into Jetspeed. We only use one layout template (default.vm), but set a variable in the User object to define a relative path that points at directories in which we have the various images and .css files that make up a particular Portal Template. Jetspeed skins have been added into skin.xreg that correspond to each portal_template, so the finished product has a consistent look, and changing portal_template changes the whole portal's look. Hopefully this is helpful. Raphael has given you (and the rest of us; thanks Raphael) a great way to get at the PortletSkin from the Turbine layer, but given the way Jetspeed is implemented, it is a little like the tail wagging the dog :-) -----Original Message----- From: Akihiko [mailto:[EMAIL PROTECTED]] Sent: Monday, October 22, 2001 5:22 PM To: [EMAIL PROTECTED] Subject: RE: Skin support in top.vm Christopher, So let me see if I understand you correctly. I was already aware of "skins", but completely unaware of "templates". Templates are implemented in Turbine? I've found a few functions relating to templates during a search of the turbine documentation, but I'm not sure if they are what you have mentioned. Somehow I gather that you are dynamically changing the .css file that the portal uses. Are you doing that with something like setLayoutTemplate() from the runData object? In other words, do you have multiple "default.vm" files each pointing to a different .css file? That could be very useful. Am I way off base here? Thanks, Akihiko --- Christopher Abraham <[EMAIL PROTECTED]> wrote: > I think Akihiko is running into a similar confusion that we had early on in > using jetspeed: "skins" are implemented inside the Jetspeed portlet screen; > "templates" are implemented inside the Turbine layout (of which the Jetspeed > screen happens to be one component). > > In our case, we wanted "templates" and "skins" of predetermined pairings to > be kept in sync, so we extended the User object to hold a "PortalSkin" > string that identifies the relative path to a directory holding .css and > image files for the vm template, as well as setting the Jetspeed "skin" (in > our case, all portlets get the same skin and we're hiding the skin-chooser > in the customizer from the end-user). We set up a custom portlet that lets > administrators select the PortalSkin to display for their users (someday > we'll probably make this available to end-users, as well). > > -----Original Message----- > From: Paul Spencer [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 22, 2001 1:40 PM > To: [EMAIL PROTECTED] > Subject: Re: Skin support in top.vm > > > Akihiko, > I am not sure I follow the question. In the case of the navigation > bars, their is no skin (i.e. $skin.Name is undefined). You can edit > top.vm to change the look, but I do not know how to access the skin for > the top level portlet. > > What would the "skin" be applied to? > > Is their a reason the "content" is not in a Portlet? > > Paul Spencer > > Akihiko wrote: > > > > Is there any way to access skin information from top.vm, or any other > > navigation for that matter? It seems that skins are associated with > portlets, > > not users which allows some very fine grained skinning. However, I've not > found > > a way to keep the top and bottom navigations in sync with the top level > skin. > > > > Has anyone found a way to do this? > > > > Thanks! > > Akihiko > > > > __________________________________________________ > > Do You Yahoo!? > > Make a great connection at Yahoo! Personals. > > http://personals.yahoo.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
