From: Sami Wagiaalla <swagiaal@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Mike Cvet <mcvet@redhat.com>, frysk@sourceware.org
Subject: Re: EventViewer Rewrite
Date: Wed, 10 Jan 2007 20:29:00 -0000 [thread overview]
Message-ID: <45A54BD8.1080105@redhat.com> (raw)
In-Reply-To: <45A54800.1040302@redhat.com>
> The above, there might be a case (at some point) to make the behavior
> of the widget scriptable. (ie time tick or not, just count, etc).
> Personally I can see the printf model working with the tag-sets (tags
> tied to lines of code in a program) but wonder how useful it would to
> know that my program forked in the event-viewer, but not what time it
> forked. The immediate solution to that problem would have a custom
> observer create a log-event and plot to event-viewer. This bring us
> nicely to log and event-viewer integration (ie click a log entry in
> the log view, have it highlighted in the eventviewer). Certainly food
> for thought, and something to think on, down the line.
Its a good idea, scripting in particular has not occurred to me.
Providing more detailed information when the user selects a particular
event is in the plan. The time stamp could be provided there.
Integrating log and event viewer will make the event viewer multi
purpose, fulfilling our requirement for an off-line viewer int he future.
next prev parent reply other threads:[~2007-01-10 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 21:14 Sami Wagiaalla
2006-11-07 1:46 ` Sami Wagiaalla
2007-01-10 19:17 ` Sami Wagiaalla
2007-01-10 19:35 ` Phil Muldoon
2007-01-10 19:41 ` Mike Cvet
2007-01-10 20:00 ` Sami Wagiaalla
2007-01-10 20:06 ` Mike Cvet
2007-01-10 20:09 ` Phil Muldoon
2007-01-10 20:29 ` Sami Wagiaalla [this message]
2007-01-10 19:52 ` Sami Wagiaalla
2007-01-10 22:13 ` Nurdin Premji
2007-01-11 13:25 ` Sami Wagiaalla
2007-01-11 13:38 ` Phil Muldoon
2007-01-10 22:20 ` Nurdin Premji
2007-01-10 22:27 ` Nickolay V. Shmyrev
2007-01-11 13:43 ` Sami Wagiaalla
2007-01-11 14:18 ` Sami Wagiaalla
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=45A54BD8.1080105@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sourceware.org \
--cc=mcvet@redhat.com \
--cc=pmuldoon@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).