2
« on: March 21, 2013, 11:11:32 pm »
I was able to get it to compile and run in Mountain Lion a few weeks ago but I gave up. I'm no programmer but the current source code makes vague references to the OSX version (probably because it's a fork of a project that did have OSX support). I was able to get it to run by commenting out certain lines and editing others. I realize this isn't helpful, but I wasn't able to get it to actually do anything useful. I could get it to run, but clicking Connect to DF didn't actually do it. It didn't error out, it just wouldn't connect or load the dwarves.
The whole process was beyond my understanding so there's nothing worth reporting from it other than it's possible to toy with it and get it to run in Mountain Lion, but that's not new information. Previous projects would compile and run so it doesn't surprise me that this fork will. It doesn't really do anything useful, though, and I am incapable of really producing anything meaningful. I'm not a programmer, as I said.
Anyway, the lack of Mac OS support in Dwarf Therapist, in general, can be traced back to an inability to access/modify the memory addresses in question. This specifically pops up when dealing with setting custom professions. It doesn't surprise me that the newest enhancements are available mostly for Windows. What's surprising is that Linux-based systems are getting these new versions of DT because Mac OS X is also a Unix-like system. The fact that there's no steam behind getting this going on Mac OS is surprising, considering the number of Mac OS users nowadays and how similar it is to other Unix-like systems. This isn't a Splinterz issue, though. DT for Mac OS has been broken for a while now. It's just surprising that among all of the Mac OS players, there's no one familiar enough to solve this.
Please don't get me wrong -- I don't like complainers who won't/can't step up and try to offer solutions. I realize that's what I'm doing now. But, I did fire up Xcode and QTCreator. I did try to step through the source code and get this going. However, I'm not a programmer and the solution for this is well beyond me. I'm just surprised that there aren't seasoned programmers who are also Mac users. Me not fixing this should come as no shock, but there must be people familiar with programming and Mac OS who could fix this. Splinterz is doing great work with this, but if he or she is more comfortable developing for Windows, that's fine. This is a free project and no one is in a position to make demands beyond what a person is comfortable offering.
