These two are the exact same things I have in mind about wicket: On Nov 15, 2007 10:18 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > I've always had in my mind that the perfect > approach to state handling would be to give users the choice between > server managed and client managed (i.e. by passing parameters/ rest) > on a component level.
Yes! Taking after the database-backed DetatchableModel, there could be a PageParameterModel. We could use it to store the search form values and the DefaultDataTable sort parameters and such to make application state bookmarkable (and preferably human readable). > * Java. I'm getting tired of Java's limitations and plain inelegance Same here, too much academic language programming on my mind :-) I hope I can get around to replicate and your scala-wicket experiments in the holiday season. Oh, and type-safe models are a must, I was surprised to read in this thread not everybody agrees with that. Especially since type erasure ensures backwards compatibility, and lets the cast-fans stick to their habits :-) Szocske --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
