Re: Wicket source code moved to Git

2011-12-21 Thread Martin Grigorov
The most important info is missing - the checkout url! :-) For devs: https://your_apache_usern...@git-wip-us.apache.org/repos/asf/wicket.git For users: git://git.apache.org/wicket.git or https://github.com/apache/wicket On Wed, Dec 21, 2011 at 6:46 AM, Jeremy Thomerson jer...@wickettraining.com

Re: Wicket source code moved to Git

2011-12-21 Thread Martijn Dashorst
On Wed, Dec 21, 2011 at 10:04 AM, Martin Grigorov mgrigo...@apache.org wrote: The most important info is missing - the checkout url! :-) For devs: https://your_apache_usern...@git-wip-us.apache.org/repos/asf/wicket.git If you set up the .netrc like the git @ apache document states, you should

Roadmap for Wicket 6.0

2011-12-21 Thread Martin Grigorov
Hi, Let discuss (again) what will be included in Wicket 6.0 so we can schedule what and when will be implemented. Here is how I see it: - use JQuery as backing library - already in master/trunk - rework Wicket Ajax to use event registration instead of inline attributes (like onclick, onchange,

Re: Wicket source code moved to Git

2011-12-21 Thread Igor Vaynberg
not sure if git://git.apache.org/wicket.git is kept up with commits to git-wip-us i think for users On Wed, Dec 21, 2011 at 1:04 AM, Martin Grigorov mgrigo...@apache.org wrote: The most important info is missing - the checkout url! :-) For devs:

Re: Wicket source code moved to Git

2011-12-21 Thread Igor Vaynberg
i think for users its fine to git clone https://git-wip-us.apache.org/repos/asf/wicket.git -igor On Wed, Dec 21, 2011 at 8:26 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote: not sure if git://git.apache.org/wicket.git is kept up with commits to git-wip-us i think for users On Wed,

Re: Wicket source code moved to Git

2011-12-21 Thread Igor Vaynberg
also note that for some clones trunk is still the default branch. be sure to 'git checkout master' which is where 6.0 stuff lives. -igor On Wed, Dec 21, 2011 at 8:30 AM, Martin Grigorov mgrigo...@apache.org wrote: On Wed, Dec 21, 2011 at 6:26 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:

Re: Wicket source code moved to Git

2011-12-21 Thread Jeremy Thomerson
On Tue, Dec 20, 2011 at 11:46 PM, Jeremy Thomerson jer...@wickettraining.com wrote: On Tue, Dec 20, 2011 at 11:20 PM, Clint Checketts checke...@gmail.comwrote: Jeremy, Will Git development mimic the current subversion workflow, or will we see we see a more Git-ish way like 'git flow'?

Re: Wicket source code moved to Git

2011-12-21 Thread Johan Compagner
hmm i use EGit but some how i always get not authorized if i try to push something I am quite sure the username/password is correct, but will recheck it, i use this url: https://jcompag...@git-wip-us.apache.org/repos/asf/wicket.git On Wed, Dec 21, 2011 at 19:26, Jeremy Thomerson

Re: Wicket source code moved to Git

2011-12-21 Thread Jeremy Thomerson
On Wed, Dec 21, 2011 at 1:40 PM, Johan Compagner jcompag...@gmail.comwrote: hmm i use EGit but some how i always get not authorized if i try to push something I am quite sure the username/password is correct, but will recheck it, i use this url:

Re: Roadmap for Wicket 6.0

2011-12-21 Thread Gabriel Landon
I would love to have a refactor of the Treegrid (see https://issues.apache.org/jira/browse/WICKET-1600 WICKET-1600 ) implemented with the http://code.google.com/p/wicket-tree/ wicket-tree implementation Sven Meier has done. It would be very nice to use a TreeProvider instead of the swing

Re: Wicket source code moved to Git

2011-12-21 Thread Martin Grigorov
On Wed, Dec 21, 2011 at 8:40 PM, Johan Compagner jcompag...@gmail.com wrote: hmm i use EGit but some how i always get not authorized if i try to push something I am quite sure the username/password is correct, but will recheck it, i use this url:

Re: Roadmap for Wicket 6.0

2011-12-21 Thread Sven Meier
Hi Gabriel, there are several components which are in need of an overhaul, especially Javascript heavy implementations like modal window and autocomplete. Before we have decided on these, I'm reluctant to shove more code into the framework. It would be very nice to use a TreeProvider