Bug 4149 - Assistant missing [optional] what happens next page
Summary: Assistant missing [optional] what happens next page
Status: WAITING
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 3401
  Show dependency treegraph
 
Reported: 2007-03-06 21:24 UTC by Andrew Cagney
Modified: 2007-03-21 15:54 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
screen shot of a possible assistant page (25.34 KB, image/png)
2007-03-19 20:37 UTC, Sami Wagiaalla
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2007-03-06 21:24:38 UTC
The Session Assistant needs to clearly explain what is going to happen next with
an introductory page.

-> clicking "next" on that page goes to the current first proc-picker page
-> clicking, don't show this again tick-box, stops the page appearing
-> editing preferences lets the box again appear
Comment 1 Andrew Cagney 2007-03-06 21:26:49 UTC
It might also be better to, at this point, have the user select if they want to
create a debug or monitoring session (i.e., before they get to the proc-picker).

(that would mean that the screen isn't optional).
Comment 2 Sami Wagiaalla 2007-03-19 20:37:00 UTC
Created attachment 1629 [details]
screen shot of a possible assistant page

would something like the attached screenshot help ? with some nice icons maybe
?
This would be page 2 in the assistant.
Comment 3 Sami Wagiaalla 2007-03-21 15:54:03 UTC
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 Assitant 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).
    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 ?