[SHOWOFF] NoggitWin32/SDL

[Valium]

Frustrated by the lack of qt development, and in collaboration with my hatred of qt, I present a screenshot of a little something I'm working on.  No need for qt when we have native controls.  Not like anyone uses a mac anyways lolz.(Sorry guys, I just don't have one to develop on.  If anyone wants to donate one, I'll gladly get it compiling on osx.)

I still have to get the rest of the buttons in, and strip out the crappy SDL controls (which apparently, the reason for the switch to qt is because you have to manually draw all the controls with SDL, which we windows folks are cool with anyways, that's just common practice.)  In the end, I hope to have something that uhh... looks different but works pretty much the same?  Why am I doing this again?

[Steff]

Stupid decition and the reason i did not gave away SDL source.


Again wasted resources in somehting unneeded.
And people ask me why the wow szene dont work?

[Valium]

Well, you may call it stupid, and I'll accept that.

But I'll disagree on wasted resources.  I am at least doing something that I think will improve upon Noggit.  I simply don't see a need for qt.  
Honestly, what are the benefits of using qt with noggit?  What was so wrong with SDL that it needed to be replaced?  I think it is almost self evident from the lack of contributions to the repo that either qt is something that people find to difficult to deal with, or simply don't know how to use.  You have said that Noggit SDL 1.2 works fine, then why not build off of that?

I'm not asking these questions to troll, I'm asking because I don't know.

[schlumpf]

The lack of contributions is not caused by qt but rather a result of steff doing other things and me not caring anymore.
Reproducing the screenshot you made is a ten minute job on any windowing framework, no matter if cocoa, win32, qt, wx and most likely even ncurses. The problem noggit is having is not the UI being ugly, but rather the whole code being ugly. If you will continue your development, you will see  lot of places where the UI is just hacked onto existing code from wowmapviewer. Hacking win32 onto that will not improve anything.
Also, I'm on a mac and hate projects I maintained for multiple years to suddenly become platform specific, even disallowing myself to use them.

[Valium]

The lack of contributions is not caused by qt but rather a result of steff doing other things and me not caring anymore.

That I can understand.

Reproducing the screenshot you made is a ten minute job on any windowing framework, no matter if cocoa, win32, qt, wx and most likely even ncurses. The problem noggit is having is not the UI being ugly, but rather the whole code being ugly. If you will continue your development, you will see  lot of places where the UI is just hacked onto existing code from wowmapviewer. Hacking win32 onto that will not improve anything.

Possibly not, but then, I may be able to clean some of it up even.  The worst that can happen is I end up making a complete mess of it.

Also, I'm on a mac and hate projects I maintained for multiple years to suddenly become platform specific, even disallowing myself to use them.

 This I understand 100%.  My intent is not to make it platform specific at all.  My intent is to at the very least, clean up the UI.  There is the very real possibility that I'll have access to a mac and have it compiling on both.  Yes, I get that it means lots of extra time and code, particularly since it would mean dealing with completely seperate window managers.

Understand of course, that isn't meant to downplay any of the progress that has been made on noggit-qt, I've read the commit logs, it's some excellent work.  Also understand please that last year when I talked to steff and a couple others in IRC about how exactly it was that I managed to get the noggit-SDL source, I was asked not to share it or how I got it, and I have respected that request..  In the event that I thought I had something functional worth sharing, the only people I would be sending code to would be Steff, or you, if you wanted it.

To tell the truth, II'm not even super attached to the Win32 part of it.  And it would probably be a hell of a lot easier just to make the changes in the existing code, a route that I just may take in fact.  I don't know yet.

I'm just trying to make the project better in the ways I think it could be improved, by doing the things I can.  This is just a hobby for me, I do it because I enjoy it.

[schlumpf]

Just work on the Qt version. Really. Nothing else makes sense at all.

[Steff]

Or if you wan to contribute join cromons SharpWoW Its in c# and only windows. And much cleaner code base.

[detonatorss]

i have a little question can you help me i know how to compile the noggit but where i have to put the boostht? i am really angry with the shit of the cmake

[Valium]

i have a little question can you help me i know how to compile the noggit but where i have to put the boostht? i am really angry with the shit of the cmake

What revision are you trying to compile?

I had to put the boost include directory in manually.


I woke up this morning and realized that while an interesting excursion, doing the win32 stuff really is pointless.  not much to be achieved there.

So I'm currently compiling the latest qt revision, hoping for good things.

***Compile is done, now which of the qt dlls should I copy over?  <-- Nevermind.

Hmm, having a bit of a issue on startup, I hope its not due to debug version.

[detonatorss]

no the little problem, is the boost i don't know how to define the path, can you help me?

[Valium]

no the little problem, is the boost i don't know how to define the path, can you help me?

Make a new thread for this please.