UI discussions 2007-02-08

[Andrew Cagney <cagney@redhat.com>]

[Note: next meeting 9:30 US East time, 2007-02-14; double clash thursday]

Elena, Kris, Sami, Mike, Phil, Rick, Mark, Scox, Nurdin, Tim?
Moller sent apology.


Session Assistant
-----------------

Mike and Sami's changes were reviewed.  Agreed much better.  The follow 
list the "nits" identified for each page:

-> Session Manager
- Again need to make how to create a new session clearer
- "edit" button should be removed for now (it can come back later when 
it really does edit the session - a more advanced concept)

-> Add Assistant introduction with (go away tickbox)
HIG suggests that an assistant start with an overview window explaining 
what will happen next.  Should include a tick box (and include in 
preference) to not show again - so it doesn't get anoying.

-> Try adding a task picker - debug or monitor chooser here

-> Process Picker
- LHS and RHS lists should be identical
- LHS and RHS lists should be same size
- Start with just PID, and name; and way to add others

-> Observer Picker
- give threads observer defaults - fork, clone, exec, terminate; and 
catch backtrace
- improve help text for each observer
- add a "save" button?


Source Code Window
------------------

- fix "continue" button, wired to "run"
- when no source code, display raw assembly in source window
Means creating a fake "dom" or source code object so that the Source 
Code Window can't tell the difference - polymorp.
- ensure selected frame always highlighted
- drop line numbers (by default?); save real estate
- highlight as much of "current line" as possible: if .debug_line 
indicates entire line, highlight hard left to hard right; if .debug_line 
indicates partial-line, highlight part; if .debug_line indicates 
multiple lines, highlight all.
- needs keyboard short cuts
- step button should not pop-up a process picker; step is for selected 
thread only; add menu for more complex cases
- "thread id", not "tid"; better or bonus marks for finding the name in 
the stack backtrace
- start looking at an integrated source/assembly view


Monitor Window
--------------

[from last week] Brief discussion about what should happen when a user 
clicks on an event:
-> below the timeline, the backtrace and source code for the event is 
displayed


Command Line
------------

[from last week] The following options have been proposed:
-> frysk --debug PID : brings up the debug window directly
-> frysk --terminal : brings up a monitor with the terminal dominating
-> frysk --monitor PID : brings up the monitor window
[also]
-> frysk --session SESS : starts the specified session
-> frysk <core-file> : brings up the debug window on the core file



Next Week
---------

Custom Observers
?

/