Currently, skins do not support alternate templates. However, this can easily be achieved by defining a custom control and assigning to a portlet.
Controls can define a "theme" parameter which indicates which template to use to render the portlet. I can see 2 approaches for integrating this into skins. 1. Allow the skin to override the "theme" parameter of control the portlet is using. 2. Allow the skin to define its own control entirely. > hopefully the > api will be generic enough to handle any templating system a project > wishes > to use by doing a simple swap. I have just finished implementing the GenericMVCPortlet API within the current CVS head, most of which was donate by Todd Kuebler. It uses view processors to render a portlets view based on the type template language being used. This should help with the issue of abstracting the view layer completely. > please contact me for further implementation details if anyone is > interested in this idea. i think this would be a great addition to this > Portlet API before everything gets finalized. Sure, let me know what you have got in mind. *===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================* > -----Original Message----- > From: James H Nguyen [mailto:[EMAIL PROTECTED] > Sent: Monday, March 24, 2003 11:15 AM > To: [EMAIL PROTECTED] > Subject: Re: Portlet API Requirements > > > > > > i'm pretty sure someone might have brought this up already, but has anyone > thought about including some APIs to also handle skins selection? i've > seen > the way jetspeed currently handles skins, but it's not as fexible as i > thought it could be. > > for instance when i worked on a skins templating system for another open > source portal system, i allowed modules or portlets to define their own > set > of skins and if they are not defined, they would default to the system > skin. not only that, but skins where actually a set of html templates > used, > not just changing the css such as the current method. i could be wrong > though on the current method, but that's my impression from using the > jetspeed portal. some please correct me if i am incorrect, i would hope > that i am because it's what skins are suppose to be able to do.. define > it's own separate html template from the default system one. hopefully the > api will be generic enough to handle any templating system a project > wishes > to use by doing a simple swap. > > please contact me for further implementation details if anyone is > interested in this idea. i think this would be a great addition to this > Portlet API before everything gets finalized. > > thanks. > > james nguyen > ibm global services > ams enterprise application development > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
