CompuServe Messages

>> plug-in's which allow smaller third parties to extend the package way >> beyond the cabability of the original authors. While that's obviously true, and I'm extremely *for* it, I can also understand that it's a huge undertaking to develop a 3D plug-in SDK. There's also the issue that everybody out there pretty much has their own method of doing it. It is kind of messy now, for developers to write for one type now (mostly IPAS), then convert to a totally different method. The best way would to make sure you take the time and develop a platform that would make the lives of 3rd party developers extremely easy in a porting situation.. In other words, do some up-front research and see what it is that they use in the most common SDK's, and what they would also like to see in the future that's not there now. This will pretty much guarantee that all of the existing cool tools is ported as fast as possible. (Believe me, they'd love to leverage what they've already written on another platform!) Otherwise, you'll "hurry" to develop an SDK that will hardly be used, or just make it longer before anyone can actually release anything.. That's the way I see it, and I know first hand that's how a lot of 3rd party plug-in developers see it today.. <$.02>