You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Shan Gopalakrishnan <sg...@cisco.com> on 2002/04/26 06:57:43 UTC

output html

Hello team

Are there any templates assoicated to the overall PSML?.  How we control 
the html that is getting generated
for the overall PSML which includes all the portlets.  I understand there 
is a possibility to assign a template
for each portlet . but I'm looking to control the html page that is getting 
generated for the entire psml after
the portlets assembly?.

- Shan


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: output html

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
Thank you David.  Appreciate all your information.  I will read thru' and 
check back with you if any questions.

- Shan

t 02:07 PM 4/26/2002 -0700, David Sean Taylor wrote:
>Shan,
>
> > where is the definition of  $screen_placeholder.?
>
>That's an object put into the 'context' for Velocity by Turbine when
>creating the layout.
>Not sure if you are aware of the Velocity context or not, if not
>recommend reading up on it, nice concept:
>
>http://jakarta.apache.org/turbine/turbine-2/howto/context-howto.html
>
>The context is used to pull Java objects into your velocity template.
>Also see:
>
>http://jakarta.apache.org/turbine/turbine-2/howto/pullmodel-howto.html
>
>Also reference any of the vm templates in Jetspeed.
>Lots of examples of pulling Java objects from the context, and using
>'Pull Tools'
>
> > If it is
> > request to send a custom screen thru' the request, how do we
> > do that?. any inputs on this will help me.  I will also go
>
>Check out the $jslink examples for how to do this from a .vm page
>
> > -----Original Message-----
> > From: Shan Gopalakrishnan [mailto:sgopalak@cisco.com]
> > Sent: Friday, April 26, 2002 1:29 PM
> > To: Jetspeed Users List
> > Subject: RE: output html
> >
> >
> > David, this is a awesome explanation. Thanks a lot.
> >   But that made me curious to ask little more question.
> >
> > On the below description
> >
> >  >>The PSML is placed into a Turbine screen(template) by the
> > layout, with  >>optional navigations.
> >  >>          $screen_placeholder
> >  >>The screen placeholder calls the specified screen in the
> > request, or the  >>default screen setup in the TR.p  >>Our
> > default screen will display the requested portal page.
> >
> > where is the definition of  $screen_placeholder.?  If it is
> > request to send a custom screen thru' the request, how do we
> > do that?. any inputs on this will help me.  I will also go
> > thru' turbine docs.
> >
> > - Shan
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:jetspeed-user-> unsubscribe@jakarta.apache.org>
> > For
> > additional commands,
> > e-mail: <ma...@jakarta.apache.org>
> >
> >
>
>
>
>--
>To unsubscribe, 
>e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: 
><ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: output html

Posted by David Sean Taylor <da...@bluesunrise.com>.
Shan,

> where is the definition of  $screen_placeholder.? 

That's an object put into the 'context' for Velocity by Turbine when
creating the layout.
Not sure if you are aware of the Velocity context or not, if not
recommend reading up on it, nice concept:

http://jakarta.apache.org/turbine/turbine-2/howto/context-howto.html

The context is used to pull Java objects into your velocity template.
Also see:

http://jakarta.apache.org/turbine/turbine-2/howto/pullmodel-howto.html

Also reference any of the vm templates in Jetspeed.
Lots of examples of pulling Java objects from the context, and using
'Pull Tools'

> If it is 
> request to send a custom screen thru' the request, how do we 
> do that?. any inputs on this will help me.  I will also go 

Check out the $jslink examples for how to do this from a .vm page

> -----Original Message-----
> From: Shan Gopalakrishnan [mailto:sgopalak@cisco.com] 
> Sent: Friday, April 26, 2002 1:29 PM
> To: Jetspeed Users List
> Subject: RE: output html
> 
> 
> David, this is a awesome explanation. Thanks a lot.
>   But that made me curious to ask little more question.
> 
> On the below description
> 
>  >>The PSML is placed into a Turbine screen(template) by the 
> layout, with  >>optional navigations.
>  >>          $screen_placeholder
>  >>The screen placeholder calls the specified screen in the 
> request, or the  >>default screen setup in the TR.p  >>Our 
> default screen will display the requested portal page.
> 
> where is the definition of  $screen_placeholder.?  If it is 
> request to send a custom screen thru' the request, how do we 
> do that?. any inputs on this will help me.  I will also go 
> thru' turbine docs.
> 
> - Shan
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:jetspeed-user-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <ma...@jakarta.apache.org>
> 
> 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: output html

Posted by Shan Gopalakrishnan <sg...@cisco.com>.
David, this is a awesome explanation. Thanks a lot.
  But that made me curious to ask little more question.

On the below description

 >>The PSML is placed into a Turbine screen(template) by the layout, with
 >>optional navigations.
 >>          $screen_placeholder
 >>The screen placeholder calls the specified screen in the request, or the
 >>default screen setup in the TR.p
 >>Our default screen will display the requested portal page.

where is the definition of  $screen_placeholder.?  If it is request to send a
custom screen thru' the request, how do we do that?. any inputs on this
will help me.  I will also go thru' turbine docs.

- Shan


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: output html

Posted by David Sean Taylor <da...@bluesunrise.com>.
I'll try to give a brief overview, but this is all described in the docs
http://jakarta.apache.org/jetspeed

PSML controls the layout of where portlets are placed in the portal
page.
It is not a template, but an XML file.
Take a look at the anonymous PSML file found in the distribution
/webapps/WEB-INF/psml/anon/html

<portlets xmlns="http://xml.apache.org/jetspeed/2000/psml">
    <metainfo>
      <title>Default Jetspeed page (for default locale)</title>
    </metainfo>

  <control name="TabControl"/>

  <controller name="CardPortletController">
    <parameter name="parameter" value="pane"/>
  </controller>

  <skin name="orange-grey"/>

  <portlets>
    <controller name="RowColumnPortletController">
      <parameter name="sizes" value="66%,34%"/>
      <parameter name="mode" value="row"/>    
    </controller>

The page is defined as a collection of 'portlets'.
Each collection can have a controller and control.
The controllers and controls are best defined using templates (either
Velocity or JSPs)
Look in the distribution under /webapps/WEB-INF/templates/vm/controllers
and /webapps/WEB-INF/templates/vm/controls


Controllers determine how portlets are placed
 within a portlet set for a given media type (html,wml...)
There several predefined controllers distributed with jetspeed, such as
single column, multicolumn, and in the case above, a Card controller,
which allows for portlets sets to be 'stacked' like cards.
The controllers are defined in a system registry under
/webapps/WEB-INF/conf/controllers.xreg.

Controls are also templates, and are decorators around the portlet. They
can be used to give portlets common look and feel such as Title bars,
Tab titles, Menu titles. Take a look at the distributed vm files.
All controls are defined in the controls.xreg file. Controls defined for
a <portlets> set are applied to all portlets in the its collection. If
no control is defined, it falls back to the control defined for a
portlet entry or to the default control in the JR.p.

Portlet entries(instances) are also placed in the PSML file , and it can
also have a specific control.

      <entry
parent="http://jakarta.apache.org/jetspeed/channels/jetspeed.rss">
        <control name="ClearPortletControl"/>
      </entry>

In theory, you shouldn't have to know about the XML details, since you
can use our Customizer to layout a PSML file for you.

> for each portlet . but I'm looking to control the html page 
> that is getting 
> generated for the entire psml after
> the portlets assembly?.

The overall page is determined by the layout.
Layouts, screens, navigations and actions are all Turbine actions.
Reference the Turbine docs for more details, or I can go into more
detail on how that works if you'd like.

The overall 'layout' of a Jetspeed page is determined by Turbines
modules.
The layout determines to entire page. Look at
/webapps/WEB-INF/templates/vm/layouts/html/default.vm.
The entire default layout is defined here. Layouts are auto-associated
with requested screens(templates).
The PSML is placed into a Turbine screen(template) by the layout, with
optional navigations.

          $screen_placeholder 

The screen placeholder calls the specified screen in the request, or the
default screen setup in the TR.p
Our default screen will display the requested portal page.


> -----Original Message-----
> From: Shan Gopalakrishnan [mailto:sgopalak@cisco.com] 
> Sent: Thursday, April 25, 2002 9:58 PM
> To: Jetspeed Users List
> Subject: output html
> Importance: High
> 
> 
> Hello team
> 
> Are there any templates assoicated to the overall PSML?.  How 
> we control 
> the html that is getting generated
> for the overall PSML which includes all the portlets.  I 
> understand there 
> is a possibility to assign a template
> for each portlet . but I'm looking to control the html page 
> that is getting 
> generated for the entire psml after
> the portlets assembly?.
> 
> - Shan
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:jetspeed-user-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <ma...@jakarta.apache.org>
> 
> 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>