Comment # 5
on bug 9820
from Guy Harris
(In reply to comment #3)
> I think instead of hard-coding yet another graph, it would be better if we
> allowed people to define their own graph inputs and calcs - similar to how
> the IO graph lets one define different input calculations. But the IO one
> appears to be specific to IO-type graphing, because the X-axis is fixed to
> be time-based, and the Y-axis is basically just a count of user-defined
> values, afaik.
>
> It's no surprise I'm going to say this: we could do this using Lua, where we
> either (a) hard-code another graph dialog but allow Lua to provide a bunch
> of its stuff, or (b) expose the drawing/widget objects of Qt to Lua
> altogether. Option (b) has been done in other Qt-based projects, and is far
> more flexible of course.
Yes, although if the user is writing Wireshark GUI code in Lua, that's useful
for some but probably too big a hill to climb for others.
Something that lets users specify formulae using named fields as variables
would be sufficient, and easier to use, for many users.
Some flavor of (a) would probably be easier to use than (b) for the cases it
handles (no need to write your own graph-drawing code), and add the ability to
handle cases where the graph needs to, for example, maintain some form of
state.
(b) would be a useful extension to let arbitrary things be done in Lua; perhaps
(a) and the graph-with-formulae could be implemented atop it.
You are receiving this mail because:
- You are watching all bug changes.