Wicket's Wizard Component
I am attempting to enhance the Wizard's layout by sub-classing Wizard.java. The idea is to change the default markup to suit some specific layout requirements. The problem I am trying to solve is to re-parent the form to the component bound to the wicket:id myOuterWrapperComp, but not sure if or how this can be done using the Wizard framework. I am using Wicket Version 1.4.13. Can this be done using sub-classing Wizard.java? I would like to avoid writing my own class that mimics 99% of what Wizard.java provides, just for this layout issue. Here is a sample of the markup in my DerivedFromWizard (not real name) class, div wicket:id=myOuterWrapperComp class=wicketExtensionsWizard form wicket:id=form class=wicketExtensionsWizardForm ... rest of wizard markup, same as what is in Wizard.html /form /div Thanks, J.D.
Re: Wicket's Wizard Component
Wizard probably ought to be moved to the category of example code instead of something that can (or will) be improved. It hasn't changed much since it was written, and if it were changed, would probably break hundreds of users for no real benefit (i.e. users would have to go implement new interfaces for components that already work and have long since been forgotten about). IMHO, if you like the code, you might be better off just grabbing a copy of it into your own source tree. Then you can build what you want with impunity. Brian On May 21, 2011, at 11:08 AM, Corbin, James wrote: I am attempting to enhance the Wizard's layout by sub-classing Wizard.java. The idea is to change the default markup to suit some specific layout requirements. The problem I am trying to solve is to re-parent the form to the component bound to the wicket:id myOuterWrapperComp, but not sure if or how this can be done using the Wizard framework. I am using Wicket Version 1.4.13. Can this be done using sub-classing Wizard.java? I would like to avoid writing my own class that mimics 99% of what Wizard.java provides, just for this layout issue. Here is a sample of the markup in my DerivedFromWizard (not real name) class, div wicket:id=myOuterWrapperComp class=wicketExtensionsWizard form wicket:id=form class=wicketExtensionsWizardForm ... rest of wizard markup, same as what is in Wizard.html /form /div Thanks, J.D. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Wicket's Wizard Component
Actually, it makes sense to pull the source and modify it to support my specific needs. J.D. -Original Message- From: Brian Topping [mailto:topp...@codehaus.org] Sent: Saturday, May 21, 2011 9:29 AM To: users@wicket.apache.org Subject: Re: Wicket's Wizard Component Wizard probably ought to be moved to the category of example code instead of something that can (or will) be improved. It hasn't changed much since it was written, and if it were changed, would probably break hundreds of users for no real benefit (i.e. users would have to go implement new interfaces for components that already work and have long since been forgotten about). IMHO, if you like the code, you might be better off just grabbing a copy of it into your own source tree. Then you can build what you want with impunity. Brian On May 21, 2011, at 11:08 AM, Corbin, James wrote: I am attempting to enhance the Wizard's layout by sub-classing Wizard.java. The idea is to change the default markup to suit some specific layout requirements. The problem I am trying to solve is to re-parent the form to the component bound to the wicket:id myOuterWrapperComp, but not sure if or how this can be done using the Wizard framework. I am using Wicket Version 1.4.13. Can this be done using sub-classing Wizard.java? I would like to avoid writing my own class that mimics 99% of what Wizard.java provides, just for this layout issue. Here is a sample of the markup in my DerivedFromWizard (not real name) class, div wicket:id=myOuterWrapperComp class=wicketExtensionsWizard form wicket:id=form class=wicketExtensionsWizardForm ... rest of wizard markup, same as what is in Wizard.html /form /div Thanks, J.D. - 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: Wicket's Wizard Component
To the core wicket developers, is there any copyright concerns with pulling the Wizard source into my codebase and modifying it? J.D. -Original Message- From: Corbin, James [mailto:jcor...@iqnavigator.com] Sent: Saturday, May 21, 2011 9:37 AM To: users@wicket.apache.org Subject: RE: Wicket's Wizard Component Actually, it makes sense to pull the source and modify it to support my specific needs. J.D. -Original Message- From: Brian Topping [mailto:topp...@codehaus.org] Sent: Saturday, May 21, 2011 9:29 AM To: users@wicket.apache.org Subject: Re: Wicket's Wizard Component Wizard probably ought to be moved to the category of example code instead of something that can (or will) be improved. It hasn't changed much since it was written, and if it were changed, would probably break hundreds of users for no real benefit (i.e. users would have to go implement new interfaces for components that already work and have long since been forgotten about). IMHO, if you like the code, you might be better off just grabbing a copy of it into your own source tree. Then you can build what you want with impunity. Brian On May 21, 2011, at 11:08 AM, Corbin, James wrote: I am attempting to enhance the Wizard's layout by sub-classing Wizard.java. The idea is to change the default markup to suit some specific layout requirements. The problem I am trying to solve is to re-parent the form to the component bound to the wicket:id myOuterWrapperComp, but not sure if or how this can be done using the Wizard framework. I am using Wicket Version 1.4.13. Can this be done using sub-classing Wizard.java? I would like to avoid writing my own class that mimics 99% of what Wizard.java provides, just for this layout issue. Here is a sample of the markup in my DerivedFromWizard (not real name) class, div wicket:id=myOuterWrapperComp class=wicketExtensionsWizard form wicket:id=form class=wicketExtensionsWizardForm ... rest of wizard markup, same as what is in Wizard.html /form /div Thanks, J.D. - 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
Re: Wicket's Wizard Component
Everything including Wizard has the ASL 2.0 copyleft at the top, which grants free and unrestricted use for commercial and non-commercial purposes. On May 21, 2011, at 11:40 AM, Corbin, James wrote: To the core wicket developers, is there any copyright concerns with pulling the Wizard source into my codebase and modifying it? J.D. -Original Message- From: Corbin, James [mailto:jcor...@iqnavigator.com] Sent: Saturday, May 21, 2011 9:37 AM To: users@wicket.apache.org Subject: RE: Wicket's Wizard Component Actually, it makes sense to pull the source and modify it to support my specific needs. J.D. -Original Message- From: Brian Topping [mailto:topp...@codehaus.org] Sent: Saturday, May 21, 2011 9:29 AM To: users@wicket.apache.org Subject: Re: Wicket's Wizard Component Wizard probably ought to be moved to the category of example code instead of something that can (or will) be improved. It hasn't changed much since it was written, and if it were changed, would probably break hundreds of users for no real benefit (i.e. users would have to go implement new interfaces for components that already work and have long since been forgotten about). IMHO, if you like the code, you might be better off just grabbing a copy of it into your own source tree. Then you can build what you want with impunity. Brian On May 21, 2011, at 11:08 AM, Corbin, James wrote: I am attempting to enhance the Wizard's layout by sub-classing Wizard.java. The idea is to change the default markup to suit some specific layout requirements. The problem I am trying to solve is to re-parent the form to the component bound to the wicket:id myOuterWrapperComp, but not sure if or how this can be done using the Wizard framework. I am using Wicket Version 1.4.13. Can this be done using sub-classing Wizard.java? I would like to avoid writing my own class that mimics 99% of what Wizard.java provides, just for this layout issue. Here is a sample of the markup in my DerivedFromWizard (not real name) class, div wicket:id=myOuterWrapperComp class=wicketExtensionsWizard form wicket:id=form class=wicketExtensionsWizardForm ... rest of wizard markup, same as what is in Wizard.html /form /div Thanks, J.D. - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
