Thanks Gwyn and John, Anyway, here's what I wrote up till now: Clean / clear separation of presentation and logic Supports Ajax Security Enabling reuse Manages state Markup inheritance }POJO for logic No XML, no configuration files Stateful i18n Manipulate HTML tags and header via Java
Any thought about this list? On Tue, Jun 3, 2008 at 11:10 PM, John Krasnay <[EMAIL PROTECTED]> wrote: > > One big selling point for me was the encapsulation of components. > Because the code and all required resources (markup, CSS, JS, > localization properties) are by default retrieved from the classpath, > it's trivial to create reusable libraries of common components, page > layouts, etc. > > jk > > On Tue, Jun 03, 2008 at 10:37:50PM +0300, Eyal Golan wrote: > > Hi, > > I'm going to give an intro presentation about Wicket at my home company (I > > work as an outsource). > > There are so many cool things in Wicket and I probably know some / most of > > them. > > Can you give your advice / thoughts? > > > > Things like Ajax support, markup inheritance, POJO usage, clear and clean > > separation of view and logic, learning curve etc. > > > > Thanks > > > > -- > > Eyal Golan > > [EMAIL PROTECTED] > > > > Visit: http://jvdrums.sourceforge.net/ > > LinkedIn: http://www.linkedin.com/in/egolan74 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Eyal Golan [EMAIL PROTECTED] Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
