Hi, Martin et. al! Warning---I've been stuck three days with weather and
canceled flights in different time zones, trying to leave for Brazil for
my vacation, so please excuse any grumpiness that shines through because
of this ordeal! :D
Response below:
On 7/19/2014 10:14 AM, Martin Grigorov wrote:
...
Try to create a reusable Behavior that:
1) by default does what Wicket 6.x does (i.e. <a> -> <span>, wrap in <em>)
2) optionally prevents 1)
3) optionally adds a special class to the tag
4) optionally adds disabled="disabled" to the tag
5) optionally just removes 'href' from <a> (as per W3C recommendation)
6) is open enough so that a sub-class does something custom
It will be a big and rather complex Behavior which will try to do many
things and an application will use just of them.
Ack! I completely agree! But who proposed a behavior that does all that?
I didn't!
I prefer the Unix-style: do 1 thing and do it as simple as possible. If
second thing is needed then create a second tool (i.e. behavior)
Exactly! Wicket allows behaviors to work together, right? So we needs
lots of little simple behaviors that do their job well that can be mixed
and matched as the developer desires.
As I mentioned I'm tired and grumpy because of the flight. Give me a few
days (or maybe after my vacation this week) and I'll create a JIRA,
create some sub-tasks on it, and add some patches or do a pull request
or whatever, now that I have Git working. If you like what I give you,
great. If you don't, you can throw them away.
Have a good weekend.
Garret
