View Single Post
  #18  
Old 07-05-2007, 02:00 PM
quant's Avatar
quant quant is online now
Registered User
 
Join Date: 11-30-2006
Posts: 967
Quote:
Originally posted by janrif
I was thinking that there might be a way to accomplish the task requested w a practical workaround. If more details were available, someone might come up w a useful idea.
xja,
would it help if only the search pane shows some kind of tree structure?

Depending on the level in the tree, in the first column of the search pane (which is fixed to be an item name) would be indented (simple empty chars) and preceded with └ sign, sth like this

Column1 Column2
Root
_└ A
_└ B
__└ B2
_└ C
__└ C3

Note that there is an item C3 on level 3 straight under item from level 1, ie. item on level 2 doesn't pass the search query.
This should be very easily implemented based on the lineage attribute (ie. simply replace number of slash signs in the lineage attribute by number of empty chars), the only other thing that needs to be implemented is sorting of the search results to recover tree structure (again simple algorithm based on lineage attribute). There needs to be a little tweaking with the indentation based on whether parent/grand-parent/ ... are also in the search result (if not exist, decrease indentation).

The result would be a FILTERED tree structure based on your search. Sure, not aesthetically perfect (and only static with all nodes expanded), but would do the trick

But thinking about it, if this could be implemented, then surely the search pane could just use the "tree module" that Data explorer pane uses ... no overhead here, cause this is only the search result pane that "dies" once you click Enter on an item or navigate somewhere else in the Data explorer pane.
Reply With Quote