jspraul / slimtune

Automatically exported from code.google.com/p/slimtune
MIT License
0 stars 0 forks source link

Provide a search box in both views #12

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
It is currently impractical to find a particular method by its name in both 
views, especially if it doesn't have a big impact on performance. Sometimes, 
it's useful to see how much time a specific method takes, even though it 
isn't a bottleneck. For example, when comparing before and after an 
optimization. A search box (if possible search-as-you-type) would be nice.

Original issue reported on code.google.com by tristanl...@gmail.com on 10 Feb 2010 at 12:48

GoogleCodeExporter commented 9 years ago
I think what I will do is to write up a separate visualizer that gives you a 
lot of
information about a specific function, and put search options in there. It'll
essentially be a cut down version of the NProf style. On the left, a single 
list of
functions sorted by most time exclusive (or inclusive?), with a 
filter-as-you-type
box like how iTunes does it. Then a main pane with all the gory details.

Adding search to the existing visualizers is a little tricky; not 
insurmountable but
enough to miss the 0.2.0 release anyway. Gotta draw the line somewhere.

Sound reasonable?

Original comment by promit....@gmail.com on 10 Feb 2010 at 3:07

GoogleCodeExporter commented 9 years ago
Seems fine to me!

Original comment by tristanl...@gmail.com on 10 Feb 2010 at 3:18

GoogleCodeExporter commented 9 years ago
I've put up the first iteration of this in a new Function Details visualizer 
that
will ship with 0.2.0. It's a bit of a rough draft but it should be a decent 
start.
Here's a picture:
http://ventspace.files.wordpress.com/2010/02/021310-funcpie.png

Original comment by promit....@gmail.com on 14 Feb 2010 at 5:23

GoogleCodeExporter commented 9 years ago
I guess this is what we're rolling with for the time being.

Original comment by promit....@gmail.com on 16 Jul 2010 at 2:12