You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Dahl, Sandra" <SD...@dvsAnalytics.com> on 2009/12/21 23:05:19 UTC
decorator project
I want to put decorations in a separate project using Jetspeed 2.2.1. I have successfully created and deployed a layout project with this directory structure:
css/
decorator-macros.vm
decorator.properties
footer.vm
header.vm
images/
The same theme also requires portlet decorators. Should a different project be created for portlet and layout decorators? What is the directory structure for the portlet decorator?
Thanks!
Sandi
________________________________
Confidentiality Notice:
The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader is not the intended recipient, or the employee, or the agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us by return email or telephone immediately. Thank you.
RE: decorator project
Posted by "Dahl, Sandra" <SD...@dvsAnalytics.com>.
Perfect. Thanks, Randy!
Sandi
-----Original Message-----
From: Randy Watler [mailto:watler@wispertel.net]
Sent: Monday, December 21, 2009 6:47 PM
To: Jetspeed Developers List
Subject: Re: decorator project
Sandi,
Yes, the projects are similarly structured. The system knows the
difference between the two decorators by these lines in the
decorator.properties file:
decorates=portlet
or
decorates=layout
Portlet layouts typically have one template named decorator.vm instead
of a header.vm and footer.vm templates found with layouts. Take a look
at the portlet decorators that are defined in the jetspeed distribution.
Note that the template is often "inherited" from the parent "base"
portlets decorator directory. You can do the same or define one native
to your portlet decorator.
Deployment of these projects is identical, (drop into WEB-INF/deploy).
HTH,
Randy
Dahl, Sandra wrote:
> I want to put decorations in a separate project using Jetspeed 2.2.1. I have successfully created and deployed a layout project with this directory structure:
> css/
> decorator-macros.vm
> decorator.properties
> footer.vm
> header.vm
> images/
>
> The same theme also requires portlet decorators. Should a different project be created for portlet and layout decorators? What is the directory structure for the portlet decorator?
>
> Thanks!
> Sandi
>
>
> ________________________________
> Confidentiality Notice:
> The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader is not the intended recipient, or the employee, or the agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us by return email or telephone immediately. Thank you.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Email secured by Check Point
Confidentiality Notice:
The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader is not the intended recipient, or the employee, or the agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us by return email or telephone immediately. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: decorator project
Posted by Randy Watler <wa...@wispertel.net>.
Sandi,
Yes, the projects are similarly structured. The system knows the
difference between the two decorators by these lines in the
decorator.properties file:
decorates=portlet
or
decorates=layout
Portlet layouts typically have one template named decorator.vm instead
of a header.vm and footer.vm templates found with layouts. Take a look
at the portlet decorators that are defined in the jetspeed distribution.
Note that the template is often "inherited" from the parent "base"
portlets decorator directory. You can do the same or define one native
to your portlet decorator.
Deployment of these projects is identical, (drop into WEB-INF/deploy).
HTH,
Randy
Dahl, Sandra wrote:
> I want to put decorations in a separate project using Jetspeed 2.2.1. I have successfully created and deployed a layout project with this directory structure:
> css/
> decorator-macros.vm
> decorator.properties
> footer.vm
> header.vm
> images/
>
> The same theme also requires portlet decorators. Should a different project be created for portlet and layout decorators? What is the directory structure for the portlet decorator?
>
> Thanks!
> Sandi
>
>
> ________________________________
> Confidentiality Notice:
> The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader is not the intended recipient, or the employee, or the agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us by return email or telephone immediately. Thank you.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org