From: Andrew Cagney <cagney@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: Assistant refinement
Date: Thu, 22 Mar 2007 17:59:00 -0000 [thread overview]
Message-ID: <4602C40B.8090809@redhat.com> (raw)
In-Reply-To: <46018607.9050805@redhat.com>
Sami Wagiaalla wrote:
> 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.
No. "next" is part of an assistant, and the Session Manager is not an
assistant. The Session Assistant is for either creating a "new"
session, or picking and [re-]"open"ing an existing session. In the case
of re-opening an existing [monitoring] session, the operation is
expensive and potentially fatal, the user needs to be presented with a
check-point confirming what's about to be monitored so that they can
confirm it. That means at minimum of double-click, click.
If the desire is just to reduce the mouse-click count then there are
better ways of doing this. For instance:
- debug session of a "new process" doesn't need process-picker and/or
observer-picker. For it "open" jumps to the source code window, starts
the process and runs it to main().
- let the user explicitly edit the session so that it skips the p-p
window. When combined with specialized logic, it would let the user
quickly monitor specific processes based on an arbitrary criteria. For
instance, a session to "Monitor the top 2 processes".
>
> 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)
>
Assuming the differentiation between debugging and monitoring remains,
then I think this question should be asked up front. That way the the
first thing the user is presented is:
-> a summary of what is happening
-> a question as to what they want to be doing initially
That way the user gets a warm-fuzzy that frysk "knows" what they want
and is being customized for that need. With out that up-front question
one is wondering: "where is this going?", "what is this doing?".
To give an example, consider connecting a machine to a network. As a
user, you have an ethernet cable in one hand and the lap-top in the
other. The first question you expect is: "which network type?"
"eithernet", "wireless", "modem", ... ;; and not "is this using dhcp?"
say - "DHCP for what"?
Andrew
prev parent reply other threads:[~2007-03-22 17:59 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
2007-03-22 17:59 ` Andrew Cagney [this message]
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=4602C40B.8090809@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=swagiaal@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).