(09-19-2014, 11:22 AM)MaJoR Wrote: [ -> ]Thethiala: by getting rid of the much hated WX and moving to Qt, we might actually get some interface work from time to time since it won't be such a pain in the ass to work with!
As a Qt (pronounced cute for those who don't know) developer myself, Qt will definitely be a welcome addition to the Dolphin codebase imho, for one thing, since Qt has native Android support, unification of the GUI is entirely possible. The only potential problem in that regard is that the Android version requires QML, which honestly isn't that much of a downside really. QML is really intuitively put together and is rather trivial to learn. I'll probably wind up pushing a few PRs to the Qt submodule myself in the future.
The submodule is used to provide dependencies so that you don't have to install the Qt SDK to build dolphin (unless you want to).
If you are a Qt developer, dolphin is already set up to start developing for...just check out the repository and get hacking on
DolphinQt 
(09-19-2014, 11:22 AM)MaJoR Wrote: [ -> ]Thethiala: by getting rid of the much hated WX and moving to Qt, we might actually get some interface work from time to time since it won't be such a pain in the ass to work with!
Actually I'm pretty sure all this effort is just so shuffle2 has an excuse to keep using his "cute dolphin" avatar without people thinking he's strange.
I had to update the submodule and rebuild the DolphinQt project, but now it's working.
Well done.
Nothing to see yet though except a menu bar and an about dialog, so I guess I don't have to worry about porting my VR options over yet. :-)
I'll definitely look into getting some work done on the GUI, I think the most important part right now is getting games running in it. The games browser can wait.
My only problem right now is the fact that I don't have ready access to windows (I'm running 7 in a VM), and absolutely no access to Mac.
The current DolphinQt code is tested to compile and run on OS X, linux, and windows. You don't need a VM.
(09-22-2014, 09:29 AM)shuffle2 Wrote: [ -> ]The current DolphinQt code is tested to compile and run on OS X, linux, and windows. You don't need a VM.
Yes, but I need to test MY code
That's what our buildbot system is for, also other developers on the team.
(As a Git/submodule/VS2013 novice) I'm getting an error when building the latest version on Windows.
It states Error 1 error : QTDIR not set or non-existent (pull the submodule?) C:\***edit***\dolphin\Source\VSProps\QtCompile.props 69 5 DolphinQt
I haven't been building for a couple of months and VS threw me a bunch of warnings at first. After
-updating to VS2013 update 4
-updating git submodules with the command "git submodule update"
the only remaining error is the one above, there are no performance warnings that were there earlier. The build runs fine, and fixing my settings might be trivial, but still... do I need to do some git magic with the Qt submodule or..?
If you still have the "pull the submodule" message it means you haven't pulled the submodule properly. You have to pull them with:
Code:
git submodule init
git submodule update