Reply to Re: Windemere, dead or living...
If you don't have an account, just leave the password field blank.
You thought wrong. I said exactly this:
It seems that, with the current progress, I will be unable to continue developing Windemere. So, I will be doing one of these things:
1) Starting over by myself doing things my way.
2) Waiting for another developer to help with my self-esteem and motivation issues.
3) Some of the above.
4) All of the above.
This does not leave reason for anybody who still cares to panic that development will cease entirely. It just means that, until something happens, I will continue being a depressed maniac with no [social] life. If anyone cares enough to try to cheer me up (yeah, right, I know), you know my IM. No? Well you should: it's in my profile.
I started number 1 and am quite far. The engine is already better than that it was and I don't have to wait several hours to discuss an idea with someone else. It not only progresses much faster because of this reason, but because of the fact that I've pretty much dumped backward compatibility. I just can't do very much with Seth's limitations. Yes, the new DinkC++ will not be exactly the same, but no, it will not be hard to learn the new things. It will be C-based. I don't know why I immediately think about DinkC++, but oh well.
And I really don't care if you're a fan of this idea or not. It will be finished.
It seems that, with the current progress, I will be unable to continue developing Windemere. So, I will be doing one of these things:
1) Starting over by myself doing things my way.
2) Waiting for another developer to help with my self-esteem and motivation issues.
3) Some of the above.
4) All of the above.
This does not leave reason for anybody who still cares to panic that development will cease entirely. It just means that, until something happens, I will continue being a depressed maniac with no [social] life. If anyone cares enough to try to cheer me up (yeah, right, I know), you know my IM. No? Well you should: it's in my profile.
I started number 1 and am quite far. The engine is already better than that it was and I don't have to wait several hours to discuss an idea with someone else. It not only progresses much faster because of this reason, but because of the fact that I've pretty much dumped backward compatibility. I just can't do very much with Seth's limitations. Yes, the new DinkC++ will not be exactly the same, but no, it will not be hard to learn the new things. It will be C-based. I don't know why I immediately think about DinkC++, but oh well.
And I really don't care if you're a fan of this idea or not. It will be finished.
