I don't think this is really practical(for Click at least): one can't
really compare apples to oranges.
Things that are very important for developers like: the ease of learn,
consistence, good documentation, speed, efficiency, etc. are not
really taken in consideration in that project. These are however the
main advantages of using Click :).
Olio implementations should benefit the greater Java community as there
will be at least some common ground to compare frameworks against.
Didn't you attempt to port the Stripes bugzooky example to compare the
two frameworks? What is the difference between that and an Olio example?
Well, that was just a "one to one" comparison. That original example was
supposed to express the "advantages" of Stripes(so it was "prepared"),
and my Click example just tried to show that with Click that thing was
even simpler.
To my mind the more examples of Click are available the better, why
would you want to downplay that?
Sure the more examples the better, but I think they're just examples
- should not be taken as "comparison base" to judge frameworks upon.
Olio however tries to pretend to be more, and I think in that case the
real Click advantages won't really come to light.
I start to think that we need some tool (e.g. something like a GUI
builder - but it might be without the WYSIWYG part), to use it in
screencasts to show the power of Click.
well, I'm just thinking loud,
Demetrios.
