diff options
author | Gerald Combs <gerald@wireshark.org> | 2013-07-25 23:49:47 +0000 |
---|---|---|
committer | Gerald Combs <gerald@wireshark.org> | 2013-07-25 23:49:47 +0000 |
commit | a05f55bffc2bc7d52d3f35370a7ae1eea2b75839 (patch) | |
tree | 94644ff0a3cc6cf339a165087ddbfb0c1e553760 /doc | |
parent | 7d73903af6209ef1b013c6ed61c866291bfb3785 (diff) |
Add a UAT dialog. Make UAT preferences uat_t * instead of void *.
C++-ize the UAT headers.
Add an ElidedLabel widget. Use it in the File Set, Profile, and UAT
dialogs.
Update the Qt README.
svn path=/trunk/; revision=50896
Diffstat (limited to 'doc')
-rw-r--r-- | doc/README.qt | 26 |
1 files changed, 14 insertions, 12 deletions
diff --git a/doc/README.qt b/doc/README.qt index 6046b91e75..1c57c5a1d1 100644 --- a/doc/README.qt +++ b/doc/README.qt @@ -10,10 +10,10 @@ and let us add features more easily. 1. Getting up and running -The Qt interface for Wireshark has been compiled and tested on Mac OS X 10.6 -(XCode gcc), Windows 7 x86 (Visual C++ 2010), and Ubuntu 10.04 (gcc). -Compilation via Qt Creator has been tested but command-line compilation using -QMake and make or nmake should work. +The Qt interface for Wireshark has been compiled and tested on Mac OS X 10.8 +(XCode LLVM/clang), Windows 7 x86 (Visual C++ 2010), and Ubuntu 12.04 (gcc). +Compilation via Qt Creator and via the command line compilation using QMake and +make or nmake should work. There are several ways of building qtshark: @@ -69,10 +69,10 @@ This may or may not work for you; see 1.1.2 Windows -The default Qt SDK libraries are built using MinGW, which isn't supported -for Wireshark. Instead of downloading the Qt SDK all-in-one package, -download the Qt Libraries package from http://qt.nokia.com/downloads/ that -matches your compiler (VS 2008 or VS 2010) and Qt Creator for Windows. +The default Qt SDK libraries are built using MinGW, which isn't supported for +Wireshark. Instead of downloading the Qt SDK all-in-one package, download the Qt +Libraries package from http://qt-project.org/downloads/ that matches your +compiler (VS 2010 or VS 2012) and Qt Creator for Windows. Settings in config.nmake are passed to the Qt environment via ui/qt/config.pri. This file should be created automatically when you @@ -137,11 +137,10 @@ XXX: (WMeier): I've not had too much satisfaction using the "native Windows debu 1.1.3 Linux Install the Qt libraries and Qt Creator via your package manager or from -http://qt.nokia.com/downloads/. On Debian and Ubuntu the "qt-sdk" meta-package +http://qt-project.org/downloads/. On Debian and Ubuntu the "qt-sdk" meta-package should provide everything you need. Build the top-level directory using CMake -(see section "Using cmake" above). -As an alternative do an in-tree build without QT and then inside ui/qt/ do -"qtcreate QtShark.pro". +(see section "Using cmake" above). As an alternative do an in-tree build without +QT and then inside ui/qt/ do "qtcreate QtShark.pro". 2. Going forward @@ -158,6 +157,9 @@ HTTP request statistics? - "Go to packet" pops up a text entry in the main window instead of a separate dialog. +- Preferences are complete, and are arguably more useful than the GTK+ version. + An "Advanced" preference pane exists, which lets you edit everything. They use + the proper menu placement and keyboard shortcut on OS X. 3. Translations (i18n) For make your own translation of QtShark ! it is easy ! |