Virtual Tree 3.2 Dot Net Control (Repost)

dotNET Control | Rapidshare.com | 8 Mb

Unlike most other tree controls, Virtual Tree is designed from the ground up to be data driven. Most other tree controls have a basic "unbound" mode in which the tree representation is built manually. If they support data binding, it is typically built on top of this "unbound" mode and simply generates the in-memory representation (consisting of tree nodes) when the Data Source is set. For large Data Sources this approach can be both extremely slow and resource hungry.

The Virtual Tree approach is radically different. It does not have a separate "unbound" mode at all. This allows the design to leverage the power of data binding to extract only the information from the Data Source required to display the current state of the tree representation. This means that, regardless of the size of the Data Source, Virtual Tree only initially needs to build a display of the first 30 or so items (ie the typical number of rows displayed on a screen). As the user browses the tree, Virtual Tree extracts the information required on-demand from the Data Source. This approach greatly improves initial load times and reduces the memory footprint.

Most other data binding solutions provide only limited ability to customize the appearance or behaviour of the control. If you want to do anything more advanced you have to revert to the "unbound" mode. Because Virtual Tree is designed from the ground up to be data driven it does not suffer from this problem. You can customize just about every aspect of it's appearance and behaviour without having to sacrifice the ability to use data binding. Virtual Tree can do anything possible with a traditional "unbound" tree control plus a whole lot more.