public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "swagiaal at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4149] Assistant missing [optional] what happens next page Date: Wed, 21 Mar 2007 15:54:00 -0000 [thread overview] Message-ID: <20070321155403.2207.qmail@sourceware.org> (raw) In-Reply-To: <20070306212438.4149.cagney@redhat.com> ------- Additional Comments From swagiaal at redhat dot com 2007-03-21 15:54 ------- 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 ? -- http://sourceware.org/bugzilla/show_bug.cgi?id=4149 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2007-03-21 15:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-06 21:24 [Bug general/4149] New: " cagney at redhat dot com 2007-03-06 21:26 ` [Bug general/4149] " cagney at redhat dot com 2007-03-19 20:37 ` swagiaal at redhat dot com 2007-03-21 15:54 ` swagiaal at redhat dot com [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=20070321155403.2207.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /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: linkBe 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).