I'm curious. Which ideas would you steal from SiteBricks and JaxRS? Juergen
On Tue, Nov 30, 2010 at 5:51 AM, Eelco Hillenius <eelco.hillen...@gmail.com> wrote: > On Mon, Nov 29, 2010 at 7:45 PM, richard emberson > <richard.ember...@gmail.com> wrote: >> If wicket was going to be coded over again, would you make >> isEnabled and/or isVisible final methods? > > If *I* would do it, I'd probably write it for Scala and lean more > heavily on functions rather than mutable state. I'd also steal a few > ideas from other frameworks like SiteBricks and JaxRS, have better > 'native' JavaScript support (but definitively not going the GWT > route), make choosing between stateful and stateless more explicit and > up-front, support client-side state (but not like JSF or ASP.NET do > it), etc. I gathered plenty of ideas of how I'd do a new framework, > but I'm not even going to attempt that anyway :-) After having done a > few projects with alternatives (GWT, pure JS/ JaxRS), I'm totally sold > on Wicket again. It's not a perfect framework, but sure beats the hell > out of most other frameworks when it comes to productivity and > maintainability. :-) > > Eelco >
