Feature request - "loaded via URL" should show full URL about qvis HOT 2 OPEN

Hello Andy,

Sorry for the late reply, though I did see the issue earlier.

Showing full .qlog links is a good feature that shouldn't be too much work to add.

There are some caveats here though, in that it's more difficult if the user didn't pass in a .qlog directly (e.g., do we link to the passed-in .pcap file? What about the .keys file then?). Ideally, I'd store the qlog on the server and let people link to that, but I'm not sure I want to offer that service as part of qvis... Similar questions can be asked when passing multiple qlog files at once.

So I'll probably add the simplest case soon (if you passed in a .qlog URL, you'll get to extract that easily) and keep the rest for later.

I will also look into the "jump to a specific part of the sequence diagram via the URL" concept, which is something I'd considered before and agree would be very useful.

from qvis.

Hello Andy,

I have updated qvis to hopefully fix most of the issue for you.

Firstly, if the qlog was loaded from a URL directly, the URL is now click-able in the sequence diagram (should be underlined and clickable on top of the vertical timelines). This works for 2 sides separately (client vs server) if both were loaded from a URL individually).

Secondly, if you now click on an event in the sequence diagram to get the popup with extra qlog details (so click on one of the colored squares for example), there should now be a link on top that you can copy. This link should open qvis directly with the given trace and scroll automatically to the specified event. An example of such a link (which should scroll all the way down to packet 367) is: https://qvis.edm.uhasselt.be/?#/sequence?file=https://qlog.edm.uhasselt.be/anrw/files/examples/figure2_c.qlog&focusOnConnection=0&focusOnEvent=5869

For this second part there are some caveats though:

1. only works if the trace was loaded via a URL
2. it doesn't highlight or indicate the chosen event directly, it just makes sure it's "on screen". I guess that's ok for most purposes, so let me know what a better UX solution would be for this if not.
3. if you've loaded 2 traces separately, this will generate a single link that combines them + also scrolls to the correct event. However, due to another bug in qlog, you need to manually select the server-side trace (currently, it auto-generates another viewpoint from the client trace). Fill file this as a separate bug after this post.

Please try it out and let me know if you'd like changes!

from qvis.