We already set it up as WIcket Skunkworks :)
There are couple of reasons to set up something new.
1) We have not earned the right to commit to one of the official
extension projects. It's a meritocratic thing after all.
2) At the moment it's hacked code and not a real component... some
experimentation is needed (hence skunkworks).
This way we can monkey with a component that we only know that we two
need. if it works well and others want it, we can migrate it to wicket
stuff.
I imaging there is quite a lot of Wicket code out there that people
have put together but is not at component quality, but none the less
has promise. Let this be the place where it gets experimented upon.
- Brill
On 11-Mar-09, at 12:47 PM, Jeremy Thomerson wrote:
Use wicket-stuff. It makes sense for this. You might even consider
just
adding this to minis in WS.
http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/trunk/wicketstuff-core/minis-parent/
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Mar 10, 2009 at 10:25 AM, Christian Helmbold <
[email protected]> wrote:
Instead of competing, why don't we set up a project some place and
check
both
solutions in under different packages?
We can then refactor them into one and take the best of both :)
I agree. Is there an existing place in the wicket project to do this?
I've discovered some troubles in my solution when multiple tabbed
panes are
used in one page. The state of other panels is not hold correctly
in the
URLs and so the tabbed panels influence each other.
---------------------------------------------------------------------
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]
