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 community? For example, the current delegate might optionally have to include a Compatibility checking sort of script to ensure that no other dojo or tapestry script librariers were already being included in the browser. If they were included we might then have to check versions and do "something" if they are found to be incompatible. (both dojo and tapestry include release version meta information in the js runtime, so we can write logic to check it fairly easily.) Thoughts ? On 8/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
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 trying to pull what I think is the right way out of my arse, can the community help me out a little here? ;) I do have one specific IRender "bean" sort of class that the @Shell component delegates the work of rendering the tapestry/dojo/browser debug configuration includes to. It can be found here: http://tapestry.apache.org/tapestry4.1/tapestry-framework/apidocs/org/apache/tapestry/dojo/AjaxShellDelegate.html . If the functionality this provides sounds somewhat palatable I can try refactoring the naming a little bit to eliminate the verbage of "Shell". (I'd like to remove AJAX as well...) On 8/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > 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 javascript object - > > core.js. This means that you don't have to worry about how to include > > dojo or Tapestry javascript on any of your pages, they will already be > > available." > > > > Of course, that's not the case for portlets. > > > > Is there a simple step-by-step how-to for those of us who don't > > (can't) use the Shell component. > > > > Thanks, > > > > Ezra Epstein > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. > -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
