- adds a nice and well formated dialog, which displays our -? help message (all options/paramaters)
- moves aboutdialog.cpp/h to the new utilitydialog
- move GUI shutdown window to utilitydialog


Dialog looks good.
I'm thinking that we should maybe have a implementation/header file dedicated to 'utility dialogs' such as this one and the about box. I don't really like how this one is almost empty, for example:
https://github.com/bitcoin/bitcoin/blob/master/src/qt/aboutdialog.cpp
Edit: Another one we could throw in that bag would be the "Shutting down dialog". It's currently declared on-the-fly in bitcoin.cpp.
I just mean 'move them to one implementation file'. It doesn't have to be one class. You can easily do that in this pull.
Oh I missunderstood that, sure that can be easily done ^^.
@laanwj Let's see what you and @BitcoinPullTester says.
One thing I observed, when shutdown is taking longer and you see the Shutdown window. I was able to double-click on the tray icon and saw the no-wallet UI (perhaps the wallet was unloaded already). Is this intended @laanwj? I'm also not sure this has to do with this pull, just mentioning.
@Diapolo that's indeed strange, but has nothing to do with this pull, it's now possible to trigger this because the event loop is functional during shutdown.
Edit: a way to prevent this would be to delete the main window in initiateShutdown. This removes the tray icon during shutdown. Edit.2: or another way to disable all the tray menu actions in setClientModel(0), maybe this is better, as the tray icon can stay visible until the program has really quit.
- adds a nice and well formated dialog, which displays our -? help message
(all options/paramaters)
- moves aboutdialog.cpp/h to the new utilitydialog
- move GUI shutdown window to utilitydialog
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/7b50bb2f1b96cb8964819e03eb044c3b88746946 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
If you forget files in the makefile.am they will not make it into 'make dist' and the pull tester will fail (good test!), that also tripped me up once.
ACK
Now that you created a nice window for this, what about moving it to "Help"->"Command-line options" instead of the debug window?
Good idea, will create a pull...