the behaviours can be easily replaced with attribute modifiers. i use them directly because they are slightly more efficient. looking at the present code backporting to 1.1 looks easy, so you can try to do that. the problem i would see is that as i fix bugs in 1.2 you would have to do the same in your code. i simply do not have the time to maintain both branches and i want to take advantage of the latest features 1.2 offers.

so its really up to you. with some work you can get the 1.2 version working in 1.1, but i dont think we will release 1.2 in the timeframe you need.

-Igor


On 12/14/05, Iman Rahmatizadeh < [EMAIL PROTECTED]> wrote:
Yes, the IBehaviour for example and its implementations are used in the filter forms. So I guess you insist it'll be better to stick to 1.1 and try to make the DataTable compatible with it?


On 12/14/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i doubt we will release 1.2 in a month and a half.

i think most of the changes i made to extensions are backwards compat. can you try to compile extensions 1.2 against wicket 1.1?

-Igor



On 12/14/05, Iman Rahmatizadeh <[EMAIL PROTECTED]> wrote:
I'm currently working with DataTable's in wicket extensions 1.1 release. It seems to be lacking many of the good features Igor added to the new DataTable implementation in cvs. Moving to the new version requires me also to update my wicket to the latest cvs version. I'm planning to have a release of my application in about 1.5 months, could anyone tell if there will be a stable release of wicket till then , or can i use the new features of DataTable without having to upgrade my wicket core ?

Iman



Reply via email to