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]
