document updated 15 years ago, on Nov 25, 2008
Generally, it the current author has written quite a useful back-end, it generates lots of good data. However, the UI front-end seems to be sorely lacking. It's just begging for someone else to focus on the UI and other user-friendly stuff.
Documentation
- Explain in detail what packet information is stored in memory, and for how long. Particularly target this to users who want a light-weight application, and once they see all the things this app can do, start to worry that this might not be the app for them. (so, at the same time, explain why it's valuable to use memory)
[1]
UI
- auto-refresh! Why do you have to click the friggin' button to refresh?? Surely I'm misunderstanding something?
- be able to display some of the inner details in custom columns on the main view. This app generates a lot of data, so a custom column setup may be warranted. (personally, I want: "# bytes sent", ...)
UI preferences
- Be able to turn some of the memory-hogging features off! Some users will want to allow it to scan for long periods of time, or use it on skimpy machines.
- Remember the main sort setting
- Remember the keyword search?
Other
- It's too bad it wasn't designed to be portable from the start. Its primary dependencies are 1) UI code, 2) a read-only libpcap, and both are easily portable. But it's written in C#, so this probably isn't possible without a rewrite.