|
Hey, we hear you all loud and clear on this topic. And as a fellow end-user, I agree. In a perfect world, we would be all over upgrading the Nav engine to something better, newer, etc.
But when reality sets in, these Nav companies either don't have a Win32 (XP, Vista) SDK, aren't eager to jump into this market yet, OR a combination of the above.
So to address this issue, we've shifted our strategy to a MUCH more open framework using what are called "open interfaces" (development term) that essentially means that when these SDK's become available, and/or we (or any developer or company's development teams) are in a position to implement them, then the work will be much easier, and these open interfaces facilitate that effort in a much more seamless manner, meaning we don't have make any changes to our "core" to support them.
In 3.0 we've done the same for Bluetooth, Audio Mixer, and Speech (both SR and TTS).
Not the short-term answer some of you want, but we think this strategy is best in the long term for the customer and the industry as a whole.
|