RE: View and edit panel

2012-11-28 Thread Michal Wegrzyn 
Hi Thomas,

Bean edit panel is useful in this sort of scenarios.

http://londonwicket.googlecode.com/files/LondonWicket-BeanEditor.pdf

It is quite old, maybe there is a newer/better option.

Best regards,
Michal Wegrzyn

 -Original Message-
 From: Thomas Götz [mailto:t...@decoded.de]
 Sent: Wednesday, November 28, 2012 10:07
 To: users@wicket.apache.org
 Subject: View and edit panel
 
 Hi there,
 
 I'm currently implementing a panel that is used for viewing and editing
 of some entity. I wonder if there is an elegant solution for this.
 
 The situation:
 all my view/edit panels have a common abstract parent class (Panel),
 providing some general markup, i.e. I'm using wicket:extend in my
 concrete Panel implementation. Not every component is editable, only
 some. Currently I have a solution where I'm using a flag (isEditMode)
 and some if/else constructs to create either a label or e.g. a
 TextField. I keep the markup for the FormComponents as Fragments or
 separate Panels. Any more sophisticated ideas on how to implement this?
 ;-)
 
 Cheers,
-Tom
 
 
 
 -
 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

Re: View and edit panel

2012-11-28 Thread Nick Pratt 
You can set the Panel non-editable, and all those Form components will
become non-editable.


On Wed, Nov 28, 2012 at 4:06 AM, Thomas Götz t...@decoded.de wrote:

 Hi there,

 I'm currently implementing a panel that is used for viewing and editing of
 some entity. I wonder if there is an elegant solution for this.

 The situation:
 all my view/edit panels have a common abstract parent class (Panel),
 providing some general markup, i.e. I'm using wicket:extend in my
 concrete Panel implementation. Not every component is editable, only some.
 Currently I have a solution where I'm using a flag (isEditMode) and some
 if/else constructs to create either a label or e.g. a TextField. I keep the
 markup for the FormComponents as Fragments or separate Panels. Any more
 sophisticated ideas on how to implement this? ;-)

 Cheers,
-Tom



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