I agree with Pat, I'd rather not go this route as it exposes a lot of implementation details of the ui tags to the developer. Also, not every ui theme will have a controlheader/controlfooter. It's an implementation detail of the xhtml tags.

That said, I believe there's still a way for you to get the functionality you need. The VelocityEngine is configured to search for content from two sources, file, then class which means that if you wanted to override controlheader.vm and/or controlfooter.vm, you could write your own

/templates/xhtml/controlheader.vm
/templates/xhtml/controlfooter.vm

and place them in the web path (which gets searched before the class path).

M

Cameron Braid wrote:
What about something in the middle:

Indroduce a tag attribute called "controlTemplate" that is optional.

If the controlTemplate value is not set, use the value "default" .. i.e.
default-header.vm and default-footer.vm.
If it is set, use it in determining the filed : ${controlTemplate}-header.vm
and ${controlTemplate}-footer.vm files

Also provide a special case called "none" ... Though this can probably be
implemented by none-header.vm and none-footer.vm :)

That way, the default set of UI templates can be used without having to hack
them up to make them work with a custom layout.

..cam..



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pat Lightbody
Sent: Saturday, 31 May 2003 8:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Splitting up controlheader



This seems like a very grainular approach for a need that doesn't come up too often. Might just be easier to leave these minor customizations up to the developer. I'd lean towards not doing this...


-Pat

----- Original Message -----
From: "BOGAERT Mathias" <[EMAIL PROTECTED]>
To: "Opensymphony-Webwork (E-mail)" <[EMAIL PROTECTED]>
Sent: Friday, May 30, 2003 1:51 AM
Subject: [OS-webwork] Splitting up controlheader




Hi guys,

In order to facilitate changing the UI tag templates, I suggest we split

up


controlheader. A tag will be rendered using:

- include row-header
- include label-header
- include label
- include label-footer
- include widget-header
- include widget
- include widget-footer
- include row-footer

This way, if one would like to use for example only CSS templates, only

the


header and footers need to be changed.
Does this sound like a good idea?

Mathias


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Opensymphony-webwork mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-> 6916-5


_______________________________________________

Opensymphony-webwork mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork






-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork





------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to