Stuart Belden wrote: > I just recently went through a similar process trying to integrate a new design (not > done myself) with Jetspeed. It was a beneficial process to fight my way through the > Turbine/Jetspeed rendering jungle. Just as an example, here are a couple screens of > the layout (only about 85% done). They're not mockups; Jetspeed did draw these and > it does all work. :)http://stumod.com/jetspeed/public.png > http://stumod.com/jetspeed/staff.png > > You will :probably: not have to write your own controller(s), but that'll depend a > lot on what sort of layout you're trying to accomplish. Here are a couple tips: > > - layouts/default.vm draws the <html> tag; start here. > - controls/jetspeed.vm gets called for each portlet on the page. > - controllers.xreg and controls.xreg can tell you what templates get called when > you're using a particular control/controller. >
Good. > > To answer a few of your questions: > - putting a nav portlet drawn by the framework up in the top nav area may be a > challenge. I would bet there is a solution that would work w/o using a portlet, > though. (a simple vm with $jslink()'s to other templates or psml for instance) > - Changing the menu from L to R is trivial. > I'll look into this. Doesn't psml imply portlet usage? > > I ended up having write a control to handle the left-hand submenu and a controller > to handle the nested tabs. Both were pretty simple deals, really. I'd also really > recommend gutting all of the table tags Jetspeed comes with and use css. It will > makes things a thousand times easier in the long run. > > hth, > stu > Thanks for your help. Tod --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
