Comment # 7
on bug 10488
from Guy Harris
(In reply to Michal Labedzki from comment #6)
> Do not worry. I am spend five minutes a week looking for possibility to add
> tabs
Note that we already have multiple tabs in the main window, for "data sources"
such as the current packet, reassembled packets, decrypted/decompressed data,
etc..
Will the UI be cluttered if it has multiple tab headings?
> Do not worry Guy, there will be special "checkbox" for you to use multiple
> instances
By "instances" you mean "windows", correct?
The user should be able to open a new capture file, in a separate window,
within the *same* instance of the application, if they are given the ability to
open a new capture file in a separate tab of the existing window.
And this should ***NOT*** be governed by a preference.
On OS X, and KDE 4, applications that support multiple tabs offer "New Window"
and "New Tab" menu items under "File" (tested with the "vendor" Web browser -
Safari/Konqueror - and the "vendor" terminal emulator - Terminal/Konsole - and
with Chrome on OS X). The same is the case with IE 11 on Windows.
We should ***NOT*** invent a new way to choose between "open in a new window"
and "open in a new tab".
> per sigle file/interface (my case is use multiple Wireshark
> instances with mutiple tabs [like Firefox, Kate editor]).
Do ***NOT*** use Kate as an example of how to develop a UI for applications in
which one instance can have multiple files open. It is a truly ***HORRIBLE***
example of how to do that - it doesn't even show tab headers by default, it
just shows *one* file open, with "Back" and "Forward" arrows to move between
files.
You are receiving this mail because:
- You are watching all bug changes.