From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: fhpd user interaction (and corefiles)
Date: Mon, 05 Nov 2007 09:52:00 -0000 [thread overview]
Message-ID: <472EE7E6.9050609@redhat.com> (raw)
In-Reply-To: <472B2AC3.3080609@redhat.com>
Andrew Cagney wrote:
> Phil Muldoon wrote:
>> The question here then: if the LinuxHost code has a question for the
>> user, how does it ask that user the question via CoreCommand? As far
>> as I can tell, none of the fhpd commands are interactive.
> As you point out, the bottom line is fstack et.al., where no
> interaction is possible. The create either succeeds or fails. With
> that in mind can i suggest considering instead how you might interact
> with this from a UI. For instance, would this work:
> ->File->Open
> use file browser to open a core file
> <<Core file assistant appears; perhaps pre-populated with info from
> raw core file>>
> - indicates what action is going to happen next, for instance
> indicates the executable it will attempt to open (or don't bother)
> - OK attempts to open the executable or fails leaving the user
> with the assistant
> from a cli, a similar interaction might be:
> (fhpd) core foo
> Executable <exe> for <foo> not found.
Yeah, pretty much what I was thinking. I'm still undecided how
LinuxHost.java should message back that the corefile executable has not
been found. I could raise a (checked) exception, but that somewhat
indicates an error condition when it is not. I could implement
callbacks, but that would require a declared interface, which may muddle
the very simple and clean interaction now.
Any ideas?
Regards
Phil
>
next prev parent reply other threads:[~2007-11-05 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 10:03 Phil Muldoon
2007-11-02 13:50 ` Andrew Cagney
2007-11-05 9:52 ` Phil Muldoon [this message]
2007-11-08 11:25 ` Phil Muldoon
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=472EE7E6.9050609@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.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).