You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
(35) |
Apr
(15) |
May
(46) |
Jun
(17) |
Jul
(11) |
Aug
(7) |
Sep
|
Oct
|
Nov
(6) |
Dec
|
---|
From: <luc...@us...> - 2003-03-18 21:18:46
|
Update of /cvsroot/zxsync/zXSync/zXSyncCocoa/build In directory sc8-pr-cvs1:/tmp/cvs-serv27694a/build Log Message: Directory /cvsroot/zxsync/zXSync/zXSyncCocoa/build added to the repository |
From: <luc...@us...> - 2003-03-18 21:14:32
|
Update of /cvsroot/zxsync/zXSync/doc/xsl/html In directory sc8-pr-cvs1:/tmp/cvs-serv25572 Added Files: zxsync.xsl Log Message: Use a customized stylesheet. For now, its only purpose is to display the SourceForge.net logo as requested by SourceForge. --- NEW FILE: zxsync.xsl --- <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'> <xsl:import href="{docbook-stylesheets}/html/docbook.xsl"/> <xsl:template name="article.titlepage.before.recto"> <div style="position: absolute; right: 1ex; top: 1ex"> hosted by <a href="http://sourceforge.net"> <img src="http://sourceforge.net/sflogo.php?group_id=74655&type=2" width="125" height="37" border="0" alt="SourceForge.net Logo"/></a> </div> </xsl:template> </xsl:stylesheet> |
From: <luc...@us...> - 2003-03-18 21:14:18
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv25429 Modified Files: build.xml Log Message: Use a customized stylesheet. For now, its only purpose is to display the SourceForge.net logo as requested by SourceForge. Index: build.xml =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/build.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** build.xml 2 Mar 2003 16:36:38 -0000 1.4 --- build.xml 18 Mar 2003 21:14:12 -0000 1.5 *************** *** 22,25 **** --- 22,38 ---- </fileset> </copy> + + <!-- copy the stylesheet to a temporary location --> + <copy todir="${docbook_temp}"> + <fileset dir="xsl/html"> + <include name="zxsync.xsl"/> + </fileset> + </copy> + + <!-- replace the stylesheet location --> + <replace file="${docbook_temp}/zxsync.xsl" + token="{docbook-stylesheets}" + value="${stdxsl_location}"> + </replace> </target> *************** *** 46,55 **** <target name="make" depends="validate"> ! <!-- transform the documents to html --> <mkdir dir="${html_output}"/> ! <style basedir="${docbook_temp}" destdir="${html_output}" style="${stdxsl_location}/html/docbook.xsl" extension=".html"> <param name="section.autolabel" expression="1"/> </style> --- 59,73 ---- <target name="make" depends="validate"> ! <!-- transform the documents to html --> <mkdir dir="${html_output}"/> ! <!--<style basedir="${docbook_temp}" destdir="${html_output}" style="${stdxsl_location}/html/docbook.xsl" extension=".html"> <param name="section.autolabel" expression="1"/> + </style>--> + <style basedir="${docbook_temp}" destdir="${html_output}" + style="${docbook_temp}/zxsync.xsl" extension=".html"> + <param name="section.autolabel" expression="1"/> + <patternset refid="docbook.xml"/> </style> |
From: <luc...@us...> - 2003-03-18 21:11:55
|
Update of /cvsroot/zxsync/zXSync/doc/xsl/html In directory sc8-pr-cvs1:/tmp/cvs-serv24369/html Log Message: Directory /cvsroot/zxsync/zXSync/doc/xsl/html added to the repository |
From: <luc...@us...> - 2003-03-18 21:11:33
|
Update of /cvsroot/zxsync/zXSync/doc/xsl In directory sc8-pr-cvs1:/tmp/cvs-serv24217/xsl Log Message: Directory /cvsroot/zxsync/zXSync/doc/xsl added to the repository |
From: <gb...@us...> - 2003-03-09 23:34:20
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv12378 Modified Files: design.xml Log Message: fixed broken link to plugin api document Index: design.xml =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/design.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** design.xml 9 Mar 2003 21:47:19 -0000 1.5 --- design.xml 9 Mar 2003 23:34:16 -0000 1.6 *************** *** 362,366 **** <para> The plug-in API is described in detail in a separate ! <ulink url="api.html">document</ulink>. </para> </section> <!-- Plug-in architecture --> --- 362,366 ---- <para> The plug-in API is described in detail in a separate ! <ulink url="apidoc.html">document</ulink>. </para> </section> <!-- Plug-in architecture --> |
From: <luc...@us...> - 2003-03-09 22:00:40
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv2382 Added Files: index.html Log Message: Small refresh page to redirect to html/index.html (allows uploading to the project web page while preserving the directory structure beneath "doc") --- NEW FILE: index.html --- <html> <head> <meta http-equiv="refresh" content="0; URL=html/index.html" /> </head> </html> |
From: <luc...@us...> - 2003-03-09 21:58:41
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv1459 Added Files: index.xml Log Message: Documentation index --- NEW FILE: index.xml --- <?xml version="1.0"?> <!DOCTYPE article PUBLIC "-//OASIS//DTD Simplified DocBook XML V1.0//EN" "http://www.oasis-open.org/docbook/xml/simple/1.0/sdocbook.dtd"> <article> <articleinfo> <title>zXSync - Documentation Index</title> </articleinfo> <section> <title><ulink url="design.html">Design and Architecture</ulink></title> <para> This document explains the overall purpose, design, and architecture of zXSync. </para> </section> <!-- Design and Architecture --> <section> <title><ulink url="apidoc.html">Public Plugin API</ulink></title> <para> This document defines the API for zXSync plugins. </para> </section> <!-- Public Plugin API --> </article> |
From: <luc...@us...> - 2003-03-09 21:48:22
|
Update of /cvsroot/zxsync/zXSync/doc/images In directory sc8-pr-cvs1:/tmp/cvs-serv28319 Modified Files: screenshot.jpg screenshot.pict Log Message: Better screenshot (includes window shadow) Index: screenshot.jpg =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/images/screenshot.jpg,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 Binary files /tmp/cvsmj1MXH and /tmp/cvsWONusf differ Index: screenshot.pict =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/images/screenshot.pict,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 Binary files /tmp/cvsj8ONXI and /tmp/cvseLSTvk differ |
From: <luc...@us...> - 2003-03-09 21:47:22
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv28047 Modified Files: design.xml Log Message: Added author information Index: design.xml =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/design.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** design.xml 2 Mar 2003 16:35:28 -0000 1.4 --- design.xml 9 Mar 2003 21:47:19 -0000 1.5 *************** *** 6,10 **** <article> ! <articleinfo> <title>zXSync - Design and Architecture</title> </articleinfo> --- 6,12 ---- <article> ! <articleinfo> ! <author><firstname>Andreas</firstname><surname>Junghans</surname></author> ! <author><firstname>Geoff</firstname><surname>Beier</surname></author> <title>zXSync - Design and Architecture</title> </articleinfo> |
From: <gb...@us...> - 2003-03-04 05:28:46
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv2266 Modified Files: apidoc.xml Log Message: removed beginWrite and endWrite functions as we agreed they were no longer needed if we had beginSync and endSync. Index: apidoc.xml =================================================================== RCS file: /cvsroot/zxsync/zXSync/doc/apidoc.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** apidoc.xml 4 Mar 2003 04:51:05 -0000 1.1 --- apidoc.xml 4 Mar 2003 05:28:43 -0000 1.2 *************** *** 114,129 **** </para> </section> - <section id="func_dev_beginWrite"> - <title>Device/beginWrite</title> - <funcsynopsis> - <funcprototype> - <funcdef> - <function>Device/beginWrite</function> - </funcdef> - <paramdef>application</paramdef> - </funcprototype> - </funcsynopsis> - <para>XXX In light of the description of <function>Device/beginSync(<parameter>application</parameter>)</function>, is this function necessary anymore? A beginSync function seems like a better place to do this, so we can be certain that data on the device is not changed between read and write. (This assumes the device provides locking functionality of course!)</para> - </section> <section id="func_dev_writeEntry"> <title>Device/writeEntry</title> --- 114,117 ---- *************** *** 151,166 **** </funcsynopsis> <para>Writes <parameter>entries</parameter> to the device, where <parameter>entries</parameter> are passed in the representation of the format for <parameter>application</parameter>, as discovered in <function>Device/getApplications()</function>. All existing entries on the device are replaced.</para> - </section> - <section id="func_dev_endWrite"> - <title>Device/endWrite</title> - <funcsynopsis> - <funcprototype> - <funcdef> - <function>Device/endWrite</function> - </funcdef> - <paramdef>application</paramdef> - </funcprototype> - </funcsynopsis> - <para>XXX This can be removed if <function>Device/beginWrite()</function> can. See the explanation there.</para> </section> <section id="func_dev_deleteEntry"> --- 139,142 ---- |
From: <gb...@us...> - 2003-03-04 04:51:10
|
Update of /cvsroot/zxsync/zXSync/doc In directory sc8-pr-cvs1:/tmp/cvs-serv23212 Added Files: apidoc.xml Log Message: Initial add of Plugin API documentation --- NEW FILE: apidoc.xml --- <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <article> <articleinfo> <author> <firstname>Andreas</firstname> <surname>Junghans</surname> </author> <author> <firstname>Geoff</firstname> <surname>Beier</surname> </author> <title>zXSync Public Plugin API</title> </articleinfo> <section id="introduction"> <title>Introduction</title> <para>This document will describe the plugin API supported by zXSync. Plugins will be the sole means of data interrchange between zXSync and assorted applications, both on supported devices and on the host computer.</para> </section> <section id="pluginexports"> <title>Functions exported by Plugins</title> <para>Functions in this section will be exported by plugins and invoked by the zXSync core.</para> <section id="func_probe"> <title>probe</title> <funcsynopsis> <funcprototype> <funcdef> <function>probe</function> </funcdef> <paramdef>settings</paramdef> </funcprototype> </funcsynopsis> <para>Ask the plug-in to look for one or more devices it supports. "settings" would be a list of objects with settings made for the plug-in (like IP address; maybe simple key-value pairs will suffice). This function should return a list of device objects (in most cases consisting of a single device). "settings" must be a list to permit several devices of the same type to be connected (e.g. common in research and testing labs) - each of these should have its own settings. Even if we only support one settings object per plug-in on the frontend, it will increase flexibility for further expansions. </para> </section> <section id="func_dev_init"> <title>Device/init</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/init</function> </funcdef> <void/> </funcprototype> </funcsynopsis> <para> Give the plug-in the chance to initialize a device (whatever that means in a particular case). This method is called only once, not for every sync. However, if even the case of simply reading entries must be "protected" (i.e. the device must be put in "Sync" state before), this protection should happen here. </para> <para> XXX IMO, we may want to reconsider this. We might not want to place the device in a "Sync" state here unless this will be called every sync. A common pattern for me with the Zaurus is to connect the Z, start the sync app, synchronize, use VNC to the Z to clean up any mess there and resynchronize. Do we wish to force me to quit zXSync before doing something like this? (I do think that we should normally strive, on most devices, to have read be a "protected" operation; by this, I mean that we should go to great lengths to see that what we are synchronizing == current data for a particular application.) </para> </section> <section id="func_dev_free"> <title>Device/free</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/free</function> </funcdef> <void/> </funcprototype> </funcsynopsis> <para>Free any resources that may have been allocated and/or locked during <function>Device/init()</function>.</para> </section> <section id="func_dev_getApplications"> <title>Device/getApplications</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/getApplications</function> </funcdef> <void/> </funcprototype> </funcsynopsis> <para>Returns a list of the applications on the device. The list returns objects that indicate the application identifier and the type of data it supports (contacts, calendars, or todos).</para> </section> <section id="func_dev_beginSync"> <title>Device/beginSync</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/beginSync</function> </funcdef> <paramdef>application</paramdef> </funcprototype> </funcsynopsis> <para>Informs the plugin that we are about to begin synchronization of the specified application. Applications will be specified using the same identifier as in <function>Device/getApplications()</function>. This will be called before each synchronization. The return value to this call will provide synchronization information, including whether the plugin expects to write a single entry at a time or all entries at once.</para> </section> <section id="func_dev_endSync"> <title>Device/endSync</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/endSync</function> </funcdef> <paramdef>application</paramdef> </funcprototype> </funcsynopsis> <para>Called when synchronization of the specified application is complete. The plugin may free any resources or release any locks allocated during <function>Device/beginSync()</function>.</para> </section> <section id="func_dev_readAll"> <title>Device/readAll</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/readAll</function> </funcdef> <paramdef>application</paramdef> </funcprototype> </funcsynopsis> <para>Read all entries from the specified application. This is done after <function>Device/init()</function>, <function>Device/getApplications()</function> and <function>Device/beginSync(<parameter>application</parameter>)</function> have been called. The return value is a list of entry objects which should match the representation returned in <function>Device/getApplications()</function> </para> </section> <section id="func_dev_beginWrite"> <title>Device/beginWrite</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/beginWrite</function> </funcdef> <paramdef>application</paramdef> </funcprototype> </funcsynopsis> <para>XXX In light of the description of <function>Device/beginSync(<parameter>application</parameter>)</function>, is this function necessary anymore? A beginSync function seems like a better place to do this, so we can be certain that data on the device is not changed between read and write. (This assumes the device provides locking functionality of course!)</para> </section> <section id="func_dev_writeEntry"> <title>Device/writeEntry</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/writeEntry</function> </funcdef> <paramdef>application</paramdef> <paramdef>entry</paramdef> </funcprototype> </funcsynopsis> <para>Writes <parameter>entry</parameter> to the device, where <parameter>entry</parameter> is passed in the representation of the format for <parameter>application</parameter>, as discovered in <function>Device/getApplications()</function>.</para> </section> <section id="func_dev_writeAllEntries"> <title>Device/writeAllEntries</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/writeAllEntries</function> </funcdef> <paramdef>application</paramdef> <paramdef>entries</paramdef> </funcprototype> </funcsynopsis> <para>Writes <parameter>entries</parameter> to the device, where <parameter>entries</parameter> are passed in the representation of the format for <parameter>application</parameter>, as discovered in <function>Device/getApplications()</function>. All existing entries on the device are replaced.</para> </section> <section id="func_dev_endWrite"> <title>Device/endWrite</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/endWrite</function> </funcdef> <paramdef>application</paramdef> </funcprototype> </funcsynopsis> <para>XXX This can be removed if <function>Device/beginWrite()</function> can. See the explanation there.</para> </section> <section id="func_dev_deleteEntry"> <title>Device/deleteEntry</title> <funcsynopsis> <funcprototype> <funcdef> <function>Device/deleteEntry</function> </funcdef> <paramdef>application</paramdef> <paramdef>entry</paramdef> </funcprototype> </funcsynopsis> <para>Deletes <parameter>entry</parameter> from the device, where <parameter>entry</parameter> is passed in the representation of the format for <parameter>application</parameter>, as discovered in <function>Device/getApplications()</function>.</para> </section> </section> </article> |