Re: Portlets on Tapestry 4.1

2006-08-02 Thread Jesse Kuhnert
nal Message- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 02, 2006 6:24 PM To: Tapestry users Subject: Re: Portlets on Tapestry 4.1 Ok, I think I'm a little out of my element here. I can't honestly say I understand the day to day sort of development patterns tha

RE: Portlets on Tapestry 4.1

2006-08-02 Thread Epstein, Ezra
anks, Ezra Epstein -Original Message- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 02, 2006 6:24 PM To: Tapestry users Subject: Re: Portlets on Tapestry 4.1 Ok, I think I'm a little out of my element here. I can't honestly say I understand the day to day sort

Re: Portlets on Tapestry 4.1

2006-08-02 Thread Jesse Kuhnert
More importantly than that, we'd have a potential "situation" wrt ~other~ portlets also including javascript. It seems like something that you'd think would come up more often. I'd be interested in knowing if things like css/script includes have been addressed by anyone else in the portlet commun

Re: Portlets on Tapestry 4.1

2006-08-02 Thread Jesse Kuhnert
Ok, I think I'm a little out of my element here. I can't honestly say I understand the day to day sort of development patterns that people use with Tapestry portlets. Is there an equivalent idea to something containing each page? (ie something that handles stylesheets/ etc ?) Rather than tryin

Re: Portlets on Tapestry 4.1

2006-08-02 Thread Jesse Kuhnert
Hmm...Good question. I will answer with a documentation page. On 8/2/06, Epstein, Ezra <[EMAIL PROTECTED]> wrote: We want to move to 4.1 for our portlets. Reading up I find: "By default, the Shell component will include the core dojo javascript object dojo.js, as well as the new core Tapestry