One approach is to use css and background images. of course for that, I need to be able to specify the class or id of the butotn - which ad_formdoes not provide for.
So I added an element with the widget type = submit and used html to set the class.
VOila - it works. But wait - did I hear someone mention cross-platform compatibility issues?
Sure enough, IE on the mac stuffs up the button size and borders. But who uses ie on the mac any more? Trouble is, Safari ignores the background image css attribute on the button rendering an Aqua native button. Not too bad by itself, but it DOES honour the css size attributes, thus making the button far too small for the aqua button largesse and the button text (which gets truncated).
Back to the drawing board.
Can I use the input widget directly? Well, template::widget::input gets called ok, but with no attributes no matter how hard i try from within the ad_form block.
Is there an image widget? No - not too hard to write so I might do that.
The funny thing is that I really can't be the first person to want to do this - either an image for beauty's sake or actually as an imagemap.
SO has anyone done this? Or does anyone have any opinions about the best way for me to add this to the toolkit?
I would personally like to do two things:
1/ add an imagemap widget for imagemaps
2/ provide the ability to provide a triplet to -buttons indicating the third element is an image url