Wicket 6 development

[Martijn Dashorst <ma...@gmail.com>]

We have released 3 bug fixes to 1.5.x and it seems like it is more
stable now. Stuff for wicket.next is piling up, so I propose we start
our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
be a breaker API wise, we can just stick with trunk for new
development, and move maintenance for 1.5.x to a branch.

WDYT?

Martijn

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

Hi,

I just attached a patch to
https://issues.apache.org/jira/browse/WICKET-3367 that integrates
Matej's work described at
https://cwiki.apache.org/WICKET/wicket-ajax-rewriting.html

Please take a look and give feedback.
Thanks!

On Tue, Nov 22, 2011 at 2:03 PM, Martin Grigorov <mg...@apache.org> wrote:
> On Tue, Nov 22, 2011 at 1:15 PM, Emond Papegaaij
> <em...@topicus.nl> wrote:
>> On Tuesday 22 November 2011 13:09:08 Martin Grigorov wrote:
>>> Hi,
>>>
>>> On Tue, Nov 22, 2011 at 1:02 PM, Hielke Hoeve <Hi...@topicus.nl>
>> wrote:
>>> > Emond Papegaaij and I have also attempted to see if it is possible to
>>> > integrate a small part of WiQuery's functionality into Wicket. We are
>>> > still working on cleaning the code but here is a preview:
>>> > https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#file
>>> > s_bucket
>>> >
>>> > Basically we have implemented
>>> > AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) )
>>> > and have it build jQuery statements for window load and dom ready. All
>>> > resources are automatically an
>>> > AbstractResourceDependentResourceReference, this will not break current
>>> > resources it will only allow them to specify their dependencies.
>>> I like the change as a whole.
>>> We had recently some complains that Wicket itself doesn't use its
>>> dependency management for resource references.
>>>
>>> What I think we should do is to remove all uses of jQuery() in .java
>>> and replace them with Wicket.Event.add().
>>
>> And wicket-event-jquery.js will convert this to $(document).ready or
>> $(window).load right?
>
> Right. Almost.
>
> Only  'domready' is a special event name, because browsers have
> different impl for that.
> Passing 'domready' as event name will do: jQuery(fn).
>
> Passing any other event name will do: jQuery(target).on(eventName, fn)
>
>>
>>> > Hielke Hoeve
>>> >
>>> > -----Original Message-----
>>> > From: Martin Grigorov [mailto:mgrigorov@apache.org]
>>> > Sent: woensdag 16 november 2011 11:05
>>> > To: dev@wicket.apache.org
>>> > Subject: Re: Wicket 6 development
>>> >
>>> > On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
>>> >> +1
>>> >>
>>> >> (I'd love to take a look at the new jquery stuff.)
>>> >
>>> > https://github.com/martin-g/wicket/tree/ajax-jquery
>>> > Basically the internals of wicket-ajax.js (partially), wicket-event.js
>>> > (fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
>>> > Also there are ~ 90 QUnit tests at
>>> > https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test
>>> > /js>
>>> >> Sven
>>> >>
>>> >> -----Ursprüngliche Nachricht-----
>>> >> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
>>> >> Gesendet: Mittwoch, 16. November 2011 10:01
>>> >> An: dev@wicket.apache.org
>>> >> Betreff: Re: Wicket 6 development
>>> >>
>>> >> +1
>>> >>
>>> >> I have quite some progress with JQuery-fying Wicket's javascripts and
>>> >> I'd like to move it in trunk and involve more people in
>>> >> designing/coding/discussing/... it.
>>> >>
>>> >> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
>>> >>
>>> >> <ma...@gmail.com> wrote:
>>> >>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>>> >>> stable now. Stuff for wicket.next is piling up, so I propose we
>>> >>> start
>>> >>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6
>>> >>> will
>>> >>> be a breaker API wise, we can just stick with trunk for new
>>> >>> development, and move maintenance for 1.5.x to a branch.
>>> >>>
>>> >>> WDYT?
>>> >>>
>>> >>> Martijn
>>> >>
>>> >> --
>>> >> Martin Grigorov
>>> >> jWeekend
>>> >> Training, Consulting, Development
>>> >> http://jWeekend.com
>>> >
>>> > --
>>> > Martin Grigorov
>>> > jWeekend
>>> > Training, Consulting, Development
>>> > http://jWeekend.com
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

On Tue, Nov 22, 2011 at 1:15 PM, Emond Papegaaij
<em...@topicus.nl> wrote:
> On Tuesday 22 November 2011 13:09:08 Martin Grigorov wrote:
>> Hi,
>>
>> On Tue, Nov 22, 2011 at 1:02 PM, Hielke Hoeve <Hi...@topicus.nl>
> wrote:
>> > Emond Papegaaij and I have also attempted to see if it is possible to
>> > integrate a small part of WiQuery's functionality into Wicket. We are
>> > still working on cleaning the code but here is a preview:
>> > https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#file
>> > s_bucket
>> >
>> > Basically we have implemented
>> > AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) )
>> > and have it build jQuery statements for window load and dom ready. All
>> > resources are automatically an
>> > AbstractResourceDependentResourceReference, this will not break current
>> > resources it will only allow them to specify their dependencies.
>> I like the change as a whole.
>> We had recently some complains that Wicket itself doesn't use its
>> dependency management for resource references.
>>
>> What I think we should do is to remove all uses of jQuery() in .java
>> and replace them with Wicket.Event.add().
>
> And wicket-event-jquery.js will convert this to $(document).ready or
> $(window).load right?

Right. Almost.

Only  'domready' is a special event name, because browsers have
different impl for that.
Passing 'domready' as event name will do: jQuery(fn).

Passing any other event name will do: jQuery(target).on(eventName, fn)

>
>> > Hielke Hoeve
>> >
>> > -----Original Message-----
>> > From: Martin Grigorov [mailto:mgrigorov@apache.org]
>> > Sent: woensdag 16 november 2011 11:05
>> > To: dev@wicket.apache.org
>> > Subject: Re: Wicket 6 development
>> >
>> > On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
>> >> +1
>> >>
>> >> (I'd love to take a look at the new jquery stuff.)
>> >
>> > https://github.com/martin-g/wicket/tree/ajax-jquery
>> > Basically the internals of wicket-ajax.js (partially), wicket-event.js
>> > (fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
>> > Also there are ~ 90 QUnit tests at
>> > https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test
>> > /js>
>> >> Sven
>> >>
>> >> -----Ursprüngliche Nachricht-----
>> >> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
>> >> Gesendet: Mittwoch, 16. November 2011 10:01
>> >> An: dev@wicket.apache.org
>> >> Betreff: Re: Wicket 6 development
>> >>
>> >> +1
>> >>
>> >> I have quite some progress with JQuery-fying Wicket's javascripts and
>> >> I'd like to move it in trunk and involve more people in
>> >> designing/coding/discussing/... it.
>> >>
>> >> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
>> >>
>> >> <ma...@gmail.com> wrote:
>> >>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>> >>> stable now. Stuff for wicket.next is piling up, so I propose we
>> >>> start
>> >>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6
>> >>> will
>> >>> be a breaker API wise, we can just stick with trunk for new
>> >>> development, and move maintenance for 1.5.x to a branch.
>> >>>
>> >>> WDYT?
>> >>>
>> >>> Martijn
>> >>
>> >> --
>> >> Martin Grigorov
>> >> jWeekend
>> >> Training, Consulting, Development
>> >> http://jWeekend.com
>> >
>> > --
>> > Martin Grigorov
>> > jWeekend
>> > Training, Consulting, Development
>> > http://jWeekend.com
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Emond Papegaaij <em...@topicus.nl>]

On Tuesday 22 November 2011 13:09:08 Martin Grigorov wrote:
> Hi,
> 
> On Tue, Nov 22, 2011 at 1:02 PM, Hielke Hoeve <Hi...@topicus.nl> 
wrote:
> > Emond Papegaaij and I have also attempted to see if it is possible to
> > integrate a small part of WiQuery's functionality into Wicket. We are
> > still working on cleaning the code but here is a preview:
> > https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#file
> > s_bucket
> > 
> > Basically we have implemented
> > AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) )
> > and have it build jQuery statements for window load and dom ready. All
> > resources are automatically an
> > AbstractResourceDependentResourceReference, this will not break current
> > resources it will only allow them to specify their dependencies.
> I like the change as a whole.
> We had recently some complains that Wicket itself doesn't use its
> dependency management for resource references.
> 
> What I think we should do is to remove all uses of jQuery() in .java
> and replace them with Wicket.Event.add().

And wicket-event-jquery.js will convert this to $(document).ready or 
$(window).load right?

> > Hielke Hoeve
> > 
> > -----Original Message-----
> > From: Martin Grigorov [mailto:mgrigorov@apache.org]
> > Sent: woensdag 16 november 2011 11:05
> > To: dev@wicket.apache.org
> > Subject: Re: Wicket 6 development
> > 
> > On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
> >> +1
> >> 
> >> (I'd love to take a look at the new jquery stuff.)
> > 
> > https://github.com/martin-g/wicket/tree/ajax-jquery
> > Basically the internals of wicket-ajax.js (partially), wicket-event.js
> > (fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
> > Also there are ~ 90 QUnit tests at
> > https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test
> > /js> 
> >> Sven
> >> 
> >> -----Ursprüngliche Nachricht-----
> >> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
> >> Gesendet: Mittwoch, 16. November 2011 10:01
> >> An: dev@wicket.apache.org
> >> Betreff: Re: Wicket 6 development
> >> 
> >> +1
> >> 
> >> I have quite some progress with JQuery-fying Wicket's javascripts and
> >> I'd like to move it in trunk and involve more people in
> >> designing/coding/discussing/... it.
> >> 
> >> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
> >> 
> >> <ma...@gmail.com> wrote:
> >>> We have released 3 bug fixes to 1.5.x and it seems like it is more
> >>> stable now. Stuff for wicket.next is piling up, so I propose we
> >>> start
> >>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6
> >>> will
> >>> be a breaker API wise, we can just stick with trunk for new
> >>> development, and move maintenance for 1.5.x to a branch.
> >>> 
> >>> WDYT?
> >>> 
> >>> Martijn
> >> 
> >> --
> >> Martin Grigorov
> >> jWeekend
> >> Training, Consulting, Development
> >> http://jWeekend.com
> > 
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

Hi,

On Tue, Nov 22, 2011 at 1:02 PM, Hielke Hoeve <Hi...@topicus.nl> wrote:
> Emond Papegaaij and I have also attempted to see if it is possible to integrate a small part of WiQuery's functionality into Wicket. We are still working on cleaning the code but here is a preview:
> https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#files_bucket
>
> Basically we have implemented AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) ) and have it build jQuery statements for window load and dom ready. All resources are automatically an AbstractResourceDependentResourceReference, this will not break current resources it will only allow them to specify their dependencies.

I like the change as a whole.
We had recently some complains that Wicket itself doesn't use its
dependency management for resource references.

What I think we should do is to remove all uses of jQuery() in .java
and replace them with Wicket.Event.add().

>
> Hielke Hoeve
>
> -----Original Message-----
> From: Martin Grigorov [mailto:mgrigorov@apache.org]
> Sent: woensdag 16 november 2011 11:05
> To: dev@wicket.apache.org
> Subject: Re: Wicket 6 development
>
> On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
>> +1
>>
>> (I'd love to take a look at the new jquery stuff.)
>
> https://github.com/martin-g/wicket/tree/ajax-jquery
> Basically the internals of wicket-ajax.js (partially), wicket-event.js
> (fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
> Also there are ~ 90 QUnit tests at
> https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test/js
>
>>
>> Sven
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
>> Gesendet: Mittwoch, 16. November 2011 10:01
>> An: dev@wicket.apache.org
>> Betreff: Re: Wicket 6 development
>>
>> +1
>>
>> I have quite some progress with JQuery-fying Wicket's javascripts and
>> I'd like to move it in trunk and involve more people in
>> designing/coding/discussing/... it.
>>
>> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
>> <ma...@gmail.com> wrote:
>>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>>> stable now. Stuff for wicket.next is piling up, so I propose we start
>>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
>>> be a breaker API wise, we can just stick with trunk for new
>>> development, and move maintenance for 1.5.x to a branch.
>>>
>>> WDYT?
>>>
>>> Martijn
>>>
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

RE: Wicket 6 development

[Hielke Hoeve <Hi...@topicus.nl>]

Emond Papegaaij and I have also attempted to see if it is possible to integrate a small part of WiQuery's functionality into Wicket. We are still working on cleaning the code but here is a preview:
https://github.com/papegaaij/wicket/compare/trunk...wicket+wiquery#files_bucket

Basically we have implemented AbstractDependencyRespectingResourceAggregatingHeaderResponse ( :-) ) and have it build jQuery statements for window load and dom ready. All resources are automatically an AbstractResourceDependentResourceReference, this will not break current resources it will only allow them to specify their dependencies. 

Hielke Hoeve

-----Original Message-----
From: Martin Grigorov [mailto:mgrigorov@apache.org] 
Sent: woensdag 16 november 2011 11:05
To: dev@wicket.apache.org
Subject: Re: Wicket 6 development

On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
> +1
>
> (I'd love to take a look at the new jquery stuff.)

https://github.com/martin-g/wicket/tree/ajax-jquery
Basically the internals of wicket-ajax.js (partially), wicket-event.js
(fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
Also there are ~ 90 QUnit tests at
https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test/js

>
> Sven
>
> -----Ursprüngliche Nachricht-----
> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
> Gesendet: Mittwoch, 16. November 2011 10:01
> An: dev@wicket.apache.org
> Betreff: Re: Wicket 6 development
>
> +1
>
> I have quite some progress with JQuery-fying Wicket's javascripts and 
> I'd like to move it in trunk and involve more people in 
> designing/coding/discussing/... it.
>
> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst 
> <ma...@gmail.com> wrote:
>> We have released 3 bug fixes to 1.5.x and it seems like it is more 
>> stable now. Stuff for wicket.next is piling up, so I propose we start 
>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will 
>> be a breaker API wise, we can just stick with trunk for new 
>> development, and move maintenance for 1.5.x to a branch.
>>
>> WDYT?
>>
>> Martijn
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
>



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

On Wed, Nov 16, 2011 at 11:54 AM, Sven Meier <sv...@meiers.net> wrote:
> +1
>
> (I'd love to take a look at the new jquery stuff.)

https://github.com/martin-g/wicket/tree/ajax-jquery
Basically the internals of wicket-ajax.js (partially), wicket-event.js
(fully) and wicket-ajax-debug.js (fully) are redone with JQuery.
Also there are ~ 90 QUnit tests at
https://github.com/martin-g/wicket/tree/ajax-jquery/wicket-core/src/test/js

>
> Sven
>
> -----Ursprüngliche Nachricht-----
> Von: Martin Grigorov [mailto:mgrigorov@apache.org]
> Gesendet: Mittwoch, 16. November 2011 10:01
> An: dev@wicket.apache.org
> Betreff: Re: Wicket 6 development
>
> +1
>
> I have quite some progress with JQuery-fying Wicket's javascripts and
> I'd like to move it in trunk and involve more people in
> designing/coding/discussing/... it.
>
> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
> <ma...@gmail.com> wrote:
>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>> stable now. Stuff for wicket.next is piling up, so I propose we start
>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
>> be a breaker API wise, we can just stick with trunk for new
>> development, and move maintenance for 1.5.x to a branch.
>>
>> WDYT?
>>
>> Martijn
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

AW: Wicket 6 development

[Sven Meier <sv...@meiers.net>]

+1

(I'd love to take a look at the new jquery stuff.)

Sven

-----Ursprüngliche Nachricht-----
Von: Martin Grigorov [mailto:mgrigorov@apache.org] 
Gesendet: Mittwoch, 16. November 2011 10:01
An: dev@wicket.apache.org
Betreff: Re: Wicket 6 development

+1

I have quite some progress with JQuery-fying Wicket's javascripts and
I'd like to move it in trunk and involve more people in
designing/coding/discussing/... it.

On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> We have released 3 bug fixes to 1.5.x and it seems like it is more
> stable now. Stuff for wicket.next is piling up, so I propose we start
> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
> be a breaker API wise, we can just stick with trunk for new
> development, and move maintenance for 1.5.x to a branch.
>
> WDYT?
>
> Martijn
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Igor Vaynberg <ig...@gmail.com>]

you can start by providing patches in our jira and by helping people
on this list.

-igor

On Wed, Nov 23, 2011 at 9:06 AM, anantasthana <an...@gmail.com> wrote:
> I would love to be a part of this (more people to design code etc)
> and provide any help i potentially can and learn as much as i can get out of
> it.
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-development-tp4075700p4100515.html
> Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
>

Re: Wicket 6 development

[anantasthana <an...@gmail.com>]

I would love to be a part of this (more people to design code etc)
and provide any help i potentially can and learn as much as i can get out of
it.

--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-development-tp4075700p4100515.html
Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

The code is in trunk with r1203152.

On Wed, Nov 16, 2011 at 8:25 PM, Martin Grigorov <mg...@apache.org> wrote:
> On Wed, Nov 16, 2011 at 8:18 PM, Andrea Del Bene <an...@gmail.com> wrote:
>> Hi Martin,
>>
>> can you notify us when you have committed your new code to trunk?
>
> Sure. Will do.
>
>>>
>>> +1
>>>
>>> I have quite some progress with JQuery-fying Wicket's javascripts and
>>> I'd like to move it in trunk and involve more people in
>>> designing/coding/discussing/... it.
>>>
>>> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
>>> <ma...@gmail.com>  wrote:
>>>>
>>>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>>>> stable now. Stuff for wicket.next is piling up, so I propose we start
>>>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
>>>> be a breaker API wise, we can just stick with trunk for new
>>>> development, and move maintenance for 1.5.x to a branch.
>>>>
>>>> WDYT?
>>>>
>>>> Martijn
>>>>
>>>
>>>
>>
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

On Wed, Nov 16, 2011 at 8:18 PM, Andrea Del Bene <an...@gmail.com> wrote:
> Hi Martin,
>
> can you notify us when you have committed your new code to trunk?

Sure. Will do.

>>
>> +1
>>
>> I have quite some progress with JQuery-fying Wicket's javascripts and
>> I'd like to move it in trunk and involve more people in
>> designing/coding/discussing/... it.
>>
>> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
>> <ma...@gmail.com>  wrote:
>>>
>>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>>> stable now. Stuff for wicket.next is piling up, so I propose we start
>>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
>>> be a breaker API wise, we can just stick with trunk for new
>>> development, and move maintenance for 1.5.x to a branch.
>>>
>>> WDYT?
>>>
>>> Martijn
>>>
>>
>>
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Andrea Del Bene <an...@gmail.com>]

Hi Martin,

can you notify us when you have committed your new code to trunk?
> +1
>
> I have quite some progress with JQuery-fying Wicket's javascripts and
> I'd like to move it in trunk and involve more people in
> designing/coding/discussing/... it.
>
> On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
> <ma...@gmail.com>  wrote:
>> We have released 3 bug fixes to 1.5.x and it seems like it is more
>> stable now. Stuff for wicket.next is piling up, so I propose we start
>> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
>> be a breaker API wise, we can just stick with trunk for new
>> development, and move maintenance for 1.5.x to a branch.
>>
>> WDYT?
>>
>> Martijn
>>
>
>

Re: Wicket 6 development

[Martin Grigorov <mg...@apache.org>]

+1

I have quite some progress with JQuery-fying Wicket's javascripts and
I'd like to move it in trunk and involve more people in
designing/coding/discussing/... it.

On Wed, Nov 16, 2011 at 10:51 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> We have released 3 bug fixes to 1.5.x and it seems like it is more
> stable now. Stuff for wicket.next is piling up, so I propose we start
> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
> be a breaker API wise, we can just stick with trunk for new
> development, and move maintenance for 1.5.x to a branch.
>
> WDYT?
>
> Martijn
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

Re: Wicket 6 development

[Igor Vaynberg <ig...@gmail.com>]

+1

-igor

On Wed, Nov 16, 2011 at 12:51 AM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:

> We have released 3 bug fixes to 1.5.x and it seems like it is more
> stable now. Stuff for wicket.next is piling up, so I propose we start
> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
> be a breaker API wise, we can just stick with trunk for new
> development, and move maintenance for 1.5.x to a branch.
>
> WDYT?
>
> Martijn
>

Re: Wicket 6 development

[Juergen Donnerstag <ju...@gmail.com>]

+1

Juergen

Re: Wicket 6 development

[Kailash Yadav <ya...@gmail.com>]

+1

Kailash Yadav

On Wed, Nov 16, 2011 at 2:22 PM, Martijn Dashorst [via Apache Wicket] <
ml-node+s1842946n4075700h82@n4.nabble.com> wrote:

> We have released 3 bug fixes to 1.5.x and it seems like it is more
> stable now. Stuff for wicket.next is piling up, so I propose we start
> our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
> be a breaker API wise, we can just stick with trunk for new
> development, and move maintenance for 1.5.x to a branch.
>
> WDYT?
>
> Martijn
>
>


--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-6-development-tp4075700p4077113.html
Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.