Unlike the MVC-based WTreeView, the tree renders a widget hierarchy,
rather than a hierarhical standard model. This provides extra flexibility (as
any widget can be used as contents), at the cost of server-side, client-side
and bandwidth resources (especially for large tree tables).