Hello.
I was actually looking to pump in my enhancements to the Widget module.
I've incorporated some Ajax-facilitating or Ajax-related features
directly into the Widget module, so I won't have to do HUGE .ftl(s).
Imagine being able to use and reuse a widget-screen for 2 (or more)
purposes: non-ajax operation and ajax operation (pulling down various
sub-sub-parts of the screen).
In general, I was able to make all listings screens (with the Prev/Next
hrefs) load via Ajax.
Did anyone here ever try wicket? (http://wicket.sourceforge.net/) We (the
company I'm working for) didn't try it out until now (but we plan to do
so), so I cannot really tell how good it is. However, here's what the wiki
page of wicket says (http://en.wikipedia.org/wiki/Wicket_framework) -
these things sound pretty smart to me:
- Transparent state management
- Wicket pages can be mocked up, previewed, and later revised using
standard WYSIWYG HTML design tools (except when using special tags like
<wicket:border>..</wicket:border> or <wicket:body/>).
- Dynamic content processing and form handling is all handled in Java code.
- No XML configuration files.
br,
--
Florin Jurcovici
------------------
Why do psychics have to ask you for your name?
On Tue, 24 Apr 2007 06:33:36 +0300, Jonathon -- Improov <[EMAIL PROTECTED]>
wrote:
