{"id":243,"date":"2006-05-29T09:12:39","date_gmt":"2006-05-28T22:12:39","guid":{"rendered":"http:\/\/www.somethinkodd.com\/oddthinking\/2006\/05\/29\/samsung-pc-studio-3-versus-microsoft-outlook\/"},"modified":"2007-09-10T18:40:42","modified_gmt":"2007-09-10T08:40:42","slug":"samsung-pc-studio-3-versus-microsoft-outlook","status":"publish","type":"post","link":"https:\/\/www.somethinkodd.com\/oddthinking\/2006\/05\/29\/samsung-pc-studio-3-versus-microsoft-outlook\/","title":{"rendered":"Samsung PC Studio 3 versus Microsoft Outlook"},"content":{"rendered":"
In a previous post, I did a review of the Samsung D600<\/a>. One of my major complaints was about the Windows software used to talk to the phone, called Samsung PC Studio 3. In this article I get a lot more detailed about one key aspect of its brokenness.<\/div>\n

I’ve have been doing some forensic analysis of Samsung’s PC Studio 3 to work out why it sucks so very badly when synching my Outlook 2003 calendar and my Samsung D600.<\/p>\n

I put aside the issues of the frequent crashes, the frequent inability to recognise the phone is connected and the duplicate contact problems (which largely seem to have settled down). Instead I focussed on why Outlook claims I have a busy day of meetings while my phone claims my day is free of any plans.<\/p>\n

D600 Model of my Calendar<\/h3>\n

First, let’s understand the phone’s model of my calendar.<\/p>\n

The phone has three different types of “events”. The following table lists their corresponding fields.<\/p>\n\n\n\n\n\n
Type<\/th>\nSubject1<\/sup><\/th>\nDetails2<\/sup><\/th>\nStart<\/th>\nEnd<\/th>\nLocation<\/th>\nAlarm<\/th>\nRecur: Never<\/th>\nRecur: Daily<\/th>\nRecur: Monthly<\/th>\nRecur: Yearly<\/th>\n<\/tr>\n
Appointment<\/th>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n <\/td>\n<\/tr>\n
Miscellaneous<\/th>\n•<\/td>\n•<\/td>\n•<\/td>\n•<\/td>\n <\/td>\n•<\/td>\n•<\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n
Anniversary<\/th>\n <\/td>\n•3<\/sup><\/td>\n•4<\/sup><\/td>\n <\/td>\n <\/td>\n•5<\/sup><\/td>\n•<\/td>\n <\/td>\n <\/td>\n•<\/td>\n<\/tr>\n<\/table>\n

Footnotes<\/strong><\/p>\n

1<\/sup> Subject field is limited to 14 characters.<\/p>\n

2<\/sup> Details field is limited to 100 characters.<\/p>\n

3<\/sup> Field is displayed as ‘Occasion’.<\/p>\n

4<\/sup> Start limited to date, not date and time.<\/p>\n

5<\/sup> Alarm reminder set as absolute time of day, rather than relative to start time.<\/p>\n

It can be seen from the table above, that the Daily, Weekly and Monthly recurring Appointments are scheduled to end on a set date. The yearly recurrences (i.e. Anniversaries) are left open to continue forever.<\/p>\n

The D600’s universe starts on Jan 1, 2000, and finishes sometime in 2098.<\/p>\n

I have learned about this model by playing with the user interfaces to the phone and the PC Studio 3. It is possible that there are other constraints underneath the hood.<\/p>\n

Outlook Model of my Calendar<\/h3>\n

Outlook has a far more sophisticated model of a calendar<\/a>.<\/p>\n

Outlook’s UI pretends to have a number of different objects – Appointments, All-Day Events, Meetings, Recurring Appointment, Recurring Events and Recurring Meetings – but these are all unified into one type, Appointment<\/a>, in the underlying data model.<\/p>\n

Each appointment has access to all of the recurrence options of the D600 Appointments and Anniversaries – e.g. Daily, Weekly, Monthly and Yearly – but they also have access to more powerful options. They can recur every n<\/em> weeks. They can recur weekly on a “day mask” – e..g every weekday, or every Monday and<\/em> Wednesday. They can recur on a given day of a given week of each month (e.g. last Friday of the month). They can also recur on a given day of a given week of a given month each year (e.g. third Saturday in June).<\/p>\n

Unlike the D600, Outlook allows all recurring frequencies to continue forever, or to stop at a certain end date. (Outlook also supports setting the count of the number of reccurrences, but that is merely a convenient way to set the end-date rather than indicative a more powerful calendar model.)<\/p>\n

Another major difference between the naive D600 model and the more sophisticated Outlook model is that Outlook Appointments supports “Exceptions<\/a>” to recurring Appointments. Exceptions occur when the regularly scheduled Appointment is modified only for a particular date. Outlook allows a set of Exception objects to be associated with an Appointment. Each Exception contains the (original) date of the scheduled meeting, and the new details for the appointment on that day.<\/p>\n

Outlook supports Location information on all Appointments.<\/p>\n

Ignored Details<\/h3>\n

Both Outlook and the D600 have a number of other items, which I have elected to ignore because they aren’t causing me direct grief at the moment. Some of the more obvious items are listed below.<\/p>\n\n\n\n\n\n\n\n\n\n\n
D600 Item<\/th>\nOutlook Item<\/th>\n<\/tr>\n
To-do item<\/td>\nTask<\/td>\n<\/tr>\n
Phonebook<\/td>\nContact<\/td>\n<\/tr>\n
Email<\/td>\nMail<\/td>\n<\/tr>\n
SMS<\/td>\n <\/td>\n<\/tr>\n
Memo<\/td>\nNote<\/td>\n<\/tr>\n
 <\/td>\nDistribution List<\/td>\n<\/tr>\n
 <\/td>\nJournal<\/td>\n<\/tr>\n
 <\/td>\nPost<\/td>\n<\/tr>\n<\/table>\n

Mapping Difficulties<\/h3>\n

A sync program, like PC Studio 3, has its work cut out for it. It needs to “paper over the cracks” caused by the differences between these two models of the calendar, and allow synchronisation of appointments in both directions.<\/p>\n

The D600 model is much more naive than the Outlook model, so going from D600 to Outlook is fairly straightforward, but the other direction is tricky.<\/p>\n

Here are some of examples of Outlook appointments that the phone cannot natively support:<\/p>\n