[tkined] tkined future development

John Stumbles (J.D.Stumbles@reading.ac.uk)
Fri, 3 Jul 1998 20:21:19 +0100 (BST)

In an earlier message I wondered aloud whether tkined development was
frozen. I then found myself drifting into "wouldn't-it-be-nice"-land so I
decided to put this in a separate message ....

---

What is happening to tkined generally?

The more I use it and find out about it, the more I like it as a tool for investigating and monitoring the network. I'm not familiar enough with it to see clearly how it's structured and everything it can do so I'm probably missing stuff that's already there, but here are some suggestions for how it might develop:

- separate monitoring from display, so tkineds are displays of views of the underlying monitoring/data collection processes. Other 'displays' could include report generators, pagers for alarms etc. Monitoring and colection carries on even if no displays are open. With .xbm -> .gif conversion one could think of easily using tkined to draw a network map which can be exported to a www page, with the web map following the status of the nodes being monitored (red = down). This could give an easy read-only display mechanism useful where you want e.g. users, advisors to have access to network status pictures but only network managers (using tkined) to change maps.

- extensible toolset for troubleshooting. (It probably already is extensible and I just haven't learned how to do it yet!) i.e. so when you right-click on a node and get a menu one option is e.g. for a webserver to fire up a browser at it; or for a network device to run its manager application (assuming it can run on or be launched from the same platform as tkined).

- better way of managing tkined window space: it would be nice if I could define parts of the canvas (like browser frames) so that when I, say, expand a group or discover a network, the expanded or discovered map appears in a separate area to my main map, and selecting icons is confined to the scope of that window. (I guess this is either trivially easy or wickedly difficult to do in Tk - I know to little to know which!)

- better documentation e.g. extension of Mark Newham's Getting Started doc. (Maybe I'll have a crack at that - once I've got familiar with all that's in there at present!)

regards,

--
John Stumbles                                      j.d.stumbles@reading.ac.uk
Computer Services, University of Reading       http://www.rdg.ac.uk/~suqstmbl 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       If a job's worth doing, it'll still be worth doing tomorrow.

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.