Recent changes to feature-requests

Provide standard tooltip format

Rachel Rodgers — Tue, 22 May 2007 17:15:52 -0000

When a standardized way of commenting tapsets has been implemented, the tooltips should use this format to make them better laid out and more visually appealing.

Drag and Drop Probes/Functions

Rachel Rodgers — Wed, 11 Apr 2007 23:08:33 -0000

Allow the user to drag a probe or function from the side menu and drop it into the editor as an alternative to double clicking it.

View raw data in dashboard

Ryan Morse — Sat, 28 Oct 2006 22:48:08 -0000

There should be an option on the graphs, possibly right
click menu, that will allow the user to view all the
information from that graph in a table. In addition
there ought to be a way for users to save both the
graph and/or the raw data.

Ability to stack graphs

Ryan Morse — Thu, 12 Oct 2006 20:11:42 -0000

There should be some method for allowing graphs to be
stacked on top of each other. In doing so both graph's
data should remain visible. When combined, there
should also be a way to split them appart.

Ability to quickly track functions/variables

Ryan Morse — Thu, 12 Oct 2006 20:09:10 -0000

In the Probe Alias Browser there should be an option
when a user right clicks on a probe point or variable
to track this value. Clicking this should
automatically create and run a new script that will
watch that specific value. The user never needs to see
the contents of this script.

For function calls, it could simply count the number of
times the function is called each second. For
variables it could print out the value of the variable
every time it is hit, as well as counting the number of
times it is called each second.

Generate entry/return probes when possible

Anonymous — Fri, 15 Sep 2006 14:21:35 -0000

The probes generated from the kernel source view always
use the line number form, which limits portability.
Where possible, entry and return probes should be
generated instead. From a UI perspective, perhaps if
the user double-clicks anywhere before the opening
brace of a function, this should generate an entry
probe, and clicking on a closing brace should generate
a return probe (what to do when everything is on the
same line?), and anywhere in between use a line number
version. Maybe there should also be a toggleable mode
where clicking anywhere within a function always
generates an entry/return pair (or just entry probes,
again settable via preferences).

Allow dashboard module creation from live graph

Tom Zanussi — Thu, 14 Sep 2006 21:29:44 -0000

It would be convenient to be able to be able to create
a dashboard module from a currently running graphical
view in the Graphing Perspective. In order to create a
dashboard module now, you go through essentially the
same steps from the IDE perspective's Export Script
action as you do to set up a graphical display in the
Graphing perspective. Since all the information needed
should be (or could be made) accessible to the Graphing
perspective, it would probably be user-friendly to
allow the user to 'snapshot' the current view than to
do or re-do it from the IDE perspective.

Graphing system is too slow

Ryan Morse — Thu, 07 Sep 2006 14:59:20 -0000

Graphing system uses approximatly 10% of CPU at start,
and will continue to use ever increasing amounts.
After about 15 minutes it is using upwards of 60%. It
should not increase the CPU usage over time.
Additionally, it seems that there can only be about 8
graphs active at a time before everything slows down
too much to display reliable information.

Quantitative Bars within DataSet

Jeff Briggs — Wed, 06 Sep 2006 18:35:47 -0000

It would be nice to add graphical bars as a column in
the DataSet similar to other tools. Esentially a built
in bar graph right into the DataSet.

Trace Function Calls

Jeff Briggs — Wed, 06 Sep 2006 18:32:33 -0000

Need to add the ability to trace function calls down
from a particular functional call invocation in a
process or in the kernel, or system calls.