public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Sami Wagiaalla <swagiaal@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: Assistant refinement
Date: Wed, 21 Mar 2007 19:23:00 -0000	[thread overview]
Message-ID: <46018607.9050805@redhat.com> (raw)
In-Reply-To: <46017E7D.8090004@redhat.com>

I am suggesting this:

user starts up frysk:

[1]
A page pops up with a list of previous sessions the buttons new and 
delete to the side.
in the bottom the buttons [next] and [finish].
clicking [finish] at any point starts the monitor/debugger depending on 
was was saved from before.
this enables the user to select the session and start it in two clicks.

user clicks next/new

[2]
they see the page currently referred to as the process picker.
In the bottom the buttons [back] [next] [finish]

user clicks next

[3]
they see this: 
http://sourceware.org/bugzilla/attachment.cgi?id=1629&action=view
(maybe here if they choose "debugging" (should be Debuging Session :)) 
then next is disabled)

user clicks next

[4]
they see observer picker

This stream-lines the process, eliminates extra clicks when restarting 
an old session, eliminates loops and branches in the story board, and 
eliminates the quick debug button.


Andrew Cagney wrote:
> 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 ?
>>
>>
>

  reply	other threads:[~2007-03-21 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 16:17 Sami Wagiaalla
2007-03-21 17:48 ` Sami Wagiaalla
2007-03-21 18:50 ` Andrew Cagney
2007-03-21 19:23   ` Sami Wagiaalla [this message]
2007-03-22 17:59     ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46018607.9050805@redhat.com \
    --to=swagiaal@redhat.com \
    --cc=cagney@redhat.com \
    --cc=frysk@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).