You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by saki <sa...@chare.eu> on 2008/01/14 10:18:58 UTC
Change of panel
Hello,
would it be possible to make some little changes in component markup lookup,
which would allow to control if the markup is inherited or is in the html
file ? Currently if I want to specify for formComponent own lookup, I have
to extend Panel, which is little bit painful. I've created example of such
functionality -
http://www.chare.eu/test/panel.zip
The main goal is to be able to produce lot of forms using same components
without
the need to write html for form (only once for component). The embedding of
such components in panel is little bit painful, so I tried a bit different
approach.
I do not want to start any discussion about how wicket works (in a style
wicket x echo), I'm very happy with wicket and thanks to all developers... I
only think, that the Panel can be improved or added some new functionality
to wicket, which would enable developers to created 'panel like components'
without need to extend Panel (eg. implement some interface (like
IHeaderContributor) or override some method, ...) so the reuse of existing
components in repeaters would be easier.
But may be I overlooked something, so please let me know, if there is some
easier way and more elegant way than I the one selected.
I do appreciate any comments (even the bad ones) and suggestions
Petr Sakar
--
View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14797276.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Wicket Stuff commit access
Posted by Eelco Hillenius <ee...@gmail.com>.
On Jan 17, 2008 2:36 PM, saki <sa...@chare.eu> wrote:
>
> In that case it is sakiss (login name).
> Petr
You're in. Have fun!
Eelco
Re: Wicket Stuff commit access
Posted by saki <sa...@chare.eu>.
In that case it is sakiss (login name).
Petr
Eelco Hillenius wrote:
>
>> Wow, that was quick ...
>> My user id is 1289197. May be I will have same questions regarding the
>> initial import - just to be sure I'll not do something wrong ...
>> Petr
>
> I think we need your logic id (mine is 'eelco12' for instance).
>
> Eelco
>
>
--
View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14936041.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Wicket Stuff commit access
Posted by Eelco Hillenius <ee...@gmail.com>.
> Wow, that was quick ...
> My user id is 1289197. May be I will have same questions regarding the
> initial import - just to be sure I'll not do something wrong ...
> Petr
I think we need your logic id (mine is 'eelco12' for instance).
Eelco
Re: Wicket Stuff commit access
Posted by saki <sa...@chare.eu>.
Wow, that was quick ...
My user id is 1289197. May be I will have same questions regarding the
initial import - just to be sure I'll not do something wrong ...
Petr
Gerolf Seitz wrote:
>
> give us your sourceforge.net user id, then we can give you commit rights
> (though i don't have the karma for that, iirc)
>
> gerolf
>
On Jan 17, 2008 10:47 PM, saki <sa...@chare.eu> wrote:
--
View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14935882.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Wicket Stuff commit access
Posted by Gerolf Seitz <ge...@gmail.com>.
give us your sourceforge.net user id, then we can give you commit rights
(though i don't have the karma for that, iirc)
gerolf
On Jan 17, 2008 10:47 PM, saki <sa...@chare.eu> wrote:
>
> Hello,
> can I get access to wicket stuff to be able to create a project (or can
> the
> admins setup the project and give me access to the project) please ?
>
> I would like to create project for Panel component which would allow me to
> use components in following way:
>
> 1. create subclass of existing component (eg. TextField) and corresponding
> html file.
> 2. modify my class (override some method(s) or better by implement some
> interface (hopefully empty))
> 3. add such component to the panel only in code (panel does not have any
> html)
>
> I already have partial implementation and working example.
>
> Thank you
> Petr Sakar
>
>
> Could'nt you encourage Petr to create a wicket stuff for it :)
>
>
> --
> View this message in context:
> http://www.nabble.com/Change-of-panel-tp14797276p14934883.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Wicket Stuff commit access
Posted by saki <sa...@chare.eu>.
Hello,
can I get access to wicket stuff to be able to create a project (or can the
admins setup the project and give me access to the project) please ?
I would like to create project for Panel component which would allow me to
use components in following way:
1. create subclass of existing component (eg. TextField) and corresponding
html file.
2. modify my class (override some method(s) or better by implement some
interface (hopefully empty))
3. add such component to the panel only in code (panel does not have any
html)
I already have partial implementation and working example.
Thank you
Petr Sakar
Could'nt you encourage Petr to create a wicket stuff for it :)
--
View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14934883.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Change of panel
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Could'nt you encourage Petr to create a wicket stuff for it :)
hint hint...
Eelco Hillenius wrote:
>> Hello Eelco,
>> thank you for your response. I've checked the FormComponentPanel, but if I
>> want to use it in forms I would have to reimplement all the functionality of
>> such components (eg. Button, CheckBox, TextField, ...), which would be
>> definitely reinventing the wheel. I'm looking for how to do the following:
>>
>> 1. create subclass of existing component (eg. TextField) and corresponding
>> html file.
>> 2. modify my class (override some method(s) or better by implement some
>> interface (hopefully empty))
>>
>> As a result I would be able to use it in repeaters.
>>
>> I did it in my example, but I think and hope it could be done in some better
>> way.
>>
>
> Yeah, that's just not possible at this time. You'll have to duplicate
> the components by wrapping them in these panels. This is an area where
> we'd love to have some more power in the language (mixins for
> instance). Maybe we'll find a better way to do it in Wicket sometime,
> but that won't be anytime soon I'm afraid.
>
> Eelco
>
>
>
--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
Re: Change of panel
Posted by Eelco Hillenius <ee...@gmail.com>.
> Hello Eelco,
> thank you for your response. I've checked the FormComponentPanel, but if I
> want to use it in forms I would have to reimplement all the functionality of
> such components (eg. Button, CheckBox, TextField, ...), which would be
> definitely reinventing the wheel. I'm looking for how to do the following:
>
> 1. create subclass of existing component (eg. TextField) and corresponding
> html file.
> 2. modify my class (override some method(s) or better by implement some
> interface (hopefully empty))
>
> As a result I would be able to use it in repeaters.
>
> I did it in my example, but I think and hope it could be done in some better
> way.
Yeah, that's just not possible at this time. You'll have to duplicate
the components by wrapping them in these panels. This is an area where
we'd love to have some more power in the language (mixins for
instance). Maybe we'll find a better way to do it in Wicket sometime,
but that won't be anytime soon I'm afraid.
Eelco
Re: Change of panel
Posted by saki <sa...@chare.eu>.
Hello Eelco,
thank you for your response. I've checked the FormComponentPanel, but if I
want to use it in forms I would have to reimplement all the functionality of
such components (eg. Button, CheckBox, TextField, ...), which would be
definitely reinventing the wheel. I'm looking for how to do the following:
1. create subclass of existing component (eg. TextField) and corresponding
html file.
2. modify my class (override some method(s) or better by implement some
interface (hopefully empty))
As a result I would be able to use it in repeaters.
I did it in my example, but I think and hope it could be done in some better
way.
Petr Sakar
Eelco Hillenius wrote:
>
>> Hello,
>> would it be possible to make some little changes in component markup
>> lookup,
>> which would allow to control if the markup is inherited or is in the html
>> file ? Currently if I want to specify for formComponent own lookup, I
>> have
>> to extend Panel, which is little bit painful. I've created example of
>> such
>> functionality -
>> http://www.chare.eu/test/panel.zip
>> The main goal is to be able to produce lot of forms using same components
>> without
>> the need to write html for form (only once for component). The embedding
>> of
>> such components in panel is little bit painful, so I tried a bit
>> different
>> approach.
>
> Check out FormComponentPanel.
>
> Eelco
>
>
--
View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14837979.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Change of panel
Posted by Eelco Hillenius <ee...@gmail.com>.
> Hello,
> would it be possible to make some little changes in component markup lookup,
> which would allow to control if the markup is inherited or is in the html
> file ? Currently if I want to specify for formComponent own lookup, I have
> to extend Panel, which is little bit painful. I've created example of such
> functionality -
> http://www.chare.eu/test/panel.zip
> The main goal is to be able to produce lot of forms using same components
> without
> the need to write html for form (only once for component). The embedding of
> such components in panel is little bit painful, so I tried a bit different
> approach.
Check out FormComponentPanel.
Eelco