from:"Vladimir K"


+1
I will buy such trick


Erik van Oosten wrote:
 
 Jonathan Locke wrote:
  I've got 13 tricks coded up now and
 ideas for a handful more, but if there are any requests out there, please
 let me know
   
 Perhaps something about handling URLs. Like writing your own url coding 
 strategy and how to mount pages with URL that have some variable before 
 the fixed parts (like /{language}/products/{productid}).
 
 Regards,
 Erik.
 
 
 -- 
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p24703581.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Twenty Six Wicket Tricks


ModalWindow (being a wicket cheat :) ) deserves a sole book of tricks. I'll
definitely author my own modal window unless someone fixes the original one.
-1 on including ModalWindow to the book.


egolan74 wrote:
 
 I can't wait for yet another great Wicket book.
 I will surly buy it.
 
 regarding tricks,
 using Modal window can be nice.
 Integrating Wicket with JS libs (If it's not a topic for a small book by
 itself).
 Cool stuff with Ajax.
 
 
 Eyal Golan
 egola...@gmail.com
 
 Visit: http://jvdrums.sourceforge.net/
 LinkedIn: http://www.linkedin.com/in/egolan74
 
 P  Save a tree. Please don't print this e-mail unless it's really
 necessary
 
 
 On Tue, Dec 30, 2008 at 10:32 AM, Jonathan Locke
 jonathan.lo...@gmail.comwrote:
 

 Well, over the break here I've started something I swore I would never do
 again (well, two things, if you include the JavaOne talk I'm working on).
 I'm writing a (hopefully relatively short) book. It's called Twenty-Six
 Wicket Tricks. Each trick in the book (lettered from A-Z) demonstrates
 something that people typically want to do and in the process builds a
 reusable and educational component. I've got 13 tricks coded up now and
 ideas for a handful more, but if there are any requests out there, please
 let me know. I'd also be interested in getting some idea how many people
 would be interested in this book (would provide some fuel for me to get
 it
 done). It does not cover any of the same ground as Wicket in Action
 (which
 you should buy if you have not already!), BTW. It's more of a companion
 to
 that book.

 Happy Holidays!

 Best,

   Jonathan


 --
 View this message in context:
 http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p21214357.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 
 -
 Eyal Golan
 egola...@gmail.com
 
 Visit: JVDrums 
 LinkedIn: LinkedIn 
 

-- 
View this message in context: 
http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p24704037.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: reuseitems problems


Martin,

please describe the context. I don't see how the process of serialization
makes the instance of the object obsolete.

In my practice I use a detachable model when rendering View page and I use a
static model when rendering an Edit page. In onSubmit method I save the
model object and forward the user to the View page.


MartinM wrote:
 
 Hi!
 
 I am having trouble with listView.setReuseitems(true).
 
 My problem is that
 1. on first request the listview creates form components.
 2. on second (or third ...) request the listView reuses the form
 components.
 3. however, the propertymodels attached to the formcomponents at 1 are
 no longer viable, because their target objects are only the orignal
 serialization copies. In state 2 or 3 the form components now update
 totally obsolete instances of the target objects .
 
 A better strategy would probably be to just copy the rawInput states
 of the formComponents instead of really reusing the components.
 
 Comments, anybody? Did I misunderstand something? I have been
 debugging this for 6 hours now, maybe my brain melted down already. ..
 
 **
 Martin
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/reuseitems-problems-tp24702133p24704253.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Twenty Six Wicket Tricks


Jeremy,

from my perspective ModalWindow is a mix of javascript widget that works in
non-wicket mode and an wicket wrapper that bridges js widget with wicket. It
is always created at the body level. That's why I said it's a cheat. Thus
are problems with form submitting when nested forms are used. Community
introduced a solution (a wrapping form that is threated as the root) to work
around the mismatch of ModalWindow structure. There is an issue registered
about that. But Matej keeps stating that we should put MW into a form. What
says that he is not aware what the problem is. And there are more problems
caused by the fact that the form element is created by javascript.

From the other hand I believe it is possible to write pure Wicket component
that would be as trice as simpler and won't suffer with problems with
request lifecycle. Probably I'm wrong and it is not worth turning the old
ModalWindow into pure Wicket component due to expensiveness of the effort
that would be spent to remain it compatible.

The same about tree components. The API is very difficult to comprehend.
Component does not work as I expect in dynamic context. But thankfully Sven
implemented different implementation that does what is expect and usable as
well as DataTable component. I believe forking and fixing the original
component would be much more expensive. After that so many people should
start complaining about that to convince core team that there is not just
one person who is experiencing problems. It is always difficult to
accomplish.


jthomerson wrote:
 
 Why create your own?  Submit a patch to fix what you see is wrong with
 the current one.  Everyone wins.
 
 --
 Jeremy Thomerson
 http://www.wickettraining.com
 
 
 
 
 On Tue, Jul 28, 2009 at 12:20 PM, Vladimir Kkoval...@gmail.com wrote:

 ModalWindow (being a wicket cheat :) ) deserves a sole book of tricks.
 I'll
 definitely author my own modal window unless someone fixes the original
 one.
 -1 on including ModalWindow to the book.


 egolan74 wrote:

 I can't wait for yet another great Wicket book.
 I will surly buy it.

 regarding tricks,
 using Modal window can be nice.
 Integrating Wicket with JS libs (If it's not a topic for a small book by
 itself).
 Cool stuff with Ajax.


 Eyal Golan
 egola...@gmail.com

 Visit: http://jvdrums.sourceforge.net/
 LinkedIn: http://www.linkedin.com/in/egolan74

 P  Save a tree. Please don't print this e-mail unless it's really
 necessary


 On Tue, Dec 30, 2008 at 10:32 AM, Jonathan Locke
 jonathan.lo...@gmail.comwrote:


 Well, over the break here I've started something I swore I would never
 do
 again (well, two things, if you include the JavaOne talk I'm working
 on).
 I'm writing a (hopefully relatively short) book. It's called
 Twenty-Six
 Wicket Tricks. Each trick in the book (lettered from A-Z) demonstrates
 something that people typically want to do and in the process builds a
 reusable and educational component. I've got 13 tricks coded up now and
 ideas for a handful more, but if there are any requests out there,
 please
 let me know. I'd also be interested in getting some idea how many
 people
 would be interested in this book (would provide some fuel for me to get
 it
 done). It does not cover any of the same ground as Wicket in Action
 (which
 you should buy if you have not already!), BTW. It's more of a companion
 to
 that book.

 Happy Holidays!

 Best,

       Jonathan


 --
 View this message in context:
 http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p21214357.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 -
 Eyal Golan
 egola...@gmail.com

 Visit: JVDrums
 LinkedIn: LinkedIn


 --
 View this message in context:
 http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p24704037.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p24705381.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: reuseitems problems


Martin,

why do you get Page instance 2 on page refresh?


MartinM wrote:
 
 please describe the context. I don't see how the process of serialization
 makes the instance of the object obsolete.
 
 1. Page instantiation. Page instance 1 {manipulating target data 1},
 formComponent instance 1-target data instance 1.
 2. Ajax request or similar onto page.
 3. Page refresh (deserialized from diskstore). Page instance 2
 {manipulating target data instance 2}, reused formComponent instance
 1-target data instance 1.
 
 So in stage 3 the page is manipulating target data instance 2 while
 the reused form components still manipulate target data instance 1.
 
 What this means? It means that  for example if you Submit form, the
 values will be updated onto target data 1. The mistake is that if your
 Page instance 2 handles saving procedure, it will save the target data
 {2} which does not receive the form submit.
 
 This might work differently with detached models. I do not bother with
 detached models on lightweight models.
 
 **
 Martin
 

 MartinM wrote:

 Hi!

 I am having trouble with listView.setReuseitems(true).

 My problem is that
 1. on first request the listview creates form components.
 2. on second (or third ...) request the listView reuses the form
 components.
 3. however, the propertymodels attached to the formcomponents at 1 are
 no longer viable, because their target objects are only the orignal
 serialization copies. In state 2 or 3 the form components now update
 totally obsolete instances of the target objects .

 A better strategy would probably be to just copy the rawInput states
 of the formComponents instead of really reusing the components.

 Comments, anybody? Did I misunderstand something? I have been
 debugging this for 6 hours now, maybe my brain melted down already. ..

 **
 Martin

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 View this message in context:
 http://www.nabble.com/reuseitems-problems-tp24702133p24704253.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/reuseitems-problems-tp24702133p24705518.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: reuseitems problems


trying to undertand what is happening in your case. When the page is
serialized the steam contains the whole graph, including the ListView and
it's items and the page default model and the ListView items models. When
the page is deserialized, the whole graph is restored including page, its
model, items and their models. My understanding is that in your case the
items models are the old ones that was in the previous version of the page,
how could it be? Or I didn't get what you were saying.


MartinM wrote:
 
 Or session store.. anyways, that's not relevant. The important fact is
 that the copies are different.
 
 **
 Martin
 
 2009/7/28 Martin Makundi martin.maku...@koodaripalvelut.com:
 why do you get Page instance 2 on page refresh?

 Wicket always deserializes page state from diskstore.. so it is a copy.

 **
 Martin



 MartinM wrote:

 please describe the context. I don

 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/reuseitems-problems-tp24702133p24705851.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Twenty Six Wicket Tricks


Matej,

one of the problems is that when ajax submit happens (by pressing ajax
submit button that resides in a form that resides in a ModalWindow that is
put into another form) it contains no data for the components of enclosing
form but the process of handling the submit handles the eclosing form and
the validation fails or the values become empty. (If I remember all the
details correctly - it was 3 months ago)

Another problem happens when you don't use ajax submit but regular one
instead. If I'm not wrong Wicket can't find components of inner form.

In case if some pieces are missed in sandwitch FormModalWinwodForm the
mismatch occurs immediately.

Having no acces to hardcoded form element makes impossible to enhance
ModalWindow as well as to implement just regular upload submit from within
ModalWindow without patching .js file. If you could fix that (preventing
wicket from making it a div) and make the form configurable it would be
great!

Concerning Tree. It is my subjective opinion. It is the API that was
difficult to figure out how to employ to solve my tasks. I find the
difference betwen DataTable and TreeTable APIs to be unnecessary difficulty
to users. At least they are two different things that requires more time to
learn and work with. And if you have a panel where you switch between table
and tree you have to write an abstraction layer. Sven's TableTree just fits
where it should be. I completely added it within 2 hours. TreeTable took 2
days to learn and employ. Once again, I'm subjective here. It was just my
experience. My idea is that diversity is a good thing when the original
component dont meet our needs makes the development more complicated.

I'm aware of CSS positioning model and I have ideas to investigate. Besides
there are a jQuery popup window which example is embedded into enclosing div
and can be freely relocated inside the body.

Anyway it is possible to do what the modal.js is doing by Wicket means and
don't have a component tree mismatch with DOM.


Matej Knopp-2 wrote:
 
 On Tue, Jul 28, 2009 at 8:31 PM, Vladimir Kkoval...@gmail.com wrote:

 Jeremy,

 from my perspective ModalWindow is a mix of javascript widget that works
 in
 non-wicket mode and an wicket wrapper that bridges js widget with wicket.
 It
 is always created at the body level. That's why I said it's a cheat. Thus
 are problems with form submitting when nested forms are used.
 There is a good reason why the modal window has to be created on body
 level. That's the only reliable way to have element
 with absolute position. If you create the DOM structure deeper you are
 risking that a container has position:relative somewhere which will
 essentially break it. Welcome to the wonderful world of CSS.
 
 Community
 introduced a solution (a wrapping form that is threated as the root) to
 work
 around the mismatch of ModalWindow structure. There is an issue
 registered
 about that. But Matej keeps stating that we should put MW into a form.
 What
 says that he is not aware what the problem is. And there are more
 problems
 caused by the fact that the form element is created by javascript.
 Is it, really?
 
 I've already explained why the DOM structure is created on root level.
 If you have form component inside modal window, chances are that
 wicket will (to support nested forms) render it as div. If this
 happens it is no longer possible to serialize the form when doing an
 ajax submit. That's why the actual modal window markup contains a real
 form.
 
 And this is why it is necessary to put a modal window inside a form if
 you want to have form in modal window. What we should have done is to
 put a wicket form inside the modal window panel itself (just to force
 all forms in modal window content) to be rendered as nested. But for
 some reason i thought that a simple mention in javadoc about putting
 modal window to form would be sufficient. My bad.
 

 From the other hand I believe it is possible to write pure Wicket
 component
 that would be as trice as simpler and won't suffer with problems with
 request lifecycle. Probably I'm wrong and it is not worth turning the old
 ModalWindow into pure Wicket component due to expensiveness of the effort
 that would be spent to remain it compatible.
 Would you mind specifying the actual problems with request
 lifecycle? And how exactly would a pure wicket modal window look
 like? No javascript?

 The same about tree components. The API is very difficult to comprehend.
 Component does not work as I expect in dynamic context. But thankfully
 Sven
 implemented different implementation that does what is expect and usable
 as
 well as DataTable component. I believe forking and fixing the original
 component would be much more expensive. After that so many people should
 start complaining about that to convince core team that there is not just
 one person who is experiencing problems. It is always difficult to
 accomplish.
 I would like to have some clarification on this. What is

Re: Twenty Six Wicket Tricks


The following class fixes the problem. It is the evidence of mismatch I'm
saying about.

public class ModalWindowFormT extends FormT {
public ModalWindowForm(String id) {
super(id);
}

@Override
public Form? getRootForm() {
Form? form = super.getRootForm();

if ((findParent(ModalWindow.class) != null) 
(form.findParent(ModalWindow.class) == null))
return this;
else
return form;
}
}

I assume I don't understand something. But anyway I expect following the
least surprise rule.



Matej Knopp-2 wrote:
 
 On Tue, Jul 28, 2009 at 8:31 PM, Vladimir Kkoval...@gmail.com wrote:

 Jeremy,

 from my perspective ModalWindow is a mix of javascript widget that works
 in
 non-wicket mode and an wicket wrapper that bridges js widget with wicket.
 It
 is always created at the body level. That's why I said it's a cheat. Thus
 are problems with form submitting when nested forms are used.
 There is a good reason why the modal window has to be created on body
 level. That's the only reliable way to have element
 with absolute position. If you create the DOM structure deeper you are
 risking that a container has position:relative somewhere which will
 essentially break it. Welcome to the wonderful world of CSS.
 
 Community
 introduced a solution (a wrapping form that is threated as the root) to
 work
 around the mismatch of ModalWindow structure. There is an issue
 registered
 about that. But Matej keeps stating that we should put MW into a form.
 What
 says that he is not aware what the problem is. And there are more
 problems
 caused by the fact that the form element is created by javascript.
 Is it, really?
 
 I've already explained why the DOM structure is created on root level.
 If you have form component inside modal window, chances are that
 wicket will (to support nested forms) render it as div. If this
 happens it is no longer possible to serialize the form when doing an
 ajax submit. That's why the actual modal window markup contains a real
 form.
 
 And this is why it is necessary to put a modal window inside a form if
 you want to have form in modal window. What we should have done is to
 put a wicket form inside the modal window panel itself (just to force
 all forms in modal window content) to be rendered as nested. But for
 some reason i thought that a simple mention in javadoc about putting
 modal window to form would be sufficient. My bad.
 

 From the other hand I believe it is possible to write pure Wicket
 component
 that would be as trice as simpler and won't suffer with problems with
 request lifecycle. Probably I'm wrong and it is not worth turning the old
 ModalWindow into pure Wicket component due to expensiveness of the effort
 that would be spent to remain it compatible.
 Would you mind specifying the actual problems with request
 lifecycle? And how exactly would a pure wicket modal window look
 like? No javascript?

 The same about tree components. The API is very difficult to comprehend.
 Component does not work as I expect in dynamic context. But thankfully
 Sven
 implemented different implementation that does what is expect and usable
 as
 well as DataTable component. I believe forking and fixing the original
 component would be much more expensive. After that so many people should
 start complaining about that to convince core team that there is not just
 one person who is experiencing problems. It is always difficult to
 accomplish.
 I would like to have some clarification on this. What is so difficult
 about the Wicket Tree API? (apart from the fact that it uses swing
 TreeModel which seem to be too confusing for some people). What does
 dynamic context mean? Assuming you have properly implemented
 TreeModel that fires the proper notifications, wicket tree is capable
 for updating itself on ajax request by only transmitting the changed
 part to the clients. How much more dynamic can you get?
 
 For next version we will probably ditch swing TreeModel for something
 simpler but we will still need some kind of modal change notification.
 Wicket tree has many objectives, simplicity is only one of them.
 Having simple tree is nice as long as you don't have to refresh the
 entire thing every time you expand a node or add a node child.
 
 -Matej


 jthomerson wrote:

 Why create your own?  Submit a patch to fix what you see is wrong with
 the current one.  Everyone wins.

 --
 Jeremy Thomerson
 http://www.wickettraining.com




 On Tue, Jul 28, 2009 at 12:20 PM, Vladimir Kkoval...@gmail.com wrote:

 ModalWindow (being a wicket cheat :) ) deserves a sole book of tricks.
 I'll
 definitely author my own modal window unless someone fixes the original
 one.
 -1 on including ModalWindow to the book.


 egolan74 wrote:

 I can't wait for yet another great Wicket book.
 I will surly buy it.

 regarding tricks,
 using Modal window can be nice.
 Integrating

Re: Twenty Six Wicket Tricks


Ok then. I'm a noob in maven and ... I even don't know how to make a
quickstart of this problem for you. I have never done Wicket project from
scratch. But I have just found a free maven by example book and started to
read. I will be back soon :)


Matej Knopp-2 wrote:
 
 This would be then a bug in nested forms support and not in the modal
 window itself. If a form inside modal window is submitted only that
 form should be processed. I still don't understand what problem
 exactly this fixes.
 
 -Matej
 
 On Tue, Jul 28, 2009 at 10:04 PM, Vladimir Kkoval...@gmail.com wrote:

 The following class fixes the problem. It is the evidence of mismatch I'm
 saying about.

 public class ModalWindowFormT extends FormT {
        public ModalWindowForm(String id) {
                super(id);
        }

       �...@override
        public Form? getRootForm() {
                Form? form = super.getRootForm();

                if ((findParent(ModalWindow.class) != null) 
 (form.findParent(ModalWindow.class) == null))
                        return this;
                else
                        return form;
        }
 }

 I assume I don't understand something. But anyway I expect following the
 least surprise rule.



 Matej Knopp-2 wrote:

 On Tue, Jul 28, 2009 at 8:31 PM, Vladimir Kkoval...@gmail.com wrote:

 Jeremy,

 from my perspective ModalWindow is a mix of javascript widget that
 works
 in
 non-wicket mode and an wicket wrapper that bridges js widget with
 wicket.
 It
 is always created at the body level. That's why I said it's a cheat.
 Thus
 are problems with form submitting when nested forms are used.
 There is a good reason why the modal window has to be created on body
 level. That's the only reliable way to have element
 with absolute position. If you create the DOM structure deeper you are
 risking that a container has position:relative somewhere which will
 essentially break it. Welcome to the wonderful world of CSS.

 Community
 introduced a solution (a wrapping form that is threated as the root) to
 work
 around the mismatch of ModalWindow structure. There is an issue
 registered
 about that. But Matej keeps stating that we should put MW into a form.
 What
 says that he is not aware what the problem is. And there are more
 problems
 caused by the fact that the form element is created by javascript.
 Is it, really?

 I've already explained why the DOM structure is created on root level.
 If you have form component inside modal window, chances are that
 wicket will (to support nested forms) render it as div. If this
 happens it is no longer possible to serialize the form when doing an
 ajax submit. That's why the actual modal window markup contains a real
 form.

 And this is why it is necessary to put a modal window inside a form if
 you want to have form in modal window. What we should have done is to
 put a wicket form inside the modal window panel itself (just to force
 all forms in modal window content) to be rendered as nested. But for
 some reason i thought that a simple mention in javadoc about putting
 modal window to form would be sufficient. My bad.


 From the other hand I believe it is possible to write pure Wicket
 component
 that would be as trice as simpler and won't suffer with problems with
 request lifecycle. Probably I'm wrong and it is not worth turning the
 old
 ModalWindow into pure Wicket component due to expensiveness of the
 effort
 that would be spent to remain it compatible.
 Would you mind specifying the actual problems with request
 lifecycle? And how exactly would a pure wicket modal window look
 like? No javascript?

 The same about tree components. The API is very difficult to
 comprehend.
 Component does not work as I expect in dynamic context. But thankfully
 Sven
 implemented different implementation that does what is expect and
 usable
 as
 well as DataTable component. I believe forking and fixing the original
 component would be much more expensive. After that so many people
 should
 start complaining about that to convince core team that there is not
 just
 one person who is experiencing problems. It is always difficult to
 accomplish.
 I would like to have some clarification on this. What is so difficult
 about the Wicket Tree API? (apart from the fact that it uses swing
 TreeModel which seem to be too confusing for some people). What does
 dynamic context mean? Assuming you have properly implemented
 TreeModel that fires the proper notifications, wicket tree is capable
 for updating itself on ajax request by only transmitting the changed
 part to the clients. How much more dynamic can you get?

 For next version we will probably ditch swing TreeModel for something
 simpler but we will still need some kind of modal change notification.
 Wicket tree has many objectives, simplicity is only one of them.
 Having simple tree is nice as long as you don't have to refresh the
 entire thing every time you expand a node or add a node child.

 -Matej


 jthomerson wrote:

Re: Twenty Six Wicket Tricks



Matej Knopp-2 wrote:
 
 Modal Window is an ajax component. Submitting it with regular submit
 is not supported and it never was.
 

But I would like to have AjaxFallbackModalWindow that survives page refresh.
Why not author my own if the aims are different? Probably requirements we
have are far from being accepted as common.



 Again, modal window doesn't support regular submits (by design) so if
 you want to do file upload you'll have to use a hidden iframe or some
 other approach like that.
 

IMO, Iframe is not an approach it is a work around the limitation (made by
design) :)



 I just looked at jquery dialog example. The dialog is declared in
 markup but it is then reparented as top level DOM element. Same thing
 wicket modalwindow does.
 

What is especial in my case is that the page height is limited by the window
height and contains a srollable div within. Taking into account that the
browsers we support works well with fixed positioning and assuming that the
following excerpt works:



 Fixed positioning is a special case of absolute positioning. For fixed
 elements, the containing block is always taken to be the viewport of the
 browser window.
 

It seems to be pretty doable. But it needs investigation. I haven't tried
yet.



Anyway it is possible to do what the modal.js is doing by Wicket means and
don't have a component tree mismatch with DOM.
 
 Is it really? Mind sharing with me how?
 

In case if the position:fixed does not help I would subclass a Form and make
it a container of ModalWindows. Then by placing the
modal-window-container-form at the body level I would acquire a new
ModalWindow from the container. Does it make sense?

-- 
View this message in context: 
http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p24708596.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Twenty Six Wicket Tricks


We developed a RAD framework that builds page design dynamically completely
basing on metadata. So there is no any concrete page that I could extract.

I believe it would be more convinient for you and simpler for me to just
have a look at the concrete page without dynamic layout.


Matej Knopp-2 wrote:
 
 Doesn't really have to be a complete quickstart. Put the pages with
 markup in a zip (without any external references to your daos, etc).
 That should be enough.
 
 -Matej
 
 On Tue, Jul 28, 2009 at 11:13 PM, Vladimir Kkoval...@gmail.com wrote:

 Ok then. I'm a noob in maven and ... I even don't know how to make a
 quickstart of this problem for you. I have never done Wicket project from
 scratch. But I have just found a free maven by example book and started
 to
 read. I will be back soon :)


 Matej Knopp-2 wrote:

 This would be then a bug in nested forms support and not in the modal
 window itself. If a form inside modal window is submitted only that
 form should be processed. I still don't understand what problem
 exactly this fixes.

 -Matej

 On Tue, Jul 28, 2009 at 10:04 PM, Vladimir Kkoval...@gmail.com wrote:

 The following class fixes the problem. It is the evidence of mismatch
 I'm
 saying about.

 public class ModalWindowFormT extends FormT {
        public ModalWindowForm(String id) {
                super(id);
        }

       �...@override
        public Form? getRootForm() {
                Form? form = super.getRootForm();

                if ((findParent(ModalWindow.class) != null) 
 (form.findParent(ModalWindow.class) == null))
                        return this;
                else
                        return form;
        }
 }

 I assume I don't understand something. But anyway I expect following
 the
 least surprise rule.



 Matej Knopp-2 wrote:

 On Tue, Jul 28, 2009 at 8:31 PM, Vladimir Kkoval...@gmail.com wrote:

 Jeremy,

 from my perspective ModalWindow is a mix of javascript widget that
 works
 in
 non-wicket mode and an wicket wrapper that bridges js widget with
 wicket.
 It
 is always created at the body level. That's why I said it's a cheat.
 Thus
 are problems with form submitting when nested forms are used.
 There is a good reason why the modal window has to be created on body
 level. That's the only reliable way to have element
 with absolute position. If you create the DOM structure deeper you are
 risking that a container has position:relative somewhere which will
 essentially break it. Welcome to the wonderful world of CSS.

 Community
 introduced a solution (a wrapping form that is threated as the root)
 to
 work
 around the mismatch of ModalWindow structure. There is an issue
 registered
 about that. But Matej keeps stating that we should put MW into a
 form.
 What
 says that he is not aware what the problem is. And there are more
 problems
 caused by the fact that the form element is created by javascript.
 Is it, really?

 I've already explained why the DOM structure is created on root level.
 If you have form component inside modal window, chances are that
 wicket will (to support nested forms) render it as div. If this
 happens it is no longer possible to serialize the form when doing an
 ajax submit. That's why the actual modal window markup contains a real
 form.

 And this is why it is necessary to put a modal window inside a form if
 you want to have form in modal window. What we should have done is to
 put a wicket form inside the modal window panel itself (just to force
 all forms in modal window content) to be rendered as nested. But for
 some reason i thought that a simple mention in javadoc about putting
 modal window to form would be sufficient. My bad.


 From the other hand I believe it is possible to write pure Wicket
 component
 that would be as trice as simpler and won't suffer with problems with
 request lifecycle. Probably I'm wrong and it is not worth turning the
 old
 ModalWindow into pure Wicket component due to expensiveness of the
 effort
 that would be spent to remain it compatible.
 Would you mind specifying the actual problems with request
 lifecycle? And how exactly would a pure wicket modal window look
 like? No javascript?

 The same about tree components. The API is very difficult to
 comprehend.
 Component does not work as I expect in dynamic context. But
 thankfully
 Sven
 implemented different implementation that does what is expect and
 usable
 as
 well as DataTable component. I believe forking and fixing the
 original
 component would be much more expensive. After that so many people
 should
 start complaining about that to convince core team that there is not
 just
 one person who is experiencing problems. It is always difficult to
 accomplish.
 I would like to have some clarification on this. What is so difficult
 about the Wicket Tree API? (apart from the fact that it uses swing
 TreeModel which seem to be too confusing for some people). What does
 dynamic context mean? Assuming you have properly implemented

Re: reuseitems problems


Hmm ... i can imagine the only case - somewhere resolveObject() method is
called during deserialization.
But I'm afraid your code don't have such a method and the cause is
different.


MartinM wrote:
 
 I do not know exactly what happens, but if I run the debugger I can
 see thet the page seen by the formcomponents' propertymodels is in a
 different state than the one actually holding the form components.
 
 I wonder if ajax has something to do with this, because only part of
 the page is refreshed via ajax. Maybe the parent page and the
 refreshed ajax panel remain in different serialization graphs?
 
 **
 Martin
 
 2009/7/28 Vladimir K koval...@gmail.com:

 trying to undertand what is happening in your case. When the page is
 serialized the steam contains the whole graph, including the ListView and
 it's items and the page default model and the ListView items models. When
 the page is deserialized, the whole graph is restored including page, its
 model, items and their models. My understanding is that in your case the
 items models are the old ones that was in the previous version of the
 page,
 how could it be? Or I didn't get what you were saying.


 MartinM wrote:

 Or session store.. anyways, that's not relevant. The important fact is
 that the copies are different.

 **
 Martin

 2009/7/28 Martin Makundi martin.maku...@koodaripalvelut.com:
 why do you get Page instance 2 on page refresh?

 Wicket always deserializes page state from diskstore.. so it is a copy.

 **
 Martin



 MartinM wrote:

 please describe the context. I don


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 View this message in context:
 http://www.nabble.com/reuseitems-problems-tp24702133p24705851.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/reuseitems-problems-tp24702133p24708835.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to determine which behavior corresponds to the currently handled request target

2009-07-27 Thread Vladimir K


Could anyone shed light on that?
-- 
View this message in context: 
http://www.nabble.com/How-to-determine-which-behavior-corresponds-to-the-currently-handled--request-target-tp24635282p24680015.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to determine which behavior corresponds to the currently handled request target

2009-07-27 Thread Vladimir K

I'm trying to add AjaxFormComponentUpdating behavior to FormComponentPanel.
The latter is inherintly not suited for Ajax requests. So I have to use
some workarounds to update model of FormComponentPanel by ajax update on
onblur js event on inner input, see code posted here. It works for now but
I'm afraid I should bypass updating of model when whole form is submitted
via ajax. So I'm trying to figure out what particular behavior is in
progress.

From the other hand you probably know different way how to add
AjaxFormComponentUpdatingBehaviour to DateField component. Any thoughts are
welcome.

igor.vaynberg wrote:

you can use AjaxRequestTarget.get() to see if an ajax request is being
processed.

-igor

On Mon, Jul 27, 2009 at 5:41 AM, Vladimir Kkoval...@gmail.com wrote:

Could anyone shed light on that?
--
View this message in context:
http://www.nabble.com/How-to-determine-which-behavior-corresponds-to-the-currently-handled--request-target-tp24635282p24680015.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

--
View this message in context:
http://www.nabble.com/How-to-determine-which-behavior-corresponds-to-the-currently-handled--request-target-tp24635282p24686879.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


Nested tree and tree table seems promicing.

What I missed in your example is single-selection mode, and sortable headers
with filters.

One of my the upcoming tasks is to build a selector component that knows
whether the object is hierarchical and puts inside a datatable with
navigator or treetable. Since wicket-extentions project has completely
incompatible components in this regard my component that unifies both looks
pretty complex to do. Your treetable components seems to be more close to
datable so it definitely might come in handy.

When are you going to finalize the component contract (api)?


svenmeier wrote:
 
 Sure, wicket-tree is still in its conception phase.
 
 I'll tidy up the project structure soon.
 
 Sven
 
 On Sa, 2009-07-25 at 18:57 -0400, James Carman wrote:
 So is the project a war (since it runs with jetty:run)?  Wouldn't that
 make
 it hard to use in other projects?
 
 On Jul 25, 2009 6:18 PM, Major Péter majorpe...@sch.bme.hu wrote:
 
 Cool, that was exactly, what I was looking for.
 Thanks.
 
 Peter
 
 2009-07-26 00:06 keltezéssel, Sven Meier írta:
 
   Hi Peter,   // at the chekcedfoldercontent (nested tree) example
 if I
 check the  parent, t...
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24665096.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


Why you don't extend ITreeProvider from IDataProvider? They looks compatible
for now. I can add IDataProvider to my implementation class and delegate
roots() to iterator(). From the other hand it is just extra method.

One thing to mention. There should be full row select option. You just
need to add a selected class attribute for selected TDs.


Vladimir K wrote:
 
 Nested tree and tree table seems promicing.
 
 What I missed in your example is single-selection mode, and sortable
 headers with filters.
 
 One of my the upcoming tasks is to build a selector component that knows
 whether the object is hierarchical and puts inside a datatable with
 navigator or treetable. Since wicket-extentions project has completely
 incompatible components in this regard my component that unifies both
 looks pretty complex to do. Your treetable components seems to be more
 close to datable so it definitely might come in handy.
 
 When are you going to finalize the component contract (api)?
 
 
 svenmeier wrote:
 
 Sure, wicket-tree is still in its conception phase.
 
 I'll tidy up the project structure soon.
 
 Sven
 
 On Sa, 2009-07-25 at 18:57 -0400, James Carman wrote:
 So is the project a war (since it runs with jetty:run)?  Wouldn't that
 make
 it hard to use in other projects?
 
 On Jul 25, 2009 6:18 PM, Major Péter majorpe...@sch.bme.hu wrote:
 
 Cool, that was exactly, what I was looking for.
 Thanks.
 
 Peter
 
 2009-07-26 00:06 keltezéssel, Sven Meier írta:
 
   Hi Peter,   // at the chekcedfoldercontent (nested tree) example
 if I
 check the  parent, t...
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24665206.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


I find the source code pretty clean and easy to understand. Especially if you
are familiar with DataTable component. For instance I see that it is easy to
use Ajax versions of Toolbars instead of static (however
DefaultAjaxFallbackTreeTable would be usefull)

Looking forward for the post-conception version :)

I would suggest adding it to the Wicket right next to DataTable.

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24665301.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Reading Wicket source code


For me the magic is how wicket is managing pages and their versions. For
instance I realized that it increments version when preparing the page for
render. But when I was debugging the code related to version manager I felt
lost :)
All the other stuff is pretty complex but not difficult to understand.


MartinM wrote:
 
 Also one very benefiial point of view is just to code something and
 when you find a bug (either in your own code or Wicket), debug through
 wicket source and find the cause. If it's a wicket bug - contribute
 quickstart to jira that repeats the bug. I have learned myself quite a
 bit by doing this. However, I am still a bit puzzled with wicket's
 request cycle, there seems to still to be some magic going on ... ;)
 
 **
 Martin
 
 2009/7/24 Pierre Goupil goupilpie...@gmail.com:
 Good evening,

 In order to learn Wicket as well as good Java coding ^ ^, I'd like to
 read
 Wicket source code. It's been a couple of months since I use it, so I
 have a
 general user-view on it.

 Do you have advice ? Where should I start it all ? Is there any typical
 workflow through the code-base for such a matter ?

 Hope to hear from you soon, guys !

 Regards,

 Pierre



 --
 Sans amis était le grand maître des mondes,
 Eprouvait manque, ce pour quoi il créa les esprits,
 Miroirs bienveillants de sa béatitude.
 Mais au vrai, il ne trouva aucun égal,
 Du calice du royaume total des âmes
 Ecume jusqu'à lui l'infinité.

 (Schiller, l'amitié)

 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Reading-Wicket-source-code-tp24651141p24665454.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


Just make IDataProvider in charge for sorting and filtering like DataTable
does.

Filtering in tree could be seen in Eclipse preferences for instance.


svenmeier wrote:
 
 Hi,
 
 I've added single selection to the example. I'm not sure how sorting and
 filtering applies to hierarchical data though.
 
 API will be finalized after sufficient feedback from the Wicket
 community - so keep on firing questions ;).
 
 Sven
 
 On So, 2009-07-26 at 01:51 -0700, Vladimir K wrote:
 Nested tree and tree table seems promicing.
 
 What I missed in your example is single-selection mode, and sortable
 headers
 with filters.
 
 One of my the upcoming tasks is to build a selector component that knows
 whether the object is hierarchical and puts inside a datatable with
 navigator or treetable. Since wicket-extentions project has completely
 incompatible components in this regard my component that unifies both
 looks
 pretty complex to do. Your treetable components seems to be more close to
 datable so it definitely might come in handy.
 
 When are you going to finalize the component contract (api)?
 
 
 svenmeier wrote:
  
  Sure, wicket-tree is still in its conception phase.
  
  I'll tidy up the project structure soon.
  
  Sven
  
  On Sa, 2009-07-25 at 18:57 -0400, James Carman wrote:
  So is the project a war (since it runs with jetty:run)?  Wouldn't that
  make
  it hard to use in other projects?
  
  On Jul 25, 2009 6:18 PM, Major Péter majorpe...@sch.bme.hu wrote:
  
  Cool, that was exactly, what I was looking for.
  Thanks.
  
  Peter
  
  2009-07-26 00:06 keltezéssel, Sven Meier írta:
  
Hi Peter,   // at the chekcedfoldercontent (nested tree)
 example
  if I
  check the  parent, t...
  
  
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
  
  
  
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24665608.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project



svenmeier wrote:
 
 ITreeProvider and IDataProvider are not exactly compatible, I don't
 think we gain anything by extending the former from the latter.
 

I don't insist. But you do have IDataProvider wrapper over ITreeProvider in
TableTree.java :)



 Selection is not part of the tree components. There are just to many
 different notions of selection:
 - single/multiple selection
 - subtree selection
 - continuous/discontinuous selection
 - several selections on a single tree (see example with checkable *and*
 selectable content)
 - no selection at all
 - ...
 
 IMHO it's better to leave these requirements out of a tree
 implementation.
 If you need a selected class attribute on a TableTree, override
 #newRowItem() and do it yourself. Ever noticed that DataTable has no
 notion of selection too?
  tag. Whatever.

I din't find API to control expanded state of node. Say I would like to add
a button to collapse all nodes, or I would like to save expanded state and
restore when the user returns back to this page again.

Please explain how I should operate with the state of tree (what nodes are
expanded and what nodes are selected). Once I realize I will be able to
override newRowItem properly.

Also you have 2 Branch classes. I find it confusing a bit.

I'm going to play with TreeTable tomorrow.

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24666766.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


It does not. It is stated at the bottom of the home page
http://code.google.com/p/wicket-tree/
For ajax updates it should behave not worse than DataTable component.

Matej, I find the idea of re-using data provider, columns and cells
developed for DataTable very important.


Matej Knopp-2 wrote:
 
 Does TableTree support partial (ajax) updates?
 
 -Matej
 
 On Sun, Jul 26, 2009 at 3:00 PM, Vladimir Kkoval...@gmail.com wrote:


 svenmeier wrote:

 ITreeProvider and IDataProvider are not exactly compatible, I don't
 think we gain anything by extending the former from the latter.


 I don't insist. But you do have IDataProvider wrapper over ITreeProvider
 in
 TableTree.java :)



 Selection is not part of the tree components. There are just to many
 different notions of selection:
 - single/multiple selection
 - subtree selection
 - continuous/discontinuous selection
 - several selections on a single tree (see example with checkable *and*
 selectable content)
 - no selection at all
 - ...

 IMHO it's better to leave these requirements out of a tree
 implementation.
 If you need a selected class attribute on a TableTree, override
 #newRowItem() and do it yourself. Ever noticed that DataTable has no
 notion of selection too?
  tag. Whatever.

 I din't find API to control expanded state of node. Say I would like to
 add
 a button to collapse all nodes, or I would like to save expanded state
 and
 restore when the user returns back to this page again.

 Please explain how I should operate with the state of tree (what nodes
 are
 expanded and what nodes are selected). Once I realize I will be able to
 override newRowItem properly.

 Also you have 2 Branch classes. I find it confusing a bit.

 I'm going to play with TreeTable tomorrow.

 --
 View this message in context:
 http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24666766.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24666861.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: advice about ImageSubmitButton and AjaxImageSubmitButton


In addition I need something like AjaxFallbackImageSubmitButton. Just to let
you know that he is not alone :)

From my perspective Wicket should provide basic Button and mixins (mostly
behaviours) to add Ajax, AjaxFallback, Image, Submit etc. So users could
just get the button they need by adding mixins like bricks to the wall.


Martijn Dashorst wrote:
 
 You are the first one to miss them, so they are not used very often :).
 They are easy enough to create yourself, -1 on adding more bloated buttons
 to the core.
 
 Martijn
 
 On Nov 29, 2007 10:17 AM, xiefei xie___...@hotmail.com wrote:
 
 In the Button type hierachy, there are ImageButton and
 AjaxSubmitButton,
 but no ImageSubmitButton or AjaxImageSubmitButton found.

 These two are also very often used in practice, worth being provided as
 standard component.
 _
 Windows Live Photo gallery 数码相机的超级伴侣，轻松管理和编辑照片，还能制作全景美图！
 http://get.live.cn/product/photo.html
 
 
 
 
 -- 
 Buy Wicket in Action: http://manning.com/dashorst
 Apache Wicket 1.3.0-rc1 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
 
 

-- 
View this message in context: 
http://www.nabble.com/advice-about-ImageSubmitButton-and-AjaxImageSubmitButton-tp14022088p24671164.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


Sven,

i added TableTree (why not TreeTable?) to my panel and added a button to
switch between tree and table representation.

The problem is that DataTable relies on the user that binds it to the
table tag at the time when your TableTree contains table within.

It is not a big deal just an unconvinience. I have 12 lines of code and 5
lines of markup instead of single addOrReplace call.

Hmm ... from the other hand I see a showstopper - I can't add my attributes
and styles to TableTree because it is hidden inside. That's a big problem.

Please consider removing table tags from TableTree markup. You can make
sure that the user provided correct tag in onComponentTag method.
-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24671586.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [ANN] wicket-tree project


Since you update AbstractTree in ajax request I can't omit etra 'div' tag
that encloses table tag neither by using wicket:component nor by calling
setRenderBodyOnly(true).


Vladimir K wrote:
 
 Sven,
 
 i added TableTree (why not TreeTable?) to my panel and added a button to
 switch between tree and table representation.
 
 The problem is that DataTable relies on the user that binds it to the
 table tag at the time when your TableTree contains table within.
 
 It is not a big deal just an unconvinience. I have 12 lines of code and 5
 lines of markup instead of single addOrReplace call.
 
 Hmm ... from the other hand I see a showstopper - I can't add my
 attributes and styles to TableTree because it is hidden inside. That's a
 big problem.
 
 Please consider removing table tags from TableTree markup. You can make
 sure that the user provided correct tag in onComponentTag method.
 

-- 
View this message in context: 
http://www.nabble.com/-ANN--wicket-tree-project-tp24660403p24672778.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: how to create a BookmarkablePageLink for the particular page instance

2009-07-25 Thread Vladimir K

It seems that I can override page factory in session and re-use existing page
basing on the parameters values.

Alexandru Objelean wrote:

Bookmarkable page doesn't have state and can be created using
PageParameters. Each request for a bookmarkable page will cause a creation
of new instance of that page. In your case, if the page instance have some
state (is session relative), then there is no way to create a bookmarkable
link for it.

Alex Objelean

Vladimir K wrote:

I created a breadcrumbs panel that automatically creates a series of
bookmarkable links from the home page to the page that displays a details
of
currently viewing entity instance.
Usually it looks like for instance
home|folders|folder1|folder1.1|document

From the other hand when the user comes to this particular document by
opening folders and then the document itself she produces a page versions
that makes page history. There is an button back or close on the page
that returns the user to the previous page in the history.

As the result breadcrumbs and history forms two different ways of
navigation
but they both are natural and required.

The problem is that clicking on the particular link in breadcrumb panel
leads to creating a new version of page. I use HybridUrlCodingStrategy
and
it seems pretty possible to add version attributes to the url. But I
don't
know how to do it in compatible manner. It seems that the only link that
forms the bookmarkable URL using hybrid strategy is the
BookmarkablePageLink. But it does not accept anything from the particular
page version.

Please help

--
View this message in context:
http://www.nabble.com/how-to-create-a-BookmarkablePageLink-for-the-particular-page-instance-tp24659102p24659419.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: how to create a BookmarkablePageLink for the particular page instance

2009-07-25 Thread Vladimir K


Certainly, parameters are just name of object class and object code/id.
But actually I'm saying that I can create store PageReference with its
related PageParametes in session and using PageParameters from the request
to obtain a Page instance from page store.
The only thing I'm not sure is the lifecycle of values in such a cache.

AFAK overriding page factory is the only way how to make a page singleton in
the session. There are plenty of pages that should behave as singleton.
There would be the other way if it was easy to split Tree and its DYNAMIC
state. Unfortunately tree is very difficult in restoring its state.

The user don't want to expand tree items every time she has to return back
to the page.


Alexandru Objelean wrote:
 
 If you can restore the page state from passed PageParameters, then it is
 doable...
 
 Alex Objelean
 
 

-- 
View this message in context: 
http://www.nabble.com/how-to-create-a-BookmarkablePageLink-for-the-particular-page-instance-tp24659102p24659535.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Serialization of a page with a long and dynamic list of records

2009-07-25 Thread Vladimir K


I realized that it is not possible to support bookmarkable page links in
breadcrumbs panel for already instantiated pages because it won't work with
multiple browser windows and tabls.

Therefore I can use bookmarkable links for non-instantiated pages only. It
can be easily accomplished with existing components. Hmm ... wrong word. ...
EASIER than overriding page factory.
-- 
View this message in context: 
http://www.nabble.com/how-to-create-a-BookmarkablePageLink-for-the-particular-page-instance-tp24659102p24662729.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: how to strip wicket tags for particular component

2009-07-20 Thread Vladimir K


For now I use the following workaround

public class CleanBorder extends Border {
private boolean savedStripWicketTags; 

public CleanBorder(String id) {
super(id);
setRenderBodyOnly(true);
getBodyContainer().setRenderBodyOnly(true);
}

public CleanBorder(String id, IModel? model) {
super(id, model);
setRenderBodyOnly(true);
getBodyContainer().setRenderBodyOnly(true);
}

@Override
protected void onAfterRender() {
super.onAfterRender();

Application.get().getMarkupSettings().setStripWicketTags(savedStripWicketTags);
}

@Override
protected void onBeforeRender() {
savedStripWicketTags =
Application.get().getMarkupSettings().getStripWicketTags();
Application.get().getMarkupSettings().setStripWicketTags(true);
super.onBeforeRender();
}


that looks like a hack. I would prefer a settings on the MarkupContainer
that by default uses the application settings but in case of border can be
overridden.


Vladimir K wrote:
 
 I'm trying to convert main menu into components to control visibility of
 items depending on the user logged in and the context.
 I use borders to wrap menu item into li tags.
 
 The problem is that the rendered markup contains additional
 wicket:border
 and wicket:body tags. They breaks the menu and it is eventually
 displayed
 as the simple list.
 
 Stripping wicket tags at the application level would obviously solve the
 problem. But I'd like to keep wicket tags for most markup and strip only
 for
 menu.
 
 Can I override Border class somehow and strip wicket tags manually?
 
 

-- 
View this message in context: 
http://www.nabble.com/how-to-strip-wicket-tags-for-particular-component-tp24568122p24568909.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: how to strip wicket tags for particular component

2009-07-20 Thread Vladimir K


Mathias,

I just posted right after your post :) Anyway thanks.

The problem is that you can not restore origianal settings when the body of
the border is being rendered. At lease it is difficult to figure out what
workaround I could employ.

Thankfully I haven't to care about that in my case so I use it.


Mathias Nilsson wrote:
 
 This may not be the best solution but it should work
 
 DateTextField  dateField = new DateTextField(date, new ModelDate(new
 Date())){
   @Override
   protected void onBeforeRender() {
   
   
 Application.get().getMarkupSettings().setStripWicketTags(true);
   super.onBeforeRender();
   }
   @Override
   protected void onAfterRender() {
   
 Application.get().getMarkupSettings().setStripWicketTags(false);
   super.onAfterRender();
   }
 
   }; 
 

-- 
View this message in context: 
http://www.nabble.com/how-to-strip-wicket-tags-for-particular-component-tp24568122p24568972.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: MixedHybridUrlCodingStrategy wanted

2009-07-13 Thread Vladimir K


I didn't find it easy to do it myself. By easy I mean what I can accomplish
within 15 mins.

From the first glance it looks just like a mix of two strategies but it
actually does not. MixedHybridUrlCodingStrategy should handle all the
parameters delimited by slashes and some of them have names omitted.
Original Mixed strategy operates with regular parameters syntax. I believe
it would take some hours to study what strategies do internally and
implement and test mixed solution. I hoped someone have already tried that.

Unfortunately I didn't find anything by google and nabble so I posted the
question here. If you could point me some old discussion I'd appreciate.


Erik van Oosten wrote:
 
 It is fairly easy to construct it yourself. Just look at the code of 
 MixedParamUrlCodingStrategy, copy it and replace the class you're 
 extending to the corresponding HybridUrlCodingStrategy.
 
 Its also on the mailing list, search the archives. Lastly, the 
 annotation based mounting project (forgot the name) contains it.
 
 Regards,
  Erik.
 
 
 
 Vladimir Kovalyuk wrote:
 Is there a worked combination of HybridUrlCodingStrategy and
 MixedParamUrlCodingStrategy? What is missed in the latter is ability to
 stay
 bookmarkable after reaction on actions.

   
 
 
 -- 
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/MixedHybridUrlCodingStrategy-wanted-tp24448528p24457097.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: MixedHybridUrlCodingStrategy wanted

2009-07-13 Thread Vladimir K


Thanks very much!

Why not suggest it as a patch to wicket core?


Erik van Oosten wrote:
 
 Hi Vladimir,
 
 You are right. Now I look at it, it is clearly more complex then I 
 remembered.
 
 You can get my version here: http://pastie.org/543892
 
 Regards,
 Erik.
 
 
 Vladimir K wrote:
 I didn't find it easy to do it myself. By easy I mean what I can
 accomplish
 within 15 mins.

 From the first glance it looks just like a mix of two strategies but it
 actually does not. MixedHybridUrlCodingStrategy should handle all the
 parameters delimited by slashes and some of them have names omitted.
 Original Mixed strategy operates with regular parameters syntax. I
 believe
 it would take some hours to study what strategies do internally and
 implement and test mixed solution. I hoped someone have already tried
 that.

 Unfortunately I didn't find anything by google and nabble so I posted the
 question here. If you could point me some old discussion I'd appreciate.


 Erik van Oosten wrote:
   
 It is fairly easy to construct it yourself. Just look at the code of 
 MixedParamUrlCodingStrategy, copy it and replace the class you're 
 extending to the corresponding HybridUrlCodingStrategy.

 Its also on the mailing list, search the archives. Lastly, the 
 annotation based mounting project (forgot the name) contains it.

 Regards,
  Erik.



 Vladimir Kovalyuk wrote:
 
 Is there a worked combination of HybridUrlCodingStrategy and
 MixedParamUrlCodingStrategy? What is missed in the latter is ability to
 stay
 bookmarkable after reaction on actions.

   
   
 -- 
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 

   
 
 -- 
 
 Erik van Oosten
 http://day-to-day-stuff.blogspot.com/
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/MixedHybridUrlCodingStrategy-wanted-tp24448528p24457377.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: model detached many times

2009-07-13 Thread Vladimir K


Martijn,

you probably mean how chained models would be detached. So instead of
propagating detach in IChainedModel they would be detached automatically?

Is there a vision how it would be accomplished?


Martijn Dashorst wrote:
 
 Automatic detachment is one of the things we're looking into for 1.5 or
 1.6
 
 Martijn
 
 On Fri, Jul 10, 2009 at 12:47 PM, James
 Carmanjcar...@carmanconsulting.com wrote:
 Perhaps there could be some sort of registry for models that need to
 be detached.  Then, after rendering, they're all detached as part of
 the request cycle?

 On Fri, Jul 10, 2009 at 4:00 AM, Martijn
 Dashorstmartijn.dasho...@gmail.com wrote:
 If you share a model between components, then yes–each component will
 call detach on the model. That's encapsulation for you: one component
 doesn't know about another component, so it can't know that its model
 was detached.

 Martijn

 On Fri, Jul 10, 2009 at 9:41 AM, Ian MacLartyian.macla...@gmail.com
 wrote:
 I put a breakpoint on the detach method of my model and had a look at
 the Components whose detach methods were called higher up in the stack
 trace.  It looks like the detach method on the model is being called
 for every component on the page.  All the components link to the same
 underlying model via a CompoundPropertyModel, so I guess lots of calls
 to the detach method of the model should be expected?

 Ian.

 On Fri, Jul 10, 2009 at 5:17 PM, Eelco
 Hilleniuseelco.hillen...@gmail.com wrote:
 It's fine if a model if detached multiple times in a request, but
 hundreds for a single model sounds suspicious. Try to trace what
 components fire the detach method and see if there's anything weird
 with that.

 Eelco

 On Thu, Jul 9, 2009 at 11:21 PM, Ian MacLartyian.macla...@gmail.com
 wrote:
 Hi,

 I noticed that my IDetachable model is being detached many times
 (hundreds) for each request.  Is that something to worry about, or is
 it just because the detach method is called for each component that
 points to this model?

 Ian.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 
 
 -- 
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/model-detached-many-times-tp24422368p24457432.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket vs vaadin clarifications

2009-07-09 Thread Vladimir K


Joonas,

I'm wondering why your comparison table does not contain ZK?

I find Vaadin demos not very responsive. They react very very slowly. At
that internet responses are less than 100ms and response size mostly less
than 1K and there are only one-two roundtrips for each user action. The same
about every GWT application.

Wicket ajax responses in our application sometimes exceeds 30k and I don't
notice any lags.


Joonas Lehtinen wrote:
 
 Hi all, 
 
 If there are any errors in our comparison table, please accept my
 apologies - 
 I wrote the original version of the table. I take care that any errors
 will be
 corrected as soon as possible. Just to clarify the situation - I think
 that 
 wicket is a nice framework and really want to give it a fair comparison. 
 In my opinion, Vaadin is better for some applications and Wicket for some.
 
 

-- 
View this message in context: 
http://www.nabble.com/wicket-vs-vaadin-clarifications-tp24353170p24409410.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket vs vaadin clarifications

2009-07-09 Thread Vladimir K




Joonas Lehtinen wrote:
 
 
 I only included frameworks that I get the most questions about. We
 definitely should include ZK also, but validating some facts would need
 some quick research. If you are familiar with ZK, could you contribute ZK
 column to the comparison table?
 

No, I'm not familiar with ZK enough to contribute a column. Amount of its
ads is quite impressive so I assume it has a certain piece of market pie.
However I refused ZK 'cause it looks not so attractive in technical
internals.


Joonas Lehtinen wrote:
 
 
 Vladimir K wrote:
 
 I find Vaadin demos not very responsive. They react very very slowly. At
 that internet responses are less than 100ms and response size mostly less
 than 1K and there are only one-two roundtrips for each user action. The
 same about every GWT application.
 
 
 That is strange. Did you try the demos on http://demo.vaadin.com/ that is
 hosted in USA (Amazon EC2 EAST) or did you run the demos from local server
 (download vaadin package and run start.sh)?
 

I run online demo. It just came to my mind that this sort of discussion
probably is offtopic.
-- 
View this message in context: 
http://www.nabble.com/wicket-vs-vaadin-clarifications-tp24353170p24413008.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Prefill form not model?

2009-07-08 Thread Vladimir K


Martin,

having read the thread I didn't get why you can not modify the object
itself. OSiV shouldn't be the reason because the object should be detached
when submitting the form and it should be merged into a brand new hibernate
session.

Actually I don't see the value of always keeping in mind that the raw input
and backed object should have different values until final form submit. If
your reusable components can submit form and aren't aware about that you
can't reuse them in that sort of form. From my perspective your hack does
not seem cleaner.

What i'm doing in order to set the default value (for instance today for
date picker) is subclassing form component and initialize its model object.
It looks shorter and cleaner.


MartinM wrote:
 
 Typically to prefill a form you have the backing model object have
 sensible defaults.  i.e., a form that edits a person is given a
 person, and the person object has it's gender set to male as a
 default - that is reflected in your form when it is rendered.
 
 The problem is that it is not a NEW object. It is an old object with
 proposed new values which the user must SUBMIT in order to be stored
 into the object etc.
 
 otherwise, you could call setModelObject or perhaps setValue?
 
 Well.. that will destroy the object state, which is a different hassle.
 
 **
 Martin
 

 --
 Jeremy Thomerson
 http://www.wickettraining.com




 On Tue, Jul 7, 2009 at 8:57 AM, Martin
 Makundimartin.maku...@koodaripalvelut.com wrote:
 Hi!

 What is the proper way to prefill a wicket form (not poke the model
 before submit!!!)?

 I have used a hack:

      Field rawInputField =
 FormComponent.class.getDeclaredField(rawInput);
      rawInputField.setAccessible(true);
      rawInputField.set(component, description);

 Is there a better way?

 **
 Martin

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Prefill-form-not-model--tp24373824p24386875.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Can I make AjaxFormSubmitBehavior submit raw form data but not validate it?

2009-07-08 Thread Vladimir K


Igor, for now I'm concerned about how can I make sure that my code that
mimics form submitting lifecycles and wicket code in coming version do the
same things?

For instance the AjaxFormComponentUpdatingBehavior:

@Override
protected final void onEvent(final AjaxRequestTarget target)
{
final FormComponent? formComponent = getFormComponent();

if (getEvent().toLowerCase().equals(onblur)  
disableFocusOnBlur())
{
target.focusComponent(null);
}

try
{
formComponent.inputChanged();
formComponent.validate();
if (formComponent.hasErrorMessage())
{
formComponent.invalid();

onError(target, null);
}
else
{
formComponent.valid();
if (getUpdateModel())
{
formComponent.updateModel();
}

onUpdate(target);
}
}
catch (RuntimeException e)
{
onError(target, e);

}
}

I should do something similar but for the list of components the behavior
takes.
If the coming version of Wicket does it a bit different I would have to
insert a fork in my code that does version check:

switch(wicketVersion) {
case ...:
case ...:
}

If wicket sources had the form processing code extracted into utility class
I would employ it and be sure it should work in the new wicket version.


igor.vaynberg wrote:
 
 you can see how the submit behavior does it and replicate the parts
 you need. all these things are not using some magical internal apis.
 you are meant to build your own things when the default
 implementations do not do what you want.
 
 -igor
 
 On Tue, Jul 7, 2009 at 6:35 AM, Thierry Levequetleve...@gmail.com wrote:
 Thanks, but I was not talking about using the submit behavior.

 I was talking about the way to create my own ajax behavior to send the
 value
 of multiple form fields.

 I think this should be part of Wicket. It is not the first time I
 encounter
 this problem. The first time, I found a workaround but this time I am
 stuck.
 There should be a simple way to create an ajax behavior that will send
 the
 values from the form components we want. Maybe with the option to
 validate
 them or not.
 What do you think?

 Thierry


 2009/7/7 Stefan Malmesjö s.m.mo...@gmail.com

 I just realized that maybe you need to extend your validators, too, at
 least if you want your modelobject to be updated. And how you do that on
 a
 textfield that is required, I don't really know.

 Maybe that path is too complicated.

 /Stefan

 On 2009-07-06 22:55, Stefan Malmesjö wrote:

 Could setting visibility for the FeedbackPanel to false until the form
 has
 been properly submitted with a press of a submit button work?

 /Stefan

 On Mon, Jul 6, 2009 at 8:42 PM, Thierry Leveque
 tleve...@gmail.commailto:
 tleve...@gmail.com wrote:

    Any following on that?

    Daniel, have you been able to solve your problem? Did you wrote
    your own
    behavior?

    I have the same requirement as you and I am trying to find a quick
    way to
    solve my problem.

    Can someone point me to some examples on how to write my own Ajax
    behavior?

    Thanks

    Thierry


    On Tue, Jun 2, 2009 at 12:21, Igor Vaynberg
    igor.vaynb...@gmail.com mailto:igor.vaynb...@gmail.com wrote:

     well, if you do not want to *submit* the form then dont use
     ajaxformSUBMITbehavior :)
    
     with little work you can roll your own behavior that does a simple
     ajax get and appends whatever values you need from formcomponents
 to
     the url. that way the form is not submitted and you have access
    to the
     raw values.
    
     -igor
    
    
    
     On Tue, Jun 2, 2009 at 9:16 AM, dfernandez
     dfernan...@users.sourceforge.net
    mailto:dfernan...@users.sourceforge.net wrote:
     
     
      Yes, I know it is tricky, but the fact is I don't think I
    would really
     need
      type conversion in this case.
     
      I will try to explain myself. I have the following UI:
     
         |OPERATOR |V|
     
         |INPUT1=aBc        |     |INPUT2=DeF          |
     
      ...being OPERATOR the DropDownChoice, and both INPUT1 and
    INPUT2 two
      TextFields (String TextFields, to be precise). Both INPUT1 and
    INPUT2 are
      required (when they are visible, of course).
     
      When I change the value on OPERATOR, the UI will change,
    hiding INPUT1
     and
      INPUT2 but showing INPUT3, another TextField which should have
    the same

Re: Can I make AjaxFormSubmitBehavior submit raw form data but not validate it?

2009-07-07 Thread Vladimir K


From the ajax perspective it should be possible to submit any dom element
with its descendants. I believe it is exactly what Wicket ajax submit is
doing. IMO forms needed just for regular form submit.

We just need to change an implementation to accept a list of dom elements
instead of just one.

I don't have an opinion about reasons to handle partial form submitting
lifecycle on the server side.


tleveque wrote:
 
 Thanks, but I was not talking about using the submit behavior.
 
 I was talking about the way to create my own ajax behavior to send the
 value
 of multiple form fields.
 
 I think this should be part of Wicket. It is not the first time I
 encounter
 this problem. The first time, I found a workaround but this time I am
 stuck.
 There should be a simple way to create an ajax behavior that will send the
 values from the form components we want. Maybe with the option to validate
 them or not.
 What do you think?
 
 Thierry
 
 
 2009/7/7 Stefan Malmesjö s.m.mo...@gmail.com
 
 I just realized that maybe you need to extend your validators, too, at
 least if you want your modelobject to be updated. And how you do that on
 a
 textfield that is required, I don't really know.

 Maybe that path is too complicated.

 /Stefan

 On 2009-07-06 22:55, Stefan Malmesjö wrote:

 Could setting visibility for the FeedbackPanel to false until the form
 has
 been properly submitted with a press of a submit button work?

 /Stefan

 On Mon, Jul 6, 2009 at 8:42 PM, Thierry Leveque
 tleve...@gmail.commailto:
 tleve...@gmail.com wrote:

Any following on that?

Daniel, have you been able to solve your problem? Did you wrote
your own
behavior?

I have the same requirement as you and I am trying to find a quick
way to
solve my problem.

Can someone point me to some examples on how to write my own Ajax
behavior?

Thanks

Thierry


On Tue, Jun 2, 2009 at 12:21, Igor Vaynberg
igor.vaynb...@gmail.com mailto:igor.vaynb...@gmail.com wrote:

 well, if you do not want to *submit* the form then dont use
 ajaxformSUBMITbehavior :)

 with little work you can roll your own behavior that does a simple
 ajax get and appends whatever values you need from formcomponents
 to
 the url. that way the form is not submitted and you have access
to the
 raw values.

 -igor



 On Tue, Jun 2, 2009 at 9:16 AM, dfernandez
 dfernan...@users.sourceforge.net
mailto:dfernan...@users.sourceforge.net wrote:
 
 
  Yes, I know it is tricky, but the fact is I don't think I
would really
 need
  type conversion in this case.
 
  I will try to explain myself. I have the following UI:
 
 |OPERATOR |V|
 
 |INPUT1=aBc| |INPUT2=DeF  |
 
  ...being OPERATOR the DropDownChoice, and both INPUT1 and
INPUT2 two
  TextFields (String TextFields, to be precise). Both INPUT1 and
INPUT2 are
  required (when they are visible, of course).
 
  When I change the value on OPERATOR, the UI will change,
hiding INPUT1
 and
  INPUT2 but showing INPUT3, another TextField which should have
the same
  contents that were on INPUT1 before:
 
 |OPERATOR |V|
 
 |INPUT3=aBc|
 
  The problem is that, when changing OPERATOR, I need to read
the value
 from
  INPUT1 to set it into INPUT3, but if INPUT2 is empty I will
receive a
  validation message telling me that it is required... which it
is, but I
 just
  want Wicket to validate that when I want to *really* submit
the form, and
  not now that I am only changing the operator.
 
  Thanks.
 
  Regards,
  Daniel.
 
 
 
 
 
  igor.vaynberg wrote:
 
  how are you planning on reading the other values? you cannot
access
  the model so you will have to call getinput(), are you also
planning
  on doing type conversion yourself then?
 
  -igor
 
  2009/6/2 Daniel Fernández dfernan...@users.sourceforge.net
mailto:dfernan...@users.sourceforge.net:

  Hello,
 
  I have a form with a DropDownChoice, on which onchange
event I want
 to
  update some form components. But I need to read data from
other fields
 of
  the form for doing so, and so I added an
AjaxFormSubmitBehavior to the
  DropDownChoice.
 
  My intention is to read the data from the drop down and from
the other
  fields, and depending on these data, update some other
components...
 but
  the
  problem is that AjaxFormSubmitBehavior not only sends the
form data,
 but
  also *validates it*, which I don't want (I don't want
 validation
 messages
  to
  appear when changing the value of the drop down).
 
  If it where an AjaxButton I would be able to just

Re: Can I make AjaxFormSubmitBehavior submit raw form data but not validate it?

2009-07-07 Thread Vladimir K


Wicket has strong rules how to handle ajax form submit. Therefore partial
form submitting should be handled differently on the server side.
Anyway we could handle raw strings or invoke converter ourselves.


Vladimir K wrote:
 
 From the ajax perspective it should be possible to submit any dom element
 with its descendants. I believe it is exactly what Wicket ajax submit is
 doing. IMO forms needed just for regular form submit.
 
 We just need to change an implementation to accept a list of dom elements
 instead of just one.
 
 I don't have an opinion about reasons to handle partial form submitting
 lifecycle on the server side.
 
 
 tleveque wrote:
 
 Thanks, but I was not talking about using the submit behavior.
 
 I was talking about the way to create my own ajax behavior to send the
 value
 of multiple form fields.
 
 I think this should be part of Wicket. It is not the first time I
 encounter
 this problem. The first time, I found a workaround but this time I am
 stuck.
 There should be a simple way to create an ajax behavior that will send
 the
 values from the form components we want. Maybe with the option to
 validate
 them or not.
 What do you think?
 
 Thierry
 
 
 2009/7/7 Stefan Malmesjö s.m.mo...@gmail.com
 
 I just realized that maybe you need to extend your validators, too, at
 least if you want your modelobject to be updated. And how you do that on
 a
 textfield that is required, I don't really know.

 Maybe that path is too complicated.

 /Stefan

 On 2009-07-06 22:55, Stefan Malmesjö wrote:

 Could setting visibility for the FeedbackPanel to false until the form
 has
 been properly submitted with a press of a submit button work?

 /Stefan

 On Mon, Jul 6, 2009 at 8:42 PM, Thierry Leveque
 tleve...@gmail.commailto:
 tleve...@gmail.com wrote:

Any following on that?

Daniel, have you been able to solve your problem? Did you wrote
your own
behavior?

I have the same requirement as you and I am trying to find a quick
way to
solve my problem.

Can someone point me to some examples on how to write my own Ajax
behavior?

Thanks

Thierry


On Tue, Jun 2, 2009 at 12:21, Igor Vaynberg
igor.vaynb...@gmail.com mailto:igor.vaynb...@gmail.com wrote:

 well, if you do not want to *submit* the form then dont use
 ajaxformSUBMITbehavior :)

 with little work you can roll your own behavior that does a simple
 ajax get and appends whatever values you need from formcomponents
 to
 the url. that way the form is not submitted and you have access
to the
 raw values.

 -igor



 On Tue, Jun 2, 2009 at 9:16 AM, dfernandez
 dfernan...@users.sourceforge.net
mailto:dfernan...@users.sourceforge.net wrote:
 
 
  Yes, I know it is tricky, but the fact is I don't think I
would really
 need
  type conversion in this case.
 
  I will try to explain myself. I have the following UI:
 
 |OPERATOR |V|
 
 |INPUT1=aBc| |INPUT2=DeF  |
 
  ...being OPERATOR the DropDownChoice, and both INPUT1 and
INPUT2 two
  TextFields (String TextFields, to be precise). Both INPUT1 and
INPUT2 are
  required (when they are visible, of course).
 
  When I change the value on OPERATOR, the UI will change,
hiding INPUT1
 and
  INPUT2 but showing INPUT3, another TextField which should have
the same
  contents that were on INPUT1 before:
 
 |OPERATOR |V|
 
 |INPUT3=aBc|
 
  The problem is that, when changing OPERATOR, I need to read
the value
 from
  INPUT1 to set it into INPUT3, but if INPUT2 is empty I will
receive a
  validation message telling me that it is required... which it
is, but I
 just
  want Wicket to validate that when I want to *really* submit
the form, and
  not now that I am only changing the operator.
 
  Thanks.
 
  Regards,
  Daniel.
 
 
 
 
 
  igor.vaynberg wrote:
 
  how are you planning on reading the other values? you cannot
access
  the model so you will have to call getinput(), are you also
planning
  on doing type conversion yourself then?
 
  -igor
 
  2009/6/2 Daniel Fernández dfernan...@users.sourceforge.net
mailto:dfernan...@users.sourceforge.net:

  Hello,
 
  I have a form with a DropDownChoice, on which onchange
event I want
 to
  update some form components. But I need to read data from
other fields
 of
  the form for doing so, and so I added an
AjaxFormSubmitBehavior to the
  DropDownChoice.
 
  My intention is to read the data from the drop down and from
the other
  fields, and depending on these data, update some other
components...
 but
  the
  problem is that AjaxFormSubmitBehavior not only sends the
form data

Re: How to turn ModalWindow form into multipart form?

2009-06-30 Thread Vladimir K

Eyal,

did you mean you have patched wicket.jar with modal.js on your own? I'm
going to omit patching wicket.jar.

We'll replace ModalWindow with regular page for a while. I don't understand
why ModalWindow hasn't been implemented with regular wicket ajax engine. It
would be easier to fix something.

Matej,

are you going to fix ModalWindow somehow to be capable of taking
FileUploadField and UploadProgressBar components?

egolan74 wrote:

we overridden modal.js and changed the appearance of the modal window

Eyal Golan
egola...@gmail.com

Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74

P Save a tree. Please don't print this e-mail unless it's really
necessary

On Fri, Jun 26, 2009 at 11:49 AM, Vladimir K koval...@gmail.com wrote:

yes it do has.

near line 1095 of modal.js:

Wicket.Window.getMarkup = function(idWindow, idClassElement, idCaption,
idContent, idTop, idTopLeft, idTopRight, idLeft, idRight, idBottomLeft,
idBottomRight, idBottom, idCaptionText, isFrame) {
var s =
div class=\wicket-modal\ id=\+idWindow+\
style=\top: 10px; left:
10px; width: 100px;\form

style='background-color:transparent;padding:0px;margin:0px;border-width:0px;position:static'+
div id=\+idClassElement+\+

And it seems hacky and buggy.

In our case we would use regular submit for FileUploadField instead of
ajax
if it wasn't hardcoded. Now we need to hack ModalWindow some way. I don't
like iframe approach 'cause it forces user to submit twice at the time
when
regular submit should have worked.

If you don't know this very hardcoded form leads to problem reflecting
request parameters to form components models because in java we have a
stack
of forms and submit request contains just data of this particular form.
As
the result form components of enclosing forms receive empty data and then
... at least unexpected validation problems.
There has been a jira issue already that contains workaround description.
I
have to go right now. I'll find it later.

igor.vaynberg wrote:

modalwindow has a hardcoded form?

On Thu, Jun 25, 2009 at 8:00 AM, Vladimir Kovalyukkoval...@gmail.com
wrote:
How to turn ModalWindow form into multipart form?
The problem is that the markup code for that particular form is
hard-coded
into modal.js script (surprise!, surprise!).

ModalWindow form submission problems han't been fixed yet, I mean rc5

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

--
View this message in context:
http://www.nabble.com/How-to-turn-ModalWindow-form-into-multipart-form--tp24204896p24216939.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

-
Eyal Golan
egola...@gmail.com

Visit: JVDrums
LinkedIn: LinkedIn

--
View this message in context:
http://www.nabble.com/How-to-turn-ModalWindow-form-into-multipart-form--tp24204896p24273227.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to turn ModalWindow form into multipart form?

2009-06-26 Thread Vladimir K

yes it do has.

near line 1095 of modal.js:

And it seems hacky and buggy.

In our case we would use regular submit for FileUploadField instead of ajax
if it wasn't hardcoded. Now we need to hack ModalWindow some way. I don't
like iframe approach 'cause it forces user to submit twice and regular
submit should have worked.

If you don't know this very hardcoded form leads to problem reflecting
request parameters to form components models because in java we have a stack
of forms and submit request contains just data of this particular form. As
the result form components of enclosing forms receive empty data and then
... at least unexpected validation problems.
There has been a jira issue already that contains workaround description. I
have to go right now. I'll find it later.

igor.vaynberg wrote:

modalwindow has a hardcoded form?

ModalWindow form submission problems han't been fixed yet, I mean rc5

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

--
View this message in context:
http://www.nabble.com/How-to-turn-ModalWindow-form-into-multipart-form--tp24204896p24216939.html
Sent from the Wicket - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: how to split application properties file into several properties files

2009-06-22 Thread Vladimir K


As usual it becomes pretty simple if you know how.

in the init method you should add:

getResourceSettings().addStringResourceLoader(new
ClassStringResourceLoader(YourModule.class));

If ClassStringResourceLoader didn't called base class it would be more
efficient implementation.


Vladimir K wrote:
 
 I would like to split the application properties file into several
 properties files.
 I know that I can share resources of base component and page among their
 descendants and at that I can use package propeties files. I just don't
 want
 to go this way because most of messages are organized in different way
 than
 components and pages.
 I wanna just split one file into several distinct files.
 
 What is the best way?
 
 

-- 
View this message in context: 
http://www.nabble.com/how-to-split-application-properties-file-into-several-properties--files-tp24121864p24143617.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Time Field

2009-06-08 Thread Vladimir K


Does anyone know the converter for org.joda.time.Duration?
It is not trivial one taking into account the user's locale.
-- 
View this message in context: 
http://www.nabble.com/Time-Field-tp23930465p23931514.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Tools for Managing a Wicket Project

2009-05-20 Thread Vladimir K


I installed it on MyEclipse I didn't find how to format the text. Does it
capable to format text better than WTP does?


Linkan wrote:
 
 We use Aptana plugin for eclipse as html editor. If you dont install the 
 full suit its free.
 
 //Swanthe
 
 Eduardo Nunes wrote:
 I have just one problem with eclipse, I can't use the HTML formatter,
 that's very sucks. I tried tidy but it didn't work too. What do you
 use guys to format html code?

 On Mon, May 18, 2009 at 2:06 PM, Dane Laverty danelave...@gmail.com
 wrote:
   
 I just wanted to thank Jeremy, Scott, and Linda for recommending
 Effective
 Java. I read through the book this week. It's wonderful -- accessible
 and
 useful. Now I'm in the process of refactoring my project to start
 applying
 the concepts.

 On Fri, May 1, 2009 at 8:53 AM, Carlo Camerino cmcamer...@gmail.com
 wrote:

 
 we used to be bugzilla, mediawiki, continuum statck.we moved to Trac.
 It
 was
 simply amazing with all those plugins.

 Code Review WIth Trac Is Good.
 Review Board is also good software but it doesn't suit our programming
 needs.

 On Fri, May 1, 2009 at 11:38 PM, Matt Welch matt...@welchkin.net
 wrote:

   
 Tools that our team is using (after some trial and error):

 IDE - Eclipse/IDEA
 Source Control - SVN
 Build - Maven
 Local Network Maven Repo - Nexus (after a year trying different ones)
 Build Server  - TeamCity, which absolutely rocks (We actually
 purchased
 
 and
   
 used Bamboo for 9 months. I can't believe it comes from the same
 company
 
 as
   
 JIRA. Bamboo was terrible.)
 Story Mgmt/Defects - Rally (hosted commercial app for agile projects;
 not
 bad, but not fantastic either)
 Code Review - Code Collaborator (again not bad and I'd rather have it
 
 than
   
 nothing at all, but could be better)


 Our QA team has used various testing tools from expensive commercial
 
 tools
   
 like Mercury (now HP) Quality Center to Selenium. They use Rally for
 
 defect
   
 management.

 My highest recommendations are for TeamCity, Nexus, and SVN.

 -Matt


 --
 View this message in context:

 
 http://www.nabble.com/Tools-for-Managing-a-Wicket-Project-tp23299396p23334970.html
   
 Sent from the Wicket - User mailing list archive at Nabble.com.

 



   
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tools-for-Managing-a-Wicket-Project-tp23299396p23647597.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Tools for Managing a Wicket Project

2009-05-19 Thread Vladimir K


Innate markup formatting in WTP is awful. It splits all tags between lines.
I searched the web but didn't find information how to configure WTP. I
returned back to myeclipse.

How could WTP fans be ok with default formatting?


Eduardo Nunes wrote:
 
 it's very strange, because if I hit ctrl+shift+f in some html code
 with WTP, the source code will be completely unwell formatted. I will
 try amateras plugin, thank you
 
 On Mon, May 18, 2009 at 9:15 PM, John Armstrong siber...@siberian.org
 wrote:
 I always have to do a 'Refresh' when changing the HTML. Its quite
 painful..

 I tend to author the bulk of my html in an external editor that is
 more suitable to the purpose and fast ( the eclipse validators are
 painfully slow, particularly in Javascript intensive pages). Then I
 tweak it in Eclipse and hit F5. A Lot.

 John-

 On Mon, May 18, 2009 at 5:03 PM, pete swulius pswul...@gmail.com wrote:
 It appears that using external html editors causes sync issues.
  Apparently
 eclipse doesn't monitor changes to the file system, except to warn you
 that
 it's out of sync.  I would love the know the truth of it as I could very
 well be missing something obvious.  In fact, I would bet that I am,
 considering that eclispe is so cool.

 I am currently using the Amateras plugin:
 http://amateras.sourceforge.jp/cgi-bin/fswiki_en/wiki.cgi?page=EclipseHTMLEditor.
  I have no problems with it, but I use it only for the syntax coloring
 and
 the occasional content assist.

 --pete


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 
 
 -- 
 Eduardo S. Nunes
 http://e-nunes.com.br
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tools-for-Managing-a-Wicket-Project-tp23299396p23611513.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: AW: How to validate unique constraint?

2009-05-19 Thread Vladimir K


Hibernate Validator is useful for bean validations but it has nothing to do
with unique constraint for which you should consult database unless you
cache all the instances.

I would like to provide user with an early warning that the data it fills in
is not unique but I haven't found solution out of the box that uses entity
annotations, especially UniqueContraint.


Dorothée Giernoth wrote:
 
 
 
 I would find this very useful! So a contribution to wicket-stuff would be
 awesome. Thnx.
 
 - dg
  
 -Ursprüngliche Nachricht-
 Von: Clint Popetz [mailto:cl...@42lines.net] 
 Gesendet: Dienstag, 19. Mai 2009 13:49
 An: users@wicket.apache.org
 Betreff: Re: How to validate unique constraint?
 
 It's relatively straightforward to use the hibernate validator api to
 apply JPA constraints:
 
 import org.hibernate.validator.*;
 InvalidValue[] invalidValues = new
 ClassValidator(MyModel.class).getInvalidValues(instanceOfMyModel);
 
 This can also be done per-property; see the javadocs.
 
 I've done this locally; if folks would find it useful I'll contribute
 it to wicketstuff.
 
 -Clint
 
 On Tue, May 19, 2009 at 2:15 AM, Christian Helmbold
 christian.helmb...@yahoo.de wrote:

 How can I validate a unique constraint with Wicket? Because only the
 value of an input field is passed to onValidate(IValidatable
 validatable), there is no chance to check if this value belongs to a
 specific object to update or if it would violate a unique constraint when
 creating a new object. onValidate would need another paremeter for the
 related object.

 I see two possibilities:

 a) Use a form validator and get the related model object from the form.

 b) Pass the related object to the constructor of the Validator. I'm not
 sure, if the validator would be recreated any time the model object
 changes.

 I would prefer a validator tied to the field and not to the form, because
 that would be more intuitive.

 Another idea is to use existing JPA annotations. @Column(unique=true) is
 already there but not used for validation (outside the database). Perhaps
 there is a way to use this annotation. I really like the domain level
 validation of Grails:
 http://grails.org/doc/1.1/guide/7.%20Validation.html

 How would you validate a unique constraint with wicket?

 Thanks in advance
 Christian





 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 
 
 -- 
 Clint Popetz
 http://42lines.net
 Scalable Web Application Development
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/How-to-validate-unique-constraint--tp23610946p23629304.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: SV: Component creation and initialization

2009-05-18 Thread Vladimir K


From my perspective the isVisible() case deserves generification. I know that
there is a task for Wicket 1.5. I mean after that we should write an article
in Wiki.


Wilhelmsen Tor Iver wrote:
 
 Overriding methods like isVisible() is also a form of
 hack to postpone a property value to a later time (basically the
 component stops having a real property called visible since the setter
 modifies a variable that the getter does not care about).
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23592389.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: objectautocomplete on a form with CompoundPropertyModel

2009-05-17 Thread Vladimir K


Does it perform validation on form submit?



nino martinez wael wrote:
 
 hmm true, I think it's because it's ajax and actually get set before
 the form are submited. I agree it would be nice if it acted exactly
 like normal form, but I guess the way it are now allows much more
 flexibility, however it should be possible to do the other aswell.
 
 regards
 
 2009/5/14 Brill Pappin br...@pappin.ca:
 I'd actually rather it worked as expected and simply set the object on
 the
 model property :)
 However, it's usable so I'll live with it.

 - brill

 On 13-May-09, at 3:10 PM, nino martinez wael wrote:

 Yeah or just another way of thinking.. :)

 2009/5/11 Brill Pappin br...@pappin.ca:

 Thanks that worked... although its a bit of a pain in the behind :)

 - Brill Pappin

 On 11-May-09, at 6:55 AM, nino martinez wael wrote:

 You do something like this:

 // compound model
       private final IModelString cityModel = new
 PropertyModelString(
                       searchWrapper, cityId);



       builderCity
                               .updateOnSelectionChange(new
 ObjectAutoCompleteSelectionChangeListenerString() {
                                       public void
 selectionChanged(AjaxRequestTarget target,
                                                       IModelString
 model) {

  cityModel.setObject(model.getObject());

                                       }
                               });
 So it does not update on submit, but instead onSelectionChange of the
 builder..

 2009/5/11 Brill Pappin br...@pappin.ca:

 I'm trying to use ObjectAutoComplete from wicketstuff on a form where
 the
 model is a CompoundPropertyModel.

 The auto compete field doesn't seem to be setting its value on the
 form
 model at all during a submit.

 I've looked at the examples for this component and not a single one
 actually
 includes the onSubmit implementation.
 Is there something special i have to do with this component?

 - Brill Pappin

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/objectautocomplete-on-a-form-with-CompoundPropertyModel-tp23477130p23582308.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization

2009-05-17 Thread Vladimir K


If the question is ressurecting again and again then it is an evidence that
there is something to address and improve. At least Wicket does not have a
method with self-documented name which deffers component creation. As the
result people have to search (using different words) and they don't satisfy
with the result 'cause the topic is still looks open.

This list is quite active and I appreciate the answers of core developers.
Probably Wicket is so good because in addition to the devotion of talented
and capable people to implementation, they do hear what the users say
directly, not indirectly via support team.


Jeremy Thomerson-5 wrote:
 
 I actually had to Google that one.  But, yes, that is the general
 consensus that I've seen.  If you wanted to write a page that showed
 the different ways that you mentioned, that would be fine.  It really
 just depends on if you really need lazy component creation, and then
 how you want to implement it.
 
 --
 Jeremy Thomerson
 http://www.wickettraining.com
 
 
 
 
 On Fri, May 15, 2009 at 11:13 AM, Clint Popetz cl...@42lines.net wrote:
 TMTOWTDI
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23582495.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization


I'm doing just right like you described. Probably I have to pay more
attention to your comment about improper use of models. isVisible method
should rely only on the component model. I some cases it is easier to
delegate some calls to aggregated components. But instead I have to work
with component own model itself.


Jeremy Thomerson-5 wrote:
 
 expose multiple overridable methods that provide the components... i.e.:
 
 // I don't have my IDE open, so some method names may be wrong
 ParentComponent  {
 
   public void onBeforeRender {
 if (!hasBeenRendered()) {
   add(createLeftNavPanel(getModel()));
   add(createContentPanel(getModel()));
   add(createTopHeaderPanel(getModel()));
 }
 
 protected Component createContentPanel(IModel model) {
   // this can be overridden in subclasses
   return MyDefaultTypeOfContentPanel(model);
 }
 }
 
 --
 Jeremy Thomerson
 http://www.wickettraining.com
 
 
 
 
 On Fri, May 15, 2009 at 12:54 AM, Vladimir K koval...@gmail.com wrote:

 Jeremy,

 I can't add another example to mentioned RepeatingView.
 Concerning RepeatingView... Wicket allow me just one point to subclass
 parent component markup within wicket:child/ tag. RepeatingView comes
 in
 handy. It allows me to reserve some places in base component markup and
 put
 something there in subclasssing component markup. I saw examples of that
 in
 some projects when studying Wicket. So I just copy the idea without
 thinking
 about WHEN to call the overridden method that fills in the RepeatingView
 instance. It is my fault :)

 If you add name attribute to wicket:child tag, and multiple
 wicket:extend
 name=... tags I would use it instead of RepeatingView.

 Concerning your post on onBeforeRender ... I didn't say that it is
 related
 to class' constructor. Yes it is related to delayed component creation.
 And
 the reason why I delay creation is to follow mentioned rule. It is not
 related to use of models in my case. I delay creation to allow
 subclassing
 components to replace some default parts of base component. Probably I'm
 doing something wrong. Then suggest me how to do it right. For instance I
 would like to subclass NatigationToolbar in DefaultDataTable. What should
 I
 do?


 Jeremy Thomerson-5 wrote:

 Do you have any examples of where Wicket calls an overridable method
 from the constructor of a Wicket class?  If so, please file it as a
 JIRA - that would be a bug.

 Most java programmers know not to call overridable methods from the
 constructor as a general rule, although there are times when it could
 inadvertantly happen - which is why we need bug reports if you see
 that happening.

 --
 Jeremy Thomerson
 http://www.wickettraining.com




 On Fri, May 15, 2009 at 12:01 AM, Vladimir K koval...@gmail.com wrote:

 Martijn,

 here Java is not safe as a language. Yo're able to invoke overrided
 methods
 on non-completely constructed objects.

 from my perspective it is a regular case in Wicket:

 class SampleComponent extends ... {
    String parameter;

    SampleComponent(String id, String parameter) {
        super(id);
        this.parameter = parameter;
    }

    // method is called from within superconstructor
   �...@override
    void createAdditionalComponents(RepeatingView rv) {
        useSomehow(parameter);
    }
 }

 I know two approaches to work around:
 - onBeforeRender
 - a closure as a constructor formal parameter.

 But the latter does not help with built-in components.

 If Wicket does not help us with adding appropriate method for
 second-step-initialization it should document it in wiki, javadoc and
 books
 dear user, when overriding methods, beware using of yet unassigned
 constructor parameters. Hmm ... sounds stupid :)


 Martijn Dashorst wrote:

 This has been discussed till death previously and we have excluded it
 from our roadmap. We will never have an init() method for components.
 Gossling gave us a Constructor to initialize your Objects.

 Search and read the archives if you want more information on the
 subject.

 Martijn

 On Fri, May 15, 2009 at 12:36 AM, Juan G. Arias juangar...@gmail.com
 wrote:
 It would be very nice to add a new phase for component creation, like
 I
 said, an init() or createContent().
 Is there a JIRA issue for that?
 If yes, I will vote for it and suggest to change the name to
 something
 _not_
 related to the rendre phase.

 Thanks!
 Juan


 On Thu, May 14, 2009 at 3:31 PM, Daniel Stoch
 daniel.st...@gmail.comwrote:

 I think you can use hasBeenRendered() method instead of custom
 boolean
 flag.

 --
 Daniel

 On 2009-05-14, at 20:15, Jeremy Thomerson wrote:

  You could probably do it in onBeforeRender - but you would need to
 keep a boolean flag to check if it's the first render so that you
 don't recreate them on a second render  There was talking of
 adding an onBeforeFirstRender method, but I don't think it's
 happened
 yet - you could look for the method to see if I'm wrong.

 --
 Jeremy Thomerson
 http

Re: Component creation and initialization


Igor,
I didn't mean spreading this approach everywhere :) My intention was to draw
your attention on that onBeforeRender probably is a good place to delay
construction but should be used with extra care and some sort of
simplification (more appropriate method) would be great.

You turned it insideout and it does not make sence anymore :)

Igor, Jeremy, thanks a lot for your suggestions. I have some food for my
brain to think about.


igor.vaynberg wrote:
 
 by your own argument your own code will have to call your
 second-chance init constructor before invoking *any* method on the
 component.
 
 so instead of
 
 boolean visible=getMyComponent().isvisible();
 
 you will have to now do
 
 Component c=getMyComponent();
 if (!c.isinitted()) {c.initI(); }
 boolean visible=c.isvisible();
 
 that init line is now necessary because you *never* know if a
 component has been initialized, so every access to any component
 memeber has to be prefixed by that init check. that will be fun! or we
 can just use constructors since thats what they are designed to do
 (its in the name)
 
 -igor
 
 On Thu, May 14, 2009 at 10:21 PM, Vladimir K koval...@gmail.com wrote:

 it has just come to my mind 

 I'm afraid Wicket can't guarantee that onBeforeRender would be called in
 any
 case. So there could be a case (isVisible() for instance) when
 onBeforeRender is not called yet but overriding method could read
 yet-not-completely-initialized object state.

 Instead of thinking how to work around isVisible() and the other cases
 why
 not just add a second-chance method and invoke it in appropriate places.

 in Component:

 boolean complete = false;
 void ensureCompletelyInitialized() {
    if(!complete){
        finalizeCreation();
        complete = true;
    }
 }

 void internalBeforeRender() {
    ensureCompletelyInitialized();
    ...
 }

 I believe it makes sence.


 Martijn Dashorst wrote:

 This has been discussed till death previously and we have excluded it
 from our roadmap. We will never have an init() method for components.
 Gossling gave us a Constructor to initialize your Objects.

 Search and read the archives if you want more information on the
 subject.

 Martijn

 On Fri, May 15, 2009 at 12:36 AM, Juan G. Arias juangar...@gmail.com
 wrote:
 It would be very nice to add a new phase for component creation, like I
 said, an init() or createContent().
 Is there a JIRA issue for that?
 If yes, I will vote for it and suggest to change the name to something
 _not_
 related to the rendre phase.

 Thanks!
 Juan


 On Thu, May 14, 2009 at 3:31 PM, Daniel Stoch
 daniel.st...@gmail.comwrote:

 I think you can use hasBeenRendered() method instead of custom boolean
 flag.

 --
 Daniel

 On 2009-05-14, at 20:15, Jeremy Thomerson wrote:

  You could probably do it in onBeforeRender - but you would need to
 keep a boolean flag to check if it's the first render so that you
 don't recreate them on a second render  There was talking of
 adding an onBeforeFirstRender method, but I don't think it's happened
 yet - you could look for the method to see if I'm wrong.

 --
 Jeremy Thomerson
 http://www.wickettraining.com



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org






 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 View this message in context:
 http://www.nabble.com/Component-creation-and-initialization-tp23545666p23553618.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23554417.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: May be useful for projects deciding between JSF and Wicket


Where you were two years ago? :)


ptrthomas wrote:
 
 Hi,
 
 I blogged a fairly large collection of links to discussions about the
 issues
 with JSF in general.  What prompted me to put this up is that I yet again
 failed to convince a team at work that Wicket should be chosen over JSF.
 Frustrating.
 
 Hope this proves useful to some, please pass it on to the pointy haired
 bosses, architecture astronauts, powerpoint consultants etc that you know.
 
 DZone link:
 http://dzone.com/links/jsf_sucks_compendium_of_jsf_rantsreviews.html
 
 Thanks,
 
 Peter.
 
 

-- 
View this message in context: 
http://www.nabble.com/May-be-useful-for-projects-deciding-between-JSF-and-Wicket-tp23554009p23554709.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: May be useful for projects deciding between JSF and Wicket


even more ... the title sounds a bit vulgarly.

But the arrangement of such links has a value itself. Especially for people
who hasn't started a project yet.

I would sort the list by date descending. The latest articles has more value
than older.


jeroend-2 wrote:
 
 ...
 The title is subjective at best to start with and to open up with blog
 entries from 5 years ago is not giving it more credibility. ...
 
 regards,
 jeroen.
 

-- 
View this message in context: 
http://www.nabble.com/May-be-useful-for-projects-deciding-between-JSF-and-Wicket-tp23554009p23556062.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization


The horse is pretty alive -
https://issues.apache.org/jira/browse/WICKET-1134. 


Jeremy Thomerson-5 wrote:
 
 With regards to multiple wicket:extend tags - that is also an old,
 dead horse that doesn't need to be beat right now.  The user list has
 a lot of discussion on it.  The simplest way to allow a child to
 contribute multiple components to a page is the same as you would do
 in normal java (which does not allow multiple inheritance) - expose
 multiple overridable methods that provide the components... i.e.:
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23557008.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization

2009-05-14 Thread Vladimir K


Martijn,

here Java is not safe as a language. Yo're able to invoke overrided methods
on non-completely constructed objects.

from my perspective it is a regular case in Wicket:

class SampleComponent extends ... {
String parameter;

SampleComponent(String id, String parameter) {
super(id);
this.parameter = parameter;
}

// method is called from within superconstructor
@Override
void createAdditionalComponents(RepeatingView rv) {
useSomehow(parameter);
}
}

I know two approaches to work around:
- onBeforeRender 
- a closure as a constructor formal parameter.

But the latter does not help with built-in components.

If Wicket does not help us with adding appropriate method for
second-step-initialization it should document it in wiki, javadoc and books
dear user, when overriding methods, beware using of yet unassigned
constructor parameters. Hmm ... sounds stupid :)


Martijn Dashorst wrote:
 
 This has been discussed till death previously and we have excluded it
 from our roadmap. We will never have an init() method for components.
 Gossling gave us a Constructor to initialize your Objects.
 
 Search and read the archives if you want more information on the subject.
 
 Martijn
 
 On Fri, May 15, 2009 at 12:36 AM, Juan G. Arias juangar...@gmail.com
 wrote:
 It would be very nice to add a new phase for component creation, like I
 said, an init() or createContent().
 Is there a JIRA issue for that?
 If yes, I will vote for it and suggest to change the name to something
 _not_
 related to the rendre phase.

 Thanks!
 Juan


 On Thu, May 14, 2009 at 3:31 PM, Daniel Stoch
 daniel.st...@gmail.comwrote:

 I think you can use hasBeenRendered() method instead of custom boolean
 flag.

 --
 Daniel

 On 2009-05-14, at 20:15, Jeremy Thomerson wrote:

  You could probably do it in onBeforeRender - but you would need to
 keep a boolean flag to check if it's the first render so that you
 don't recreate them on a second render  There was talking of
 adding an onBeforeFirstRender method, but I don't think it's happened
 yet - you could look for the method to see if I'm wrong.

 --
 Jeremy Thomerson
 http://www.wickettraining.com



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 
 
 
 -- 
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23553458.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization

2009-05-14 Thread Vladimir K


it has just come to my mind 

I'm afraid Wicket can't guarantee that onBeforeRender would be called in any
case. So there could be a case (isVisible() for instance) when
onBeforeRender is not called yet but overriding method could read
yet-not-completely-initialized object state.

Instead of thinking how to work around isVisible() and the other cases why
not just add a second-chance method and invoke it in appropriate places.

in Component:

boolean complete = false;
void ensureCompletelyInitialized() {
if(!complete){
finalizeCreation();
complete = true;
}
}

void internalBeforeRender() {
ensureCompletelyInitialized();
...
}

I believe it makes sence.


Martijn Dashorst wrote:
 
 This has been discussed till death previously and we have excluded it
 from our roadmap. We will never have an init() method for components.
 Gossling gave us a Constructor to initialize your Objects.
 
 Search and read the archives if you want more information on the subject.
 
 Martijn
 
 On Fri, May 15, 2009 at 12:36 AM, Juan G. Arias juangar...@gmail.com
 wrote:
 It would be very nice to add a new phase for component creation, like I
 said, an init() or createContent().
 Is there a JIRA issue for that?
 If yes, I will vote for it and suggest to change the name to something
 _not_
 related to the rendre phase.

 Thanks!
 Juan


 On Thu, May 14, 2009 at 3:31 PM, Daniel Stoch
 daniel.st...@gmail.comwrote:

 I think you can use hasBeenRendered() method instead of custom boolean
 flag.

 --
 Daniel

 On 2009-05-14, at 20:15, Jeremy Thomerson wrote:

  You could probably do it in onBeforeRender - but you would need to
 keep a boolean flag to check if it's the first render so that you
 don't recreate them on a second render  There was talking of
 adding an onBeforeFirstRender method, but I don't think it's happened
 yet - you could look for the method to see if I'm wrong.

 --
 Jeremy Thomerson
 http://www.wickettraining.com



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 
 
 
 -- 
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Component-creation-and-initialization-tp23545666p23553618.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Component creation and initialization

2009-05-14 Thread Vladimir K


Jeremy,

I can't add another example to mentioned RepeatingView.
Concerning RepeatingView... Wicket allow me just one point to subclass
parent component markup within wicket:child/ tag. RepeatingView comes in
handy. It allows me to reserve some places in base component markup and put
something there in subclasssing component markup. I saw examples of that in
some projects when studying Wicket. So I just copy the idea without thinking
about WHEN to call the overridden method that fills in the RepeatingView
instance. It is my fault :)

If you add name attribute to wicket:child tag, and multiple wicket:extend
name=... tags I would use it instead of RepeatingView.

Concerning your post on onBeforeRender ... I didn't say that it is related
to class' constructor. Yes it is related to delayed component creation. And
the reason why I delay creation is to follow mentioned rule. It is not
related to use of models in my case. I delay creation to allow subclassing
components to replace some default parts of base component. Probably I'm
doing something wrong. Then suggest me how to do it right. For instance I
would like to subclass NatigationToolbar in DefaultDataTable. What should I
do?


Jeremy Thomerson-5 wrote:
 
 Do you have any examples of where Wicket calls an overridable method
 from the constructor of a Wicket class?  If so, please file it as a
 JIRA - that would be a bug.
 
 Most java programmers know not to call overridable methods from the
 constructor as a general rule, although there are times when it could
 inadvertantly happen - which is why we need bug reports if you see
 that happening.
 
 --
 Jeremy Thomerson
 http://www.wickettraining.com
 
 
 
 
 On Fri, May 15, 2009 at 12:01 AM, Vladimir K koval...@gmail.com wrote:

 Martijn,

 here Java is not safe as a language. Yo're able to invoke overrided
 methods
 on non-completely constructed objects.

 from my perspective it is a regular case in Wicket:

 class SampleComponent extends ... {
    String parameter;

    SampleComponent(String id, String parameter) {
        super(id);
        this.parameter = parameter;
    }

    // method is called from within superconstructor
   �...@override
    void createAdditionalComponents(RepeatingView rv) {
        useSomehow(parameter);
    }
 }

 I know two approaches to work around:
 - onBeforeRender
 - a closure as a constructor formal parameter.

 But the latter does not help with built-in components.

 If Wicket does not help us with adding appropriate method for
 second-step-initialization it should document it in wiki, javadoc and
 books
 dear user, when overriding methods, beware using of yet unassigned
 constructor parameters. Hmm ... sounds stupid :)


 Martijn Dashorst wrote:

 This has been discussed till death previously and we have excluded it
 from our roadmap. We will never have an init() method for components.
 Gossling gave us a Constructor to initialize your Objects.

 Search and read the archives if you want more information on the
 subject.

 Martijn

 On Fri, May 15, 2009 at 12:36 AM, Juan G. Arias juangar...@gmail.com
 wrote:
 It would be very nice to add a new phase for component creation, like I
 said, an init() or createContent().
 Is there a JIRA issue for that?
 If yes, I will vote for it and suggest to change the name to something
 _not_
 related to the rendre phase.

 Thanks!
 Juan


 On Thu, May 14, 2009 at 3:31 PM, Daniel Stoch
 daniel.st...@gmail.comwrote:

 I think you can use hasBeenRendered() method instead of custom boolean
 flag.

 --
 Daniel

 On 2009-05-14, at 20:15, Jeremy Thomerson wrote:

  You could probably do it in onBeforeRender - but you would need to
 keep a boolean flag to check if it's the first render so that you
 don't recreate them on a second render  There was talking of
 adding an onBeforeFirstRender method, but I don't think it's happened
 yet - you could look for the method to see if I'm wrong.

 --
 Jeremy Thomerson
 http://www.wickettraining.com



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org






 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com
 Apache Wicket 1.3.5 is released
 Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 View this message in context:
 http://www.nabble.com/Component-creation-and-initialization-tp23545666p23553458.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org

Re: AW: How to avoid code duplication on forms?

2009-05-11 Thread Vladimir K


Factory pattern is about Dependency Inversion Principle. You may use this
pattern to avoid dependency to concrete classes.

So the best way in your case is having Factory that constructs concrete
editors via subclassing. They work best together :)


Christian Helmbold-2 wrote:
 
 
 I think the difference between sub classing and static factory methods is
 a matter of taste in this case.
 
 If I have many fields, I'd need many classes for them. So I'd group them
 in a sub package. In the case of factory methods I'd group the methods to
 create fields in a class instead of a package.
 
 Subclass:
 
 1class UserEmailField extends TextField {
 2  public UserEmailField(String id, IModel model) {
 3super(id, model);
 4setRequired(true);
 5add(EmailAddressValidator.getInstance())
 6add(UniqueValidator.unique(SystemUser.class, email));
 7  }
 8}
 
 Factory method:
 
 1public static TextField emailTextField(String id){
 2return (TextField) new TextField(id)
 3.setRequired(true)
 4.add(EmailAddressValidator.getInstance())
 5.add(UniqueValidator.unique(SystemUser.class,
 email));
 6}
 
 Your answer shows me, that there is no dramatically simpler way to do
 this. If you ignore the two lines for factory class declaration factory
 methods are even a bit shorter. Or is there an advantage of sub classing
 that I have missed?
 
 Regards,
 Christian
 
 
 
 - Ursprüngliche Mail 
 Von: Igor Vaynberg igor.vaynb...@gmail.com
 An: users@wicket.apache.org
 Gesendet: Freitag, den 8. Mai 2009, 09:08:34 Uhr
 Betreff: Re: How to avoid code duplication on forms?
 
 much simpler
 
 class UserEmailField extends TextField {
   public UserEmailField(String id, IModel model) {
 super(id, model);
 add(EmailAddressValidator.getInstance())
 add(UniqueValidator.unique(SystemUser.class, email));
}
 }
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/How-to-avoid-code-duplication-on-forms--tp23440920p23496309.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Editable select

2009-05-07 Thread Vladimir K


Thanks. I'll try AutoCompleteSettings.


James Carman-3 wrote:
 
 Perhaps autocomplete?
 
 On Thu, May 7, 2009 at 5:55 AM, Vladimir Kovalyuk koval...@gmail.com
 wrote:
 Does anybody know any editable select wicket-component that supports
 attaching 'onchange' AjaxFormComponentUpdatingBehavior?

 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Editable-select-tp23423534p23426031.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Add a ui lock page over the page while waiting for response

2009-05-07 Thread Vladimir K


The following works for me pretty well:

http://cwiki.apache.org/WICKET/generic-busy-indicator-for-both-ajax-and-non-ajax-submits.html
http://cwiki.apache.org/WICKET/generic-busy-indicator-for-both-ajax-and-non-ajax-submits.html
 


Matthias Keller wrote:
 
 Hi
 
 Thanks for the input. I now used wicketstuff-jquery and wrote a custom 
 behaviour which adds the code to my form.
 For later reference:
 public class UIBlockerBehaviour extends JQueryBehavior {
 private static final ResourceReference BLOCKUI_JS =
 new CompressedResourceReference(UIBlockerBehaviour.class, 
 jquery.blockUI.js);
 
 ...
 

-- 
View this message in context: 
http://www.nabble.com/Add-a-ui-lock-page-over-the-page-while-waiting-for-response-tp23407195p23427935.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Offline Applications

2009-05-03 Thread Vladimir K


Agree, I mentioned already it depends on the nature of the application.
Anyway unless the bank pays you on time-and-material basis it is risky to
implement two modes application (for bank and for dev team).

Consider Java Web Start vs Gears.


Carlo Camerino wrote:
 
 hmm, you have a point here.however, every requirement is different.
 
 I know that it may sound weird, but still I believe that it depends on the
 nature of the application.
 There are lots of types of applications that banks use.
 Some I know would have to always have a central server managing it.
 
 There are different types of Technical Architectures that we cater for in
 our applications.
 There are some applicationms that always require online mode regardless
 adn
 there are applications that the user just
 needs to be able to view customer information ,etc
 
 
 actually it's hard to decide here.
 on the downside, I heard that GWT consumes a lot of resources on the
 client
 side, it's also a consideration.
 
 Failsafe servers are of course an option but again, the network is still a
 factor here.
 For example a very slow connection to the central server makes my
 productivity a lot less.
 Some places suffer from low bandwidth, unreliable networks, etc...
 
 I saw the value of distributed or offline applications that uses
 synchronization.
 It will be harder for the developers of course sicne they have to cater to
 two modes.
 On Sun, May 3, 2009 at 1:55 PM, Vladimir K koval...@gmail.com wrote:
 

 I would install failsafe cluster rather satisfying every client request
 about
 offline workability. You may end up implementing all the front-end and
 middle-end features in offline mode :)

 I believe offline mode should be used with care. The email applications
 are
 by nature offline. If you are certain that what the user does is offline
 by
 nature - implement it. If you have concerns that it should be involved
 into
 transaction (I mean a bit wider meaning than DB transaction) - implement
 it
 online and think about fail-safe servers.

 Concerning front-end and middle-end, AFAIK, every unit of work is a
 transaction which is done with multi-level authorization, including
 business
 authorization. You either implement all the authorization offline
 (insecure
 at all, and impossible in some cases) or defer authorization untill
 online
 mode (non-transactional). If a request of some client was satisfied (in
 offline mode) and then hasn't passed online authorization (for instance
 it
 violates some limits which can be thruly calculated on the server side
 only), you will have to call the client and tell him your appologises (or
 not directly you, then the bank. but the bank will then call you and tell
 you something awesome).

 Or just tell me the name of the bank. I will never become its client :)


 Carlo Camerino wrote:
 
  it's not for the public to use. but rather for people within the banks.
  internal applications. sometimes central connection is not available.
 
  On Fri, May 1, 2009 at 9:37 PM, James Carman
  jcar...@carmanconsulting.comwrote:
 
  Are you sure a banking application would be the right place for a
  gears-based implementation?  Wouldn't it be kinda important to make
  sure the main server knows where everything is, when money is
  concerned?
 
  On Fri, May 1, 2009 at 4:04 AM, Carlo Camerino cmcamer...@gmail.com
  wrote:
   Hi,
  
   Is there any project which has Wicket And Google Gears Integration?
   Wicket has really done a lot of us in speeding up development time.
  Coming
   from a struts we saw the power of Wicket in terms its reusability
 and
  i've
   noticed that
   wicket already did most of the tasks that we would have to manually
 do
  using
   struts application, like session timeouts, redirects, etc
  
One of our main concerns however are that clients
   are asking for our applications to be available even if the network
 is
  down
   or if the central server is down..
   Currently we implemented our applications in a distributed fashion
  wherein
   every branch ( Remote Location)  has its own server.
   However, this has implications of cost and administration issues.
   However, if offline mode is enabled we can just begin syncing right.
  
   I think that Wicket WIth Google Gears Application will make it even
  better .
  
  
   I think this is really a plus when it comes to marketing it to
  customers.
   Most of the applications that we create our banking applications and
  any
   downtime is costing our clients.
  
   Hopefully we can also do this to offload the central servers and to
 put
   processing into client machines.
  
   One large problem I see though is that most code wil have to be
 moved
  to
  the
   Browser Layer.
   I'm thinking of how to create a wicket application which is mostly
 run
  by
   java classes work on the client side.
   Looks as if there will be a lot of code changes...
   I'm not really sure if it would be a totally different programming
  model

Re: Wicket Offline Applications

2009-05-02 Thread Vladimir K


I would install failsafe cluster rather satisfying every client request about
offline workability. You may end up implementing all the front-end and
middle-end features in offline mode :)

I believe offline mode should be used with care. The email applications are
by nature offline. If you are certain that what the user does is offline by
nature - implement it. If you have concerns that it should be involved into
transaction (I mean a bit wider meaning than DB transaction) - implement it
online and think about fail-safe servers.

Concerning front-end and middle-end, AFAIK, every unit of work is a
transaction which is done with multi-level authorization, including business
authorization. You either implement all the authorization offline (insecure
at all, and impossible in some cases) or defer authorization untill online
mode (non-transactional). If a request of some client was satisfied (in
offline mode) and then hasn't passed online authorization (for instance it
violates some limits which can be thruly calculated on the server side
only), you will have to call the client and tell him your appologises (or
not directly you, then the bank. but the bank will then call you and tell
you something awesome).

Or just tell me the name of the bank. I will never become its client :)


Carlo Camerino wrote:
 
 it's not for the public to use. but rather for people within the banks.
 internal applications. sometimes central connection is not available.
 
 On Fri, May 1, 2009 at 9:37 PM, James Carman
 jcar...@carmanconsulting.comwrote:
 
 Are you sure a banking application would be the right place for a
 gears-based implementation?  Wouldn't it be kinda important to make
 sure the main server knows where everything is, when money is
 concerned?

 On Fri, May 1, 2009 at 4:04 AM, Carlo Camerino cmcamer...@gmail.com
 wrote:
  Hi,
 
  Is there any project which has Wicket And Google Gears Integration?
  Wicket has really done a lot of us in speeding up development time.
 Coming
  from a struts we saw the power of Wicket in terms its reusability and
 i've
  noticed that
  wicket already did most of the tasks that we would have to manually do
 using
  struts application, like session timeouts, redirects, etc
 
   One of our main concerns however are that clients
  are asking for our applications to be available even if the network is
 down
  or if the central server is down..
  Currently we implemented our applications in a distributed fashion
 wherein
  every branch ( Remote Location)  has its own server.
  However, this has implications of cost and administration issues.
  However, if offline mode is enabled we can just begin syncing right.
 
  I think that Wicket WIth Google Gears Application will make it even
 better .
 
 
  I think this is really a plus when it comes to marketing it to
 customers.
  Most of the applications that we create our banking applications and
 any
  downtime is costing our clients.
 
  Hopefully we can also do this to offload the central servers and to put
  processing into client machines.
 
  One large problem I see though is that most code wil have to be moved
 to
 the
  Browser Layer.
  I'm thinking of how to create a wicket application which is mostly run
 by
  java classes work on the client side.
  Looks as if there will be a lot of code changes...
  I'm not really sure if it would be a totally different programming
 model.
 
  Anyone out there tried to integrate Gears And Wicket
 
  Carlo
 

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Offline-Applications-tp23329675p23352910.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: ModalWindows...

2009-04-30 Thread Vladimir K


https://issues.apache.org/jira/browse/WICKET-2249

vote for it


nino martinez wael wrote:
 
 Very true
 +1 for adding a overridable method
 
 2009/4/30 Vladimir K koval...@gmail.com:

 put the following into the head section of your page:

                script language=javascript type=text/javascript
                        jQuery(document).ready(function(){
                                if (typeof Wicket != 'undefined' 
 Wicket.Window)
                                        Wicket.Window.unloadConfirmation =
 false;
                        });
                /script

 I don't like this approach because it violateds incapsulation. It should
 has
 been implemented as overridable method of ModalWindow.


 Vidhya Kailash wrote:

 1. How do I disable the popup that comes on click inside the modal
 window:
 Are you sure you want to navigate away from this page?


 --
 View this message in context:
 http://www.nabble.com/ModalWindows...-tp23300556p23309702.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/ModalWindows...-tp23300556p23311160.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: confirm leave page when a page contains unsaved data

2009-04-30 Thread Vladimir K


I think the approach similar to one used in CheckGroup would work. I just
wondered if it has already been implemented.


Newgro wrote:
 
 Vladimir Kovalyuk schrieb:
 Do wicket has a generic approach to handling the following scenario?

 1. user opens a page with details of some entity, for instance a user.
 2. user starts to type in fields
 3. user clicks some link, then she is informed that the form contains
 unsaved data and asked to press discard and proceed, save and proceed
 or
 cancel.

   
 Nope. How should wicket decide on that? It's business logic. And so you 
 have to present the dialog
 (modal window?) yourself. Alternatively you could an javascript alert.
 
 Cheers
 Per
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/confirm-leave-page-when-a-page-contains-unsaved-data-tp23312432p23313202.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Possible to retrieve previous page from PageMap


The requirements are inconsistent. It is impossible to bookmark the link
today and come to the page tomorrow. Unless it shoud be considered as a long
running transaction, in which case only page parameter works.


pixologe wrote:
 
 In our current case we would need to display a specific info only if the
 user came from a specific page.
 We are using BookmarkablePageLink with mounts and are keen on keeping our
 URLs as clean as possible, thus we would like to avoid passing a page
 classname around with every request or similar. 
 

-- 
View this message in context: 
http://www.nabble.com/Possible-to-retrieve-previous-page-from-PageMap-tp20861106p23291877.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: AW: AW: Tabbed Panel with bookmarkable links


But it is also a bug in the TabbedPanel which should work well without tabs.


Christian Helmbold-2 wrote:
 
 
  What if you use two different tabbed panels on the same page?
 
 
 Good point! It doesn't work with two panels on the same page! I don't
 know why 
 and how to fix it.
 
 It was a mistake in my test code, that lead to this error. I accidentally
 added the tabs of my second tabbed panel to the first one. Multiple
 BookmarkableTabbedPanels work fine now.
 
 Regards
 Christian
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tabbed-Panel-with-bookmarkable-links-tp22418170p23295407.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: ModalWindows...


put the following into the head section of your page:

script language=javascript type=text/javascript
jQuery(document).ready(function(){
if (typeof Wicket != 'undefined'  
Wicket.Window)
Wicket.Window.unloadConfirmation = 
false;
});
/script

I don't like this approach because it violateds incapsulation. It should has
been implemented as overridable method of ModalWindow.


Vidhya Kailash wrote:
 
 1. How do I disable the popup that comes on click inside the modal window:
 Are you sure you want to navigate away from this page?
 

-- 
View this message in context: 
http://www.nabble.com/ModalWindows...-tp23300556p23309702.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: GWT-like