Re: RFC-0001: Deprecating PageParameters for Wicket 7 (was Re: [4/4] git commit: WICKET-4997)

2013-08-22 Thread Ben Tilford
There really isn't a good reason to remove them even if parameter injection is added. If they have to be removed at least deprecate and remove in v 8. On Thu, Aug 22, 2013 at 12:26 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > On Thu, Aug 22, 2013 at 6:24 PM, Ben

Re: RFC-0001: Deprecating PageParameters for Wicket 7 (was Re: [4/4] git commit: WICKET-4997)

2013-08-22 Thread Ben Tilford
By deprecate I hope you don't mean remove. This change would break almost every single wicket application ever written. On Thu, Aug 22, 2013 at 9:55 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > In the previous thread where I spin this message from it was mentioned by > Emond that

Re: Ajax in Wicket.next

2011-09-20 Thread Ben Tilford
With the js framework suggestions I havn't seen anyone mention a module system like require.js this would be something I'd wan't to see used. If something like jQuery gets included without a module system it would only be a matter of time until jQuery.next was released and someone wants to use it.

Re: taking the I out of Interface

2009-10-05 Thread Ben Tilford
Couldn't you mark IModel as deprecated for 1.5, extend IModel with no added api for the Locator, make all implementations use the Locator interface then in 1.next remove IModel and define the API in Locator? Or is this really more than a name change? On Mon, Oct 5, 2009 at 9:17 AM, nino martinez w