Hi folks,
I hope this e-mail won't upset anyone too much.
Let me summarize our tree components situation first.
We have Tree and TreeTable components in core, and another Tree
component in extensions.
The Tree from extensions is the oldest one, without Ajax support.
The Tree in core (as well
* Matej Knopp:
I hope this e-mail won't upset anyone too much.
Let me summarize our tree components situation first.
We have Tree and TreeTable components in core, and another Tree
component in extensions.
[...]
a) remove the old (kinda unsupported) tree from extensions (is
Err. Sorry for not-explaining it right. This is not a vote. What I
suggest are all those three options.
-Matej
On 6/10/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* Matej Knopp:
I hope this e-mail won't upset anyone too much.
Let me summarize our tree components situation first.
We
I think it is much better.
As for the TreeTable: The new TreeTable that I plan (without those
neat lines but also without layout problems) is not alive yet. And the
one that we already have should be moved back to extensions. I don't
think we need (nor should have) TreeTable in core.
-Matej
On
So for the tree and treetable nothing changes with respect to wicket
1.2? Both are in extensions, and a new tree replaces the old, pre ajax
tree?
Martijn
On 6/10/07, Matej Knopp [EMAIL PROTECTED] wrote:
I think it is much better.
As for the TreeTable: The new TreeTable that I plan (without
Yes, exactly. That's what I want.
-Matej
On 6/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
So for the tree and treetable nothing changes with respect to wicket
1.2? Both are in extensions, and a new tree replaces the old, pre ajax
tree?
Martijn
On 6/10/07, Matej Knopp [EMAIL PROTECTED]
Is there any feature set available for the new treetable?
/Regards Mats
On 6/10/07, Matej Knopp [EMAIL PROTECTED] wrote:
Yes, exactly. That's what I want.
-Matej
On 6/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
So for the tree and treetable nothing changes with respect to wicket
1.2?
a) remove the old (kinda unsupported) tree from extensions (is
anyone even use it?)
+1
b) move the current Tree and TreeTable* from core to extensions
(sight, i know we moved it into core just recently)
Don't know yet.
c) move the new Tree into core.
So the 'new new' tree is
On 6/10/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
a) remove the old (kinda unsupported) tree from extensions (is
anyone even use it?)
+1
Cool.
b) move the current Tree and TreeTable* from core to extensions
(sight, i know we moved it into core just recently)
Don't know yet.
