|
What I meant is that there are varying ideas/preferences for what hoisting would actually provide and how it would be implemented.
Some actually want a filtered tree (where hoisting could be considered one type of a filtered tree); others want or independent trees in tabs; etc.
Even in the case of "simple" hoisting, there are many questions about implementation: should logically linked items not in the hoisted tree be included or excluded? Should searches be restricted to the hoisted data? Should favorites also be filtered to show only hoisted items? When/how to hoist/de-hoist? Should hoisting automatic (ala auto scroll/collapse) or manual? Should multiple hoist levels be supported? How does multiple tabs play into hoisting? Etc.
To implement in a way that accommodates even half of users' preferences and doesn't sacrifice performance would take several months of effort (at least), so it just can't be done for v3.0 (one of the drivers for v3 is Vista support and Vista is now available to consumers).
|