How can I make my own template/design?

[Leandro Sinhorini <le...@gmail.com>]

Hi all,

I'm new in Jetspeed and I would like to customize the templates for my
application. I read the documentation, but I have not understood.

Do I have to change the templates in the Jetspeed installation? Or, can I
create another .war (web application) with new templates?

The second case would be perfect for me.

Tks

Re: How can I make my own template/design?

[David Sean Taylor <da...@bluesunrise.com>]

On Feb 7, 2007, at 11:10 AM, Leandro Sinhorini wrote:

> Hi all,
>
> I'm new in Jetspeed and I would like to customize the templates for my
> application. I read the documentation, but I have not understood.
>
> Do I have to change the templates in the Jetspeed installation? Or,  
> can I
> create another .war (web application) with new templates?
>
> The second case would be perfect for me.
>
> Tks

Layouts are implemented as portlets, so they must be packaged up and  
deployed like
any other portlet.

I'm sorry to say but the solution is not in as clear of a state as we  
would like to it to be.
If you want to write your own layouts distribution:

1. in the jetspeed-portlet.xml of your war file, tell Jetspeed that  
its a layout application

    <js:metadata name="layout-app">true</js:metadata>

See the XSD here:

http://portals.apache.org/jetspeed-2/2.1/schemas/jetspeed-portlet.xsd

2. The name of your war file must have the prefix "jetspeed-"
      This will tell Jetspeed that it is a local application

3. You will need to deploy it to the WEB-INF/deploy directory

4. You have to copy in the templates yourself. We currently do not  
support putting
     templates in the war file.  This is the part that is bad IMO.

    Templates must be copied into the WEB-INF/templates/layout/html  
directory
     I don't think it will take much to copy them over during  
deployment from the WAR file
    Problem is we don't have a lot of time to get this done for the  
upcoming release
    Recommend creating a JIRA issue, and, if you have time,  
implementing it...
    An even better solution would be to store the templates in the  
WAR, and not
   ever copy them over to WEB-INF/templates




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org