Re: Assistant refinement

[Andrew Cagney <cagney@redhat.com>]

Sami,

I'm not sure I'm following here ; merge what part of the session manager 
and the assistant?  What does a user see first?

Re-starting a session, which I think is the common case, is already 
pretty slick.  For instance, double click on "Debug bash" gets the 
proc-picker, and "finish/debug" gets the debugger for those processes.  
So I'm not sure how the assistant and session manager can be merged.  
The session manager lets the user control / select / [edit] / re-start / 
[eventually] resume sessions, creating a new session is just one 
sub-task from that window.

Looking at 
http://sourceware.org/bugzilla/attachment.cgi?id=1629&action=view it is 
roughly what was described, the HIG also has a good example of the 
initial screen and guidelines:
-> there should be a heading and summary paragraph explaining what is 
going on - big picture
-> the choices should have short single sentence descriptions
-> no apply button :-)
If "debug", the session would be called "Debug ...",  the event-picker 
can be skipped, "start debugger" ("debug"?) (replaces finish) jumps to 
source window ;; for "monitor", the session would be called "Monitor 
...", the event-picker is included in the sequence, and "start monitor" 
("monitor"?) (relaces finish) jumps to the monitor.

However, this assumes that there continue to be separate monitoring and 
debugging windows.  Ideas are still bouncing around for that one.  
Regardless the "qick debug" button should be on the left.

Andrew

Sami Wagiaalla wrote:
> Yet another assistant refinement suggestion:
>
> My comment on http://sourceware.org/bugzilla/show_bug.cgi?id=4149:
>
> I have a few suggestions to solve this, and the Quick Debug button 
> problem.
> Doing screen shots its time consuming so I will try to describe it 
> verbally and
> people feel they need screen shots, I throw some together.
>
> [1] Merge Session Manager into the Assistant so that it becomes page 1
> [2] At the bottom *always* have present a next, back, and finish 
> (start?)     button.
>    clicking the finish button takes you directly to frysk with the 
> default or
>    the previously saved settings
> [3] Page 2 of the session is a page which enables the user to choose 
> from a    Traditional debugging session or a Monitoring Session, 
> something like what      is in the attached screen shot    
> (http://sourceware.org/bugzilla/attachment.cgi?id=1629&action=view 
> <http://sourceware.org/bugzilla/attachment.cgi?id=1629&action=view>).
>    My feeling is that this should only effect what window (source or 
> monitor)
>    is presented first, and that the user can always switch between the 
> modes
>    even after the session has been started.
>
> The rest of the pages remain the same. Thoughts ?
>
>