Thread: Support for Outlook?

Hey Andrew,

I love the idea. I wouldn't probably use it that much but it is nice to have the expandability options.

I would use the contacts as destinations at times. Keep up the good work

Cheers

Not that my opinion matters too much, but as I already discussed with Satish, it's hard to imagine this feature being high up on the priority list. I have access to most of the MS software, but don't have a reason to use Outlook at home. I'm wondering what value this feature would be to most of the VOICES target user base?

Does anyone think that the ability to import address book (contacts) information from a text file might be a better/cleaner option than direct synchronization with the Outlook PAB? Moreover, do you really want the heavy weight collaboration data objects (CDO) or MAPI code integrated into VOICES? Will coding this up ultimately require Outlook to reside on the carpc (ewwww) as well?

Just my off the cuff comments. Feel free to kick me around if needed.

The plan is not to tie in the synchronisation part as there are plenty of third party bits out there. Besides some people would want to Sync with a PDA, others PC to PC over wireless LAN.

If you want to import from a text file, then write a CSV to Outlook / PAB tool.

The Outlook object would be low impact and yes Outlook would need to be on the CarPC. Rando, what is your issue with Outlook being on CarPC?

Andrew

I think his problem is that he thinks that this should be last on the priority. i.e. dvd/radio/gps/viz/voice control/external appz should be priority.

I would have to agree with this although i would like the feature

I agree, unless as is being discussed in this thread Proposed open-source project - comments please :-) things are open source. This would allow people to add what they want to add. A high priority for person is a low priority to others. Software being Open Source enables everyone to manage their own priorities. It also enables faster development.

My primary issue with Outlook on the carPC is one of resources. Outlook is a heavy weight (read that: resource hog) desktop user application. The typical carpc is resource limited when compared to a typical desktop PC (less processing power, less RAM). The majority of Outlook's features serve little to no purpose on the typical (non network connected) carPC. Outlook is expensive and requires a license. Many (if not most) carpc users do not use Outlook nor own a licensed copy of Outlook.

If a list of names and addresses is the real feature you desire, this can be implemented in a manner that would consume substantially fewer resources than using Outlook. The implementation complexity is probably roughly the same. Morevoer, compatibility with Outlook could still be preserved, if desired.

Last, but not least, is the point that antimatter raised above. Given the roots of VOICES in dashPC, one might assume the priorities are as such.

1) Rock solid GPS support with voice navigation, voice recognition, auto route correction, ..... (insert your navigation wishlist here), and a user interface tailored to touch screen, voice, and/or other typical carpc input devices.
2) Tightly integrated music playback (Radio, MP3...) that works seamlessly with the GPS system
3) Ability to disable features in 4-6 while vehicle is in motion based on external sensor/switch/etc (i.e. parking brake, gear shift position, ...)
4) Video, DVD, TV Tuning playback
5) External applications / Games
6) Visualizations, Skins, other UI enhancements, Import/Expot with other apps, PDA functions, Web browsing, OBD integration, etc.

Obviosly, there are other valid orderings of the priorities. This is (again) just my off the cuff idea of how to go about building VOICES.

Again, as I've mentioned: Software being Open Source enables everyone to manage their own priorities. It also enables faster development.

Originally Posted by skippy76

I agree, unless as is being discussed in this thread Proposed open-source project - comments please :-) things are open source. This would allow people to add what they want to add. A high priority for person is a low priority to others. Software being Open Source enables everyone to manage their own priorities. It also enables faster development.

Open source or not, the project will benefit from prioritization. And I'm not saying there aren't any priorities with VOICES or even that the priorities are wrong. I was just suprised to learn that Outlook integration is a priorty and feel that Outlook integration is an 'interesting' design decision.

Also, unless I missed something, VOICES is not open source, right?