Manikus' Monks

[manikus]

Changing the race, baseclass and class files is similar to the config file, but easier. I haven't seen Steve McDonald around in a couple of months - he's usually on the Yahoo list anyways - but he had done quite a bit of work with these files for his Dragonlance project. I've just played around with naming conventions and seeing how DC handles stuff compared to what the code says.

I'm pretty sure if DC ever gets away from MFCs, I'll be able to help a little more in the coding department than I have in the past. Unfortunately, I've not been able to figure out any of the bugs, but I have gotten some pretty good ideas about a couple of feature requests. What I have no clue about coding are the special abilities. If I could figure those out even a little bit, I'd go to the trouble of tracking down the software I need and installing it just so I could get those done, well more correctly, help get those done (hopefully help get those done).

[SilentThief]

Yeah, its unfortunate that the MFCs are so difficult to get around. I mean, even in other OSs (like linux and the MacOS) there has been standardization for using graphic images and/or sound (as in IMH OPINION, a jpg or png should show up correrctly on a Mac or a linux machine as well as a windows machine, but again its opionion not fact or tested). But coding handlers for using these graphics and sound, as well as setting up the friggin' windows that displays the entire interface (design engine OR game) means that the MFCs are tied in. Modular design means that some of the code should be reusable, but I don't know anything about it

I still need to get some schooling before I can really do anything about it

ST

[manikus]

The jpg and png formats work well on linux and Mac. I have first hand experience using both on both.

There's modular and then there's modular. The whole notion of MFCs (or other libraries) is being modular. I mean, that's what object oriented programming is all about. As far as parts of the DC code being modular, i.e. reusable, with other libraries; all of the code relating to MFCs is not usable with other libraries, so everything related to how it looks will have to be rewritten. The other code may or may not be usable, I'm not the best judge, but I think a lot of it will be. Unfortunately 'a lot' of a third to a half is not a lot. But it is better than nothing.

[Uatu]

Hmm - maybe an "easy" way to replace MFCs would be to write functions with the same names and same functions to replace them?

[manikus]

I know you can't, but it wouldn't it be awesome if you could just a global replace, using SDL or gnulib in place of MFC?

[Uatu]

We can try it! As long as it sounds easier...

[manikus]

It doesn't work, though. You have to do different calls for different libraries, and things may have different names, etc.

[Uatu]

Well, it MIGHT work...

[manikus]

Feel free to try. I would love to be proved wrong.