You can have this kind of degradation with wicket. Just use AjaxFallbackLink and AjaxFallbackButton, they work both with or without Ajax, depending on user capabilities.
-Matej On 9/6/07, bmarvell <[EMAIL PROTECTED]> wrote: > > Guys, > > While I'm ruffling the wicket feathers I thought I'd ask about about another > issue that's been bothering me with wicket. > > From what I can see you either have the option of using AJAX or not. This is > all well and good but they seem like very forked approaches. So what I'm > trying to say is has there been any thought into taking a progressive > enhancement approach? > > Taking that approach would mean pages that "were ajax" would work if the the > user disabled javascript or not. Not to mention a whole wealth of other > benefits that can be found here... > > http://en.wikipedia.org/wiki/Progressive_enhancement > > Just a question/thought don't flame me ;) > -- > View this message in context: > http://www.nabble.com/Progressive-Enhancement-tf4390623.html#a12518275 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
