[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #9755: Debugger: Search field to filter images list
From:       "bonefish" <trac () haiku-os ! org>
Date:       2013-05-31 23:44:01
Message-ID: 056.dbc3a0bdbac82750c788d897ea835255 () haiku-os ! org
[Download RAW message or body]

#9755: Debugger: Search field to filter images list
-------------------------------------+----------------------------
   Reporter:  stippi                 |      Owner:  anevilyak
       Type:  enhancement            |     Status:  in-progress
   Priority:  normal                 |  Milestone:  Unscheduled
  Component:  Applications/Debugger  |    Version:  R1/Development
 Resolution:                         |   Keywords:
 Blocked By:                         |   Blocking:
Has a Patch:  0                      |   Platform:  All
-------------------------------------+----------------------------

Comment (by bonefish):

 TBH, I think the list view is way too small to be really effective. Even
 if you squeeze the search field besides the horizontal scroll bar to avoid
 losing even more space, the view probably won't be higher than 10 to 15
 lines. Considering that a tree structure is shown, we lose one line per
 path component and possibly get very sparse results. The view also isn't
 particularly wide.

 One can resize the view with the splitter, but the more interesting parts
 are the source and the variables view, so it's generally not desirable to
 do that. When searching for a file/function one wants a larger view,
 otherwise a small view is fine. When entering the search mode (via
 shortcut/button) the view could become larger temporarily. Or the view
 stays as it is and the search functionality is implemented in a dialog.
 E.g Pe's "Find Function" dialog does something rather similar to what we
 might want here.

 Regarding your questions:

 1) I think regular expressions would be overkill and possibly even
 inconvenient to use. Support for simple shell glob patterns (particularly
 "*") would be nice, though. Partial matches should suffice, though, so
 that one doesn't have to prepend and append a "*" when searching some
 substring in the middle.

 2) The search should be live.

 3) Not sure. If the multi-level tree view is kept, I would expand the
 nodes up to the component that matches. If subcomponents don't match,
 remove them. If implemented in a separate dialog, I would then support
 invoking (i.e. double-clicking/selecting+Enter) directories or files. The
 dialog would then restrict the search to that directory/file and clear the
 search string, so that one can quickly narrow down the search in case of
 big libraries/applications. Flattening the paths (but keeping a second
 level for the functions) might work as well. One could use the fact that
 the whole path is matched and e.g. use "/su" to find the support kit
 sources in libbe.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9755#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

[prev in list] [next in list] [prev in thread] [next in thread]