Re: [Kmon-devel] Begin with the end in mind

[Frank D. <ke...@dr...>]

ehlo,

> as for the config dialog, it looks nice and might be usefull, but I'd
> prefer to have a config widget inside each KMonNode (so it can be displayed
> when needed, e.g. as popup after a RMB click, or alike)

ok, so the right part of 'servers' tab becomes probably that widget.
the first tab is more or less ok.

the actions tab needs adapting (we will probably work with alert scripts just 
like mon scripts + an option to use knotify - maybe as an always-existing 
"knotify" available action, so the "paging" stuff shouldn't be hardcoded in 
the GUI). 
i'm not sure if its a good idea to split it out to a new widget, it seems i'td 
fit well in the global settings (we shouldn't have a ton of different 
settings menu entries too)

"service objects" hmm, well, we used to call it "roles" :). and my previous 
remarks are valid here (about not doing kmail-filter-dialog gui). we might 
split it out to a separate widget here, but there should be a central entry 
too (configure roles or something), because you don't always have to find an 
instance of a role in your list to configure the role.

"servers", well thats one we will split out since that will be the RMB config 
dialog (or at least part of) when you click on a server.

and another remark: you'd better use the qt designer layout features, because 
now your config dialogs won't work if i configure another fontsize. for a 
(bad :p) example see the old ui files.

and the mainwindow:
the bar with dismiss, exit kmon, i'd like to exchange for an xmlgui toolbar. i 
don't think you can do xmlgui stuff with qt designer, i'll ask on #kde-devel 
once.

> > - seems qt designer doesn't support kdialogbase. well no problem, we just
> > throw out the buttons (ok/apply/cancel) and make it a widget encapsulated
> > by a kdialogbase-descendant ?
>
> each configuration (tab) should be an idependet widget (am i repeating
> myself? ;)

the advantage of this is that we can reuse widgets: eg it makes sense to 
configure a role by right-clicking on a role instance and choose configure 
role, but also to do settings->configure roles and then choose the role.

its a bit like the konqueror settings dialog: you can choose settings->file 
types, or you can edit file types directly from various other places 
(kcontrol, konq in fm mode)

maybe we also should adapt the new-style config-dialog-UI (so no tabs but a 
kind of special listview with all the "tabs" in it, like almost every kde app 
now)


> > of hard to figure out when the last failure was when it says 344:23:12
>
> 344 years 23 days 12 hours
> hmmm, this host was started, ano domini 1659...
> ... it's ok to have an output simular to uptime(1)

brett probably meant 344 hours :)

> i'd propose a KMonNodeList class (simular to the KMonNotifierList...) it
> can be used to handle to subnodes inside a node and to handle the topnodes.
> perhaps it would be nice to have a global node list, containing one (and
> only one) pointer to each node, so check all, check down and check up could
> be implemented quite easy

i'm not sure we talk about the same thing here. but a kmonnodelist class is 
fine imo.

ok, i really have to do something for my thesis now..

greetings,
frank