> Another idea is to do what I saw years ago on a system log viewer on a > mainframe where warnings and alerts have special colors and stay glued > in the list when they have scrolled to the top and only vanish when > acknowledged. I don't know whether it's feasible to mimic the exact > behaviour of that list widget (well, probably "tidget" because it was on > a 3270 terminal ;-), but we could at least have a list of unacknowledged > alerts and warnings on top of the normal list. The process I think you mention here is the system console on MVS. Depending on your console settings, messages flagged as critical (and those needing action) won't scroll off the screen when additional messages arrive. Instead they glue to the top of the console until you REPLY to them using their message number (e.g. REPLY 21,yes). -jlaska On Tue, 2004-12-07 at 14:14 +0100, Nils Philippsen wrote: > Hi Chris, > > On Mon, 2004-12-06 at 14:57 -0500, Chris Lumens wrote: > > Hey gang, I'm working on a redo of the system-logviewer GUI. Right now, > > it's all done by hand which isn't really the ideal situation. So as > > part of my attempts to learn glade and GTK in general, I've been working > > on a mockup of system-logviewer. I'm working on making sure it complies > > to the interface guidelines as well, but I've been told there are people > > on this list more expert than me at that step. So, I've posted a bunch > > of screenshots of the thing in glade as well as the .glade file itself > > to the following: > > > > http://people.redhat.com/clumens/system-logviewer/ > > > > None of the buttons are hooked up to do anything (well, some of them > > might close windows) and no log files get displayed. This is just a UI > > workup. Please let me know what you think and if there are any > > significant problems with it so far. > > I'd say that the user needn't know about a distinction between a warning > and alert list. I'd rather have a notification list (visible and in the > program logic) where users can specify the level (e.g. alert or warning) > and when it should be notifying which consists of: > > - log files/sources relevant (i.e. one, many or all log files) > - pattern(s*) to match for which can be search engine like (single words > or expressions like "word1 AND word2 AND (word3 OR word4)" or regexes > for complicated stuff > - probably a description, i.e. a warning could say "database volume on > host foo is nearly full" when encountering specific patterns, handy when > you want technically not so inclined people to make some meaning out of > a warning. If you could use variables from regex patterns to incorporate > in these messages (i.e. the hostname in the example), I'd award bonus > points for it ;-). > > Another idea is to do what I saw years ago on a system log viewer on a > mainframe where warnings and alerts have special colors and stay glued > in the list when they have scrolled to the top and only vanish when > acknowledged. I don't know whether it's feasible to mimic the exact > behaviour of that list widget (well, probably "tidget" because it was on > a 3270 terminal ;-), but we could at least have a list of unacknowledged > alerts and warnings on top of the normal list. > > Nils > -- > Nils Philippsen / Red Hat / nphilipp@xxxxxxxxxx > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." -- B. Franklin, 1759 > PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 -- Fedora-config-list mailing list Fedora-config-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-config-list