RE: Good example for FormComponentPanel?
I am pretty sure that a tabbed panel can't be part of one form. If it can, that
would be lovely. But I was under the impression that you can't add panels to a
form.
Could someone clarify this for me? BTW, one of the things I tried was to make
each panel into a FormComponentPanel and then add it to the tabbed panel. Well,
turns out that FormComponentPanel is NOT a *panel* after all (bad naming IMHO).
At this point I'm thinking of simply building it as a straight form and then
turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form, please let me know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle [EMAIL PROTECTED] wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is out of my
hand. It's got to have tabs. Of course it is possible to do the tabbing by
CSS styling, but I wanted to see if FormComponentPanel is a way to go since
the complexity of managing the tabbed panel would then be shifted to the
CSS/JS side.
I just looked at the Multiply example and it seems to make sense. Again, if
anyone wants to share any tips/input regarding this (or how to avoid traps),
please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle [EMAIL PROTECTED] wrote:
I need to build a TabbedPanel with three tabs which are part of one form
- the selected tab will contain form components which need to be
submitted by that one form. It seems FormComponentPanel is the way to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form components
into a single object, like if you had year/month/day DropDownChoices in a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle [EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form. If it can,
that would be lovely. But I was under the impression that you can't add
panels to a form.
Could someone clarify this for me? BTW, one of the things I tried was to
make each panel into a FormComponentPanel and then add it to the tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel* after all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight form and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form, please let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle [EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is out of
my hand. It's got to have tabs. Of course it is possible to do the tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a way to go
since the complexity of managing the tabbed panel would then be shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make sense.
Again, if anyone wants to share any tips/input regarding this (or how to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle [EMAIL PROTECTED]
wrote:
I need to build a TabbedPanel with three tabs which are part of one
form
- the selected tab will contain form components which need to be
submitted by that one form. It seems FormComponentPanel is the way
to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
Re: Good example for FormComponentPanel?
DateTimeField extends FormComponentPanel On Fri, Apr 11, 2008 at 7:37 PM, Michael Mehrle [EMAIL PROTECTED] wrote: I need to build a TabbedPanel with three tabs which are part of one form - the selected tab will contain form components which need to be submitted by that one form. It seems FormComponentPanel is the way to go: are there any good examples of this? Also, would this be the recommended approach? Thanks, Michael -- Ryan Gravener http://ryangravener.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle [EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day DropDownChoices in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form. If it
can,
that would be lovely. But I was under the impression that you can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I tried was
to
make each panel into a FormComponentPanel and then add it to the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel* after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form, please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is out
of
my hand. It's got to have tabs. Of course it is possible to do the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a way to
go
since the complexity of managing the tabbed panel would then be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make sense.
Again, if anyone wants to share any tips/input regarding this (or how
to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I need to build a TabbedPanel with three tabs which are part of
one
form
- the selected tab will contain form components which need to be
submitted by that one form. It seems FormComponentPanel is the
way
to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Good example for FormComponentPanel?
You mean the links that select/toggle each panel? Not sure what you mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form. If
it
can,
that would be lovely. But I was under the impression that you can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I tried
was
to
make each panel into a FormComponentPanel and then add it to the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form, please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is
out
of
my hand. It's got to have tabs. Of course it is possible to do the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a way
to
go
since the complexity of managing the tabbed panel would then be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make
sense.
Again, if anyone wants to share any tips/input regarding this (or
how
to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I need to build a TabbedPanel with three tabs which are part
of
one
form
- the selected tab will contain form components which need to
be
submitted by that one form. It seems FormComponentPanel is
the
way
to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Good example for FormComponentPanel?
yes, those links. by default they are regular a href links, so they
wont submit the values of components that are inside the tab. you can
override tabbedpanel.newlink and return a submitlink instead.
-igor
On Mon, Apr 14, 2008 at 3:28 PM, Michael Mehrle [EMAIL PROTECTED] wrote:
You mean the links that select/toggle each panel? Not sure what you mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form. If
it
can,
that would be lovely. But I was under the impression that you can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I tried
was
to
make each panel into a FormComponentPanel and then add it to the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form, please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is
out
of
my hand. It's got to have tabs. Of course it is possible to do the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a way
to
go
since the complexity of managing the tabbed panel would then be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make
sense.
Again, if anyone wants to share any tips/input regarding this (or
how
to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I need to build a TabbedPanel with three tabs which are part
of
one
form
- the selected tab will contain form components which need to
be
submitted by that one form. It seems FormComponentPanel is
the
way
to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
RE: Good example for FormComponentPanel?
Oh, I think you misunderstood - it's just a matter of having one of
three panels visible, and all of them are part of one form. The submit
button is outside the tabbed panel.
form wicket:id=form
div wicket:id=tabbedPanel /
input type=button wicket:id=submit /
/form
It's something like the above. Assuming that the panels are simply
placeholders for a set of form components, this is going to work?
(meaning the panel's form components will be recognized as being part of
the parent form?)
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 3:33 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
yes, those links. by default they are regular a href links, so they
wont submit the values of components that are inside the tab. you can
override tabbedpanel.newlink and return a submitlink instead.
-igor
On Mon, Apr 14, 2008 at 3:28 PM, Michael Mehrle [EMAIL PROTECTED]
wrote:
You mean the links that select/toggle each panel? Not sure what you
mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day
DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form.
If
it
can,
that would be lovely. But I was under the impression that you
can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I
tried
was
to
make each panel into a FormComponentPanel and then add it to the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight
form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form,
please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the
panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision
is
out
of
my hand. It's got to have tabs. Of course it is possible to do
the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a
way
to
go
since the complexity of managing the tabbed panel would then be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make
sense.
Again, if anyone wants to share any tips/input regarding this
(or
how
to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I need to build a TabbedPanel with three tabs which are
part
of
one
form
- the selected tab will contain form components which need
to
be
submitted by that one form. It seems FormComponentPanel is
the
way
to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Re: Good example for FormComponentPanel?
On Mon, Apr 14, 2008 at 3:52 PM, Michael Mehrle [EMAIL PROTECTED] wrote:
Oh, I think you misunderstood
no, i didnt. instead of all this theorizing why dont you try to
implement this and see what the problems with it are. you will find
that since tabbed panel uses are regular links any information you
type into fields inside the tabbed panel will not be submitted and
therefore be lost since when you switch from tab to tab. what you need
to do is submit the fields when users switch tabs, the way to do that
is what i have outlined in my previous email.
-igor
- it's just a matter of having one of
three panels visible, and all of them are part of one form. The submit
button is outside the tabbed panel.
form wicket:id=form
div wicket:id=tabbedPanel /
input type=button wicket:id=submit /
/form
It's something like the above. Assuming that the panels are simply
placeholders for a set of form components, this is going to work?
(meaning the panel's form components will be recognized as being part of
the parent form?)
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 3:33 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
yes, those links. by default they are regular a href links, so they
wont submit the values of components that are inside the tab. you can
override tabbedpanel.newlink and return a submitlink instead.
-igor
On Mon, Apr 14, 2008 at 3:28 PM, Michael Mehrle [EMAIL PROTECTED]
wrote:
You mean the links that select/toggle each panel? Not sure what you
mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day
DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one form.
If
it
can,
that would be lovely. But I was under the impression that you
can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I
tried
was
to
make each panel into a FormComponentPanel and then add it to the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a *panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a straight
form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form,
please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the
panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design decision
is
out
of
my hand. It's got to have tabs. Of course it is possible to do
the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is a
way
to
go
since the complexity of managing the tabbed panel would then be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make
sense.
Again, if anyone wants to share any tips/input regarding this
(or
how
to
avoid traps), please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
RE: Good example for FormComponentPanel?
Alright, got it. Actually, for my purposes losing the tab info is
actually what I need, so this should work.
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 5:48 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
On Mon, Apr 14, 2008 at 3:52 PM, Michael Mehrle [EMAIL PROTECTED]
wrote:
Oh, I think you misunderstood
no, i didnt. instead of all this theorizing why dont you try to
implement this and see what the problems with it are. you will find
that since tabbed panel uses are regular links any information you
type into fields inside the tabbed panel will not be submitted and
therefore be lost since when you switch from tab to tab. what you need
to do is submit the fields when users switch tabs, the way to do that
is what i have outlined in my previous email.
-igor
- it's just a matter of having one of
three panels visible, and all of them are part of one form. The
submit
button is outside the tabbed panel.
form wicket:id=form
div wicket:id=tabbedPanel /
input type=button wicket:id=submit /
/form
It's something like the above. Assuming that the panels are simply
placeholders for a set of form components, this is going to work?
(meaning the panel's form components will be recognized as being part
of
the parent form?)
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 3:33 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
yes, those links. by default they are regular a href links, so they
wont submit the values of components that are inside the tab. you can
override tabbedpanel.newlink and return a submitlink instead.
-igor
On Mon, Apr 14, 2008 at 3:28 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
You mean the links that select/toggle each panel? Not sure what you
mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day
DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one
form.
If
it
can,
that would be lovely. But I was under the impression that you
can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I
tried
was
to
make each panel into a FormComponentPanel and then add it to
the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a
*panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a
straight
form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form,
please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the
panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
Yes, I agree, Vitaly - but unfortunately the design
decision
is
out
of
my hand. It's got to have tabs. Of course it is possible to
do
the
tabbing
by CSS styling, but I wanted to see if FormComponentPanel is
a
way
to
go
since the complexity of managing the tabbed panel would then
be
shifted to
the CSS/JS side.
I just looked at the Multiply example and it seems to make
sense.
Again, if anyone wants to share any tips/input regarding
Re: Good example for FormComponentPanel?
hmm, kinda weird to use the tab metaphor for this then. maybe a
dropdown or radios that switch the panel would work better. but thats
just me.
-igor
On Mon, Apr 14, 2008 at 6:49 PM, Michael Mehrle [EMAIL PROTECTED] wrote:
Alright, got it. Actually, for my purposes losing the tab info is
actually what I need, so this should work.
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 5:48 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
On Mon, Apr 14, 2008 at 3:52 PM, Michael Mehrle [EMAIL PROTECTED]
wrote:
Oh, I think you misunderstood
no, i didnt. instead of all this theorizing why dont you try to
implement this and see what the problems with it are. you will find
that since tabbed panel uses are regular links any information you
type into fields inside the tabbed panel will not be submitted and
therefore be lost since when you switch from tab to tab. what you need
to do is submit the fields when users switch tabs, the way to do that
is what i have outlined in my previous email.
-igor
- it's just a matter of having one of
three panels visible, and all of them are part of one form. The
submit
button is outside the tabbed panel.
form wicket:id=form
div wicket:id=tabbedPanel /
input type=button wicket:id=submit /
/form
It's something like the above. Assuming that the panels are simply
placeholders for a set of form components, this is going to work?
(meaning the panel's form components will be recognized as being part
of
the parent form?)
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 3:33 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
yes, those links. by default they are regular a href links, so they
wont submit the values of components that are inside the tab. you can
override tabbedpanel.newlink and return a submitlink instead.
-igor
On Mon, Apr 14, 2008 at 3:28 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
You mean the links that select/toggle each panel? Not sure what you
mean
though - can you please elaborate?
Michael
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 1:37 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
if you replace tabbedpanel links to submitlink it will
-igor
On Mon, Apr 14, 2008 at 12:51 PM, Michael Mehrle
[EMAIL PROTECTED] wrote:
So, a form CAN contain a panel? Meaning, I am able to add a
tabbedpanel
to a form and it'll work?
Michael
-Original Message-
From: Nick Heudecker [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 10:29 AM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
A FormComponentPanel is used to combine several individual form
components
into a single object, like if you had year/month/day
DropDownChoices
in
a
single component.
AFAIK, forms can contain anything except pages.
On Mon, Apr 14, 2008 at 12:26 PM, Michael Mehrle
[EMAIL PROTECTED]
wrote:
I am pretty sure that a tabbed panel can't be part of one
form.
If
it
can,
that would be lovely. But I was under the impression that you
can't
add
panels to a form.
Could someone clarify this for me? BTW, one of the things I
tried
was
to
make each panel into a FormComponentPanel and then add it to
the
tabbed
panel. Well, turns out that FormComponentPanel is NOT a
*panel*
after
all
(bad naming IMHO).
At this point I'm thinking of simply building it as a
straight
form
and
then turn some of it into tabs via divs and CSS.
Again, if there's a way to use a tabbed panel inside a form,
please
let me
know.
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 5:23 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the
panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle
[EMAIL PROTECTED
RE: Good example for FormComponentPanel?
Yes, I agree, Vitaly - but unfortunately the design decision is out of my hand. It's got to have tabs. Of course it is possible to do the tabbing by CSS styling, but I wanted to see if FormComponentPanel is a way to go since the complexity of managing the tabbed panel would then be shifted to the CSS/JS side. I just looked at the Multiply example and it seems to make sense. Again, if anyone wants to share any tips/input regarding this (or how to avoid traps), please don't be shy ;-) Michael -Original Message- From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED] Sent: Friday, April 11, 2008 4:52 PM To: users@wicket.apache.org Subject: Re: Good example for FormComponentPanel? It seems that a simple panel would be the best approach. On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle [EMAIL PROTECTED] wrote: I need to build a TabbedPanel with three tabs which are part of one form - the selected tab will contain form components which need to be submitted by that one form. It seems FormComponentPanel is the way to go: are there any good examples of this? Also, would this be the recommended approach? Thanks, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Good example for FormComponentPanel?
package org.apache.wicket.extensions.markup.html.tabs;
public class TabbedPanel extends Panel --- it extends the panel
{ ... }
Am I wrong? :)
On Sat, Apr 12, 2008 at 2:11 AM, Michael Mehrle [EMAIL PROTECTED] wrote:
Yes, I agree, Vitaly - but unfortunately the design decision is out of my
hand. It's got to have tabs. Of course it is possible to do the tabbing by
CSS styling, but I wanted to see if FormComponentPanel is a way to go since
the complexity of managing the tabbed panel would then be shifted to the
CSS/JS side.
I just looked at the Multiply example and it seems to make sense. Again, if
anyone wants to share any tips/input regarding this (or how to avoid traps),
please don't be shy ;-)
Michael
-Original Message-
From: Vitaly Tsaplin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:52 PM
To: users@wicket.apache.org
Subject: Re: Good example for FormComponentPanel?
It seems that a simple panel would be the best approach.
On Sat, Apr 12, 2008 at 1:37 AM, Michael Mehrle [EMAIL PROTECTED] wrote:
I need to build a TabbedPanel with three tabs which are part of one form
- the selected tab will contain form components which need to be
submitted by that one form. It seems FormComponentPanel is the way to
go: are there any good examples of this?
Also, would this be the recommended approach?
Thanks,
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
