Jeff Prickett <[EMAIL PROTECTED]> wrote:
> 
> 
> Hello All,
> 
> I just began work on the portlet version of the calendar since using
> turbine screens was -1'ed. Plus, i was running into some problems anyway 
> :(...

I don't know if it will be useful, but I have a portlet which you specify the
turbine screen, it eval's the screen to get the html and places it in the
portlet.  You can also pass parameters directly to the screen, which are
specified in the PSML file.  

We create our web applications in turbine.  Then we want to pull together all
these apps into an intranet portal and are using Jetspeed for that.  So in
some cases we have specific portlets, but others where we have a turbine
application, we just need that first screen to start the application.  Instead
of writing a portlet for each app, we just use this class.  Then after that
you are in the turbine application.

I put the class up here if your interested:

http://sites.netscape.com/ekkerbj/patches

> Anyway, what is everyones thoughts on associating actions with portlets.
> Should we 
> 
> Option 1. Should we create a PortletWithAction that has an Action 
> property subclass.
> 
> Option 2. Should we add an Action property directly onto the portlet.
> 
> Option 3. Should we let the programmer execute any actions he wishes
> inside the init() method
> 
> Option 4. Use the normal turbine action mechanism

[SNIPPED DESCRIPTION]

Seems like what we need is a way to take turbine screens and have them output
into their portal area.  Then the full power of turbine could be used and
jetspeed's power ( layouts, customization, etc ) would also be leveraged.  

Just rambling now,

jb


Jeff Brekke
mailto:[EMAIL PROTECTED]
http://sites.netscape.net/ekkerbj


____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at 
http://webmail.netscape.com.


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to