public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Frysk List <frysk@sourceware.org>
Subject: Question on CLI vs GUI, and today's call
Date: Wed, 21 Feb 2007 18:39:00 -0000	[thread overview]
Message-ID: <20070221183908.GA13807@ca-server1.us.oracle.com> (raw)

First of all, am I right that the CLI and GUI interfaces are mere shells
on top of the actual debugger/monitor core that handles all actual
functionality, and leaves the user interaction portion to the CLI and
GUI code?  That largely seems to be the case, and I just wanted to
confirm that this strict separation of focus is adhered to everywhere.

Which leads to another question, or comment...  Especially today's call
made me wonder a bit about the separation of processing core vs UI
because it seemed (at least to me) that part of the discussion turned
into the mechanics of stepping in the presence of multiple threads
rather than the user interaction part only.  Generally, when discussing
UI aspects, if it is not clear what a certain button, menu item, or
other element (or combination thereof) is wired to in the processing
core, there is a fundamental problem.  It indicates that either the
separation between presentation and processing is lost, or that the
behaviour at the processing level is not defined well enough to make it
clear how the user should interact with it.

I think it would make the calls a bit more targeted if we can recognize
when the conversation becomes more about the underlying mechanics and
defer that to discussion in a non-UI forum?

As always, all comments are welcome.

	Cheers,
	Kris

             reply	other threads:[~2007-02-21 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 18:39 Kris Van Hees [this message]
2007-02-22 21:46 ` Andrew Cagney
2007-02-23  0:33   ` Kris Van Hees
2007-02-23 14:37     ` Sami Wagiaalla
2007-02-23 16:14       ` 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=20070221183908.GA13807@ca-server1.us.oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=frysk@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: 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).