On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:
but as you will see, there is not much
demand for precanned components out there, they are just too easy to
roll yourself and there are a lot of open source ones that you can at
least get ideas from for your specific requirements.
But isn't that missing some of the major reasons for using components:
1. that you shouldn't have to reinvent the wheel (even if it is easy),
2. that a component that is tried and tested (version 3+) is better
than my version 1,
3. components can encapsulate best practice that takes time to learn,
4. a suite of components may integrate better.
Writing a linked list in Java is easy but I would never consider doing
that, the available classe are much more powerful, general, well-
tested, integrated, ...
I'm not knowledgeable wrt Wicket components or JSF components, but
generally speaking what components available in JSF, for example,
wouldn't be useful in Wicket and why not?
I'm with the OP in that I'm a little surprised by the lack of
published components (from low-level to high-level). Again, I am
probably missing something ...
Maybe as I learn more about Wicket and get more experience I will
understand.
Cheers,
Ashley.
--
Ashley Aitken
Perth, Western Australia
Skype/iChat: MrHatken (GMT + 8hrs!)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
