Re: page version and forms

2012-08-28 Thread Alex Shubert
Nope, 1.5 Well, I am not quite sure that my statement is correct. while tree project has some kind of examples, there are no real documentation. Let's consieder http://www.mysticcoders.com/blog/autocomplete-with-an-object/ - my opinion is that sometimes one may want to make an impression

Re: page version and forms

2012-08-28 Thread Martin Grigorov
Alex, On Tue, Aug 28, 2012 at 10:31 AM, Alex Shubert alex.shub...@gmail.com wrote: Nope, 1.5 Well, I am not quite sure that my statement is correct. while tree project has some kind of examples, there are no real documentation. Let's consieder

Re: page version and forms

2012-08-22 Thread Alex Shubert
Sven while you are here: why no documentation for Tree? Nothing at all? Right now I face a problem - tree do not persist it's state (Bookmarcable links, copied from example) and I have no clue where to see. On 21 August 2012 21:38, Sven Meier s...@meiers.net wrote: And the winner is ... Martin!

Re: page version and forms

2012-08-22 Thread Martin Grigorov
Hi, These components have been merged in Wicket 6. You can see the demo at http://www.wicket-library.com/wicket-examples-6.0.x/tree and the code in org.apache.wicket.extensions.markup.html.repeater.tree package in wicket-extensions module. The javadocs are also improved. On Wed, Aug 22, 2012 at

Re: page version and forms

2012-08-22 Thread Sven Meier
Are you using wicket-tree or the new components in Wicket 6? Please be more specific what information you're looking for. I'll gladly provide more info in javadoc or in the wiki. Sven Alex Shubert alex.shub...@gmail.com schrieb: Sven while you are here: why no documentation for Tree? Nothing

Re: page version and forms

2012-08-21 Thread Martin Grigorov
Use StatelessForm instead. On Tue, Aug 21, 2012 at 1:06 PM, Alex Shubert alex.shub...@gmail.com wrote: Hello Recently I found wicket tree control http://wicket-tree.appspot.com/nested and one there is a thing I can't understand: while the page contains Form it looks like not versioned. I

Re: page version and forms

2012-08-21 Thread Alex Shubert
They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from Wicket API doesn't extends StatelessForm while your answer states that must be the case. On 21 August 2012 14:20, Martin Grigorov mgrigo...@apache.org wrote: Use StatelessForm

Re: page version and forms

2012-08-21 Thread Martin Grigorov
The deployed examples use Wicket 1.4. http://wicket-tree.appspot.com/?wicket:interface=:0:1::: On Tue, Aug 21, 2012 at 1:35 PM, Alex Shubert alex.shub...@gmail.com wrote: They are using FormVoid form = new FormVoid(form); and still no version in url on round-trips. Also, FilterForm from

Re: page version and forms

2012-08-21 Thread Alex Shubert
Martin with all my respect but their build script uses dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version${wicket.version}/version /dependency

Re: page version and forms

2012-08-21 Thread Martin Grigorov
Sorry for being stubborn but having '?wicket:interface=:0:1:::' in the url means that this is Wicket pre-1.5 ;-) I guess Sven will join this conversation later today and explain in more details. On Tue, Aug 21, 2012 at 2:16 PM, Alex Shubert alex.shub...@gmail.com wrote: Martin with all my

Re: page version and forms

2012-08-21 Thread Alex Shubert
Martin, http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom Again, no 1.4 at all. Not in one place. Moreover, '?wicket:interface=:0:1:::' doesn't means 1.4 is in action. Just take a look at event listener implementation. About the problem:

Re: page version and forms

2012-08-21 Thread Pointbreak
The tree node selections are fully handled by ajax requests, so they will (obviously) never change the url of the page. Change the selection of e.g. the dropdown for Content, and you will see that the url changes. There are ways to have forms without version/id information in the URL. Search this

Re: page version and forms

2012-08-21 Thread Alex Shubert
It's obvious that selection of leafs (implemented as BookmarcableLinks) is NOT handled by Ajax. BookmarkableFolderContent.java : 62 PageParameters parameters = new PageParameters(); parameters.add(foo, foo.getId());

Re: page version and forms

2012-08-21 Thread Martin Grigorov
The Google Code repo contains 1.5 but the deployed app is using pre-1.5 version. I can bet on this. On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert alex.shub...@gmail.com wrote: Martin, http://wicket-tree.googlecode.com/svn/repo/wicket-tree/wicket-tree-parent/0.5.0/wicket-tree-parent-0.5.0.pom

Re: page version and forms

2012-08-21 Thread Alex Shubert
Martin, does it really makes any difference? Lack of stateless navigation does ( https://issues.apache.org/jira/browse/WICKET-1086 ) Anyway, I explained solution in my prev letter. Thanks! On 21 August 2012 16:59, Martin Grigorov mgrigo...@apache.org wrote: The Google Code repo contains 1.5 but

Re: page version and forms

2012-08-21 Thread Martin Grigorov
On Tue, Aug 21, 2012 at 4:11 PM, Alex Shubert alex.shub...@gmail.com wrote: Martin, does it really makes any difference? Lack of stateless navigation does ( https://issues.apache.org/jira/browse/WICKET-1086 ) I'm not sure what you mean by referring to this ticket. I guess you just found out

Re: page version and forms

2012-08-21 Thread Sven Meier
And the winner is ... Martin! On AppEngine I still have Wicket 1.4.x running. Sven On 08/21/2012 02:59 PM, Martin Grigorov wrote: The Google Code repo contains 1.5 but the deployed app is using pre-1.5 version. I can bet on this. On Tue, Aug 21, 2012 at 3:37 PM, Alex Shubert