what i mean is... the was specifically a VB6 project for direct x 8.1 ... it stands to reason that people using VB6 wont be using .NET, so by switching to .NET, it kind of excludes all previous vb6 developers. what i was suggesting was, fork the project, and have two. the vb6-directX8 (this one) and the directX9-.NET project. if the interfaces were kept in synch, then when people want to move from vb6 to .net, their codebase can stay the same.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't plan to move to .NET - have you read Microsoft's licensing recently? Not just on .NET, but their OS's - they say they can download/update anything they want on a given machine. I'm boycotting .NET because they want to claim control of my machine and possibly prevent me from accessing my own data. This language is in the Win2K SP4 licensing as well, so I'm sticking with SP3 on my home PC.
I don't want the project to fork, because one can't serve two masters - either he will cleave to the one and despise the other, or (etc...)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd be interested in finding out if a) anyone reads this and b) who would prefer this project to fork?
I for one (currently) arent interested in .NET development. anyone willing to discuss?
I read this. I don't know why this project should be abandoned, just because you're not interested in it doesn't mean others aren't.
what i mean is... the was specifically a VB6 project for direct x 8.1 ... it stands to reason that people using VB6 wont be using .NET, so by switching to .NET, it kind of excludes all previous vb6 developers. what i was suggesting was, fork the project, and have two. the vb6-directX8 (this one) and the directX9-.NET project. if the interfaces were kept in synch, then when people want to move from vb6 to .net, their codebase can stay the same.
or.. keep them together, in the one project, separate binaries/projects then you get two tools for the interface of one. magical.
I don't plan to move to .NET - have you read Microsoft's licensing recently? Not just on .NET, but their OS's - they say they can download/update anything they want on a given machine. I'm boycotting .NET because they want to claim control of my machine and possibly prevent me from accessing my own data. This language is in the Win2K SP4 licensing as well, so I'm sticking with SP3 on my home PC.
I don't want the project to fork, because one can't serve two masters - either he will cleave to the one and despise the other, or (etc...)