Re: NessusClient: Planned improvements (monitor dialog)

"Jan-Oliver Wagner" <[email protected]> Fri, 20 Apr 2007 00:10:10 +0200
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
On Tuesday 17 April 2007 02:02, Renaud Deraison wrote:
> On Apr 16, 2007, at 7:54 PM, Jan-Oliver Wagner wrote:
> > On Sunday 15 April 2007 20:17, Renaud Deraison wrote:
> >> No. I'm not sure I understand the benefits of changing something
> >> which is working fine today by something else whose design has not
> >> even been finalized yet -- if it's not broken, don't fix it.
> >
> > it is not broken. But it can be improved (my patch it is not just a
> > fix).
> >
> > And it is not finalized because you asked for some details,
> > so I just send the current status (clearly marked as such)
> > of my work.
>
> I'm not opposed to it, but let's define a final design before
> anything is done -- you talk about tree view and I don't see where
> you want to fit them, etc...

a GTK TreeView can have a list or a tree model.
=46or a first step I planned to use a list model for the monitor dialog.
Eventually a tree model could be used. But that's beyond the currently
implemented concept and I could imagine different ways how
this might work. Probably it is best to ask for some user feedback before=20
beginning to plan this.

However, even with a list model, the TreeView has some advantages over
the current implementation:

=2D not using deprecated methods anymore
=2D clearer code due to MVC
=2D progress bar additionally shows %tage
=2D vertical space consumption much lower
=2D personal opinion: looks nicer (more modern)
=2D sortable columns (not yet used in my code. Should I implement
  that clicking on a head line makes this the sorted column,
  a second click make it sorted reversed? This would be a pretty
  common behaviour today in many GUIs.)

Except for the the sortable-question my sample already shows
the final (list) design. Some beautification remains of course=20
and the old widget needs to be removed, naturally.

I do not expect instability due to my changes because actually
the same hooks for communication with Nessus Server are
just called in a different way.

Best

	Jan
=2D-=20
Dr. Jan-Oliver Wagner                                   Intevation GmbH
Amtsgericht Osnabr=FCck, HR B 18998             http://www.intevation.de/
Gesch=E4ftsf=FChrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel