Hey,
What are the differences between the TreeVirtual and the VirtualTree?
Just check out the demos of both trees [1]. They are technically different and
do have different roots. The VirtualTree is based on the newer virtual
infrastructure and looks like the old, non virtual tree. It is fully data
binding integrated e.g. The TreeVirtual is based on the table and can therefore
show multiple columns.
I'm creating a tree dynamically:
each time a branch is opened, a branch/leaf is renamed, deleted, moved a
call to a json server is made to obtain infos or check the rights.
In my case which one is the best?
Sounds like you could use data binding to get that done. In that case, I would
prefer the TreeVirual.
If VirtualTree is the best, is it easy to 'migrate'/adapt the code to use
VirtualTree instead of TreeVirtual?
No, the API's are not compatible and the migration steps would lead to a change
in the application logic due to the data binding.
Regards,
Martin
[1] http://demo.qooxdoo.org/current/demobrowser/#
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
