Contributions
I think that if anyone would like to contribute to the dink source, they should say what they're going to do here. For example:
"I can improve upon graphics support."
"I can improve upon graphics support."
I suggest we follow Nexis' advice and first prepare Dink for a good work: clean code, and make it portable. I think I can do that, and I will trying to do that in a easier case first: WinDinkEdit (since I am the new maintainer
)
Then, telling what each people do requires we first build a solid todo list...

Then, telling what each people do requires we first build a solid todo list...
Yeah, I might be able to do something as well; making the code more readable, internal stuff, some of those things on the wishlist et cetera.
i have a firm grasp of the c++ language now, so i think i'll be able to do just about anything that needs to be done to help, but the main thing i was wanting to work on was with commands in dinkc