Am 01.12.2006 um 10:03 schrieb Gerald Müllan:
Marcus,
please stay cool
ok, maybe I shouldn't check my email after having two zombies ;-)
, paul only wanted to told you that these kind of
questions should be post to user list only.
hmm, aren't we discussing development details?
Concerning your question; HtmlTabbedPaneRenderer is the right renderer
class where the changes have to take place. I don`t know what the
initially idea was behind why there are buttons rendered out. Maybe
because of having a tab = button and the possibilities to affect
the tab through styling. With links you have to provide a separate div
or something else which forms the button.
display:block should do the trick, e.g.
<a style="display:block" href="#">Link as a Block Level Element</a>
but I guess the button solution still has some advantages for
specific cases.
So, i am more or less sure that the change will not only be replacing
the button through a
commandLink. Maybe we should provide a new attribute in order to
switch between a button and a link tab.
ok. This sounds right.
What should the name and values of that attribute be?
submitMethod = "button"
submitMethod = "link"
What do you think?
cheers
Marcus
