Comments inline... On Wednesday 14 November 2007 12:25:32 pm John Carr wrote: > Wow, thanks for your thoughts! > > On Wed, 2007-11-14 at 12:05 -0500, Paul Stanisci wrote: > > John, > > > > A few more thoughts... > > > > I don't believe there is a place in the breakdown below for a > > compatability list. The current WM5 device list on the synce.org wiki > > mentiones only HTC devices. There are obviously more devices like the > > ipaq that can connect to synce. > > The compatibility list is a bad idea IMHO. OpenSync have ditched theirs > recently and I think we should too. If it supports ActiveSync then we > support it, if we don't its a bug. What i'm saying is, there is barely > no distinction between devices as far as our project is concerned and we > have more problems with localisation/language issues and distro issues > than we do with specific devices.
That makes good sense. I too figured most WM5 devices would be very similar. I guess the "Connecting Your Device" could state that most devices should be supported, and to file a bug with the pertinent device information if it doesn't work. > > > Also, under "Base Install", should a sub page be created to explain the > > difference between vdccm and odccm, and when to use each one? Should > > users of non-WM5 devices continue to use vdccm, or will it soon be > > deprecated? > > Unless someone steps forward, we'll only document odccm, which has a legacy > mode to support WM2003 users. We've considered it deprecated for some time > and will probably move it to legacy/ in svn for 0.11... > If odccm will handle WM2003 and WM5 users, I guess there is little point to document and maintain old version of dccm. Though, the documentation should state that old version of dccm exist and that the user should use odccm instead. > > Lastly, a summary should be created to explain from a high-level what's > > involved in syncing a WM device to the PC. It should quickly cover the > > entire process from requring one of the two kernel drivers, vdccm/odccm > > and some sync software. It would help new users to better understand the > > purpose of synce. and the other tools. > > This will require some thinkery. Specifically, the kernel and > dccm/vdccm/odccm foo isn't specific to syncing - its probably wrong to > document this as part of synchronisation. Perhaps a "stack overview" > page is called for, but i don't think that belongs as part of > installation. Perhaps a link in overview? Sorry, my terminology was obviously wrong. My main point here is that a brief summary should explain the purpose of synce in the grand scheme of things, and hint at what else the user will need to perform a sync with their device. This could be fairly short and may not warrant needing a whole page. Maybe this could be explained in a paragraph on the "About synce" page. > > > Just a few thoughts... > > > > ~Paul h ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
