>       I've been tinkering with an idea about distributing pilot-link's
> future versions as two physically separate entities: 1.) the core libraries
> and headers required for third party packages and authoring conduits
> (libpisock), and 2.) a package which contains all of the current conduits
> which are derived from those sources (dlpsh, install-todo, etc.)
> 
>       Comments?
> 
> /d

Hello David,

I think the pilot-link source directory would benefit from a tidying
up and that doing so would probably facilitate what you outline, even
if you still choose to distribute the "core" conduits with the
libraries etc.  as one package.

Maybe a $PILOT_LINK_TOP/conduits/core directory that collected all the
current stuff that sits above the "libsock", "libcc" and other
directories would do this and allow folk who wish to tinker with the
conduit codes for their own ends to distribute stuff for testing that
simply slots into the main tree.

Maybe even something like the following would suit:

$PILOT_LINK_TOP/conduits/buttons  (the four main Palm OS Apps)

$PILOT_LINK_TOP/conduits/osapps   (non-"button" Palm OS Apps)

$PILOT_LINK_TOP/conduits/system   (pilot-xfer, schelp etc etc - manipulates
                                    the system rather than any App per-se)

$PILOT_LINK_TOP/conduits/package-name  (for non Palm OS App conduits)

within which, each conduit either reads/writes a single format (XML ?)
that provides for other formats through external translators, or where
the conduit itself is written so that drop-in read/write routines
built around individual records can be added there.

For example, the ical specifc bits  of 

read-ical.c :  Translate Palm ToDo and Datebook databases into ical 2.0
               format

would then either become read/write routines in "beefed up"

$PILOT_LINK_TOP/conduits/buttons/todo.c
$PILOT_LINK_TOP/conduits/buttons/datebook.c

or become a external converter pair that operate on the XML output of
the above two, eg,

$PILOT_LINK_TOP/xslt/todo-ical.c
$PILOT_LINK_TOP/xslt/datebook-ical.c

I guess it all depends on how many pipes you want in your "pipeline"
between the PalmDB and the output format of choice.

just food for thought,
Kevin

-- 
Regards,

----------------------------------------------------------------------
*  Kevin M. Buckley              e-mail: [EMAIL PROTECTED]   *
*                                                                    *
*  Systems Administrator                                             *
*  Computer Centre                                                   *
*  Lancaster University          Voice:  +44 (0) 1524 5 93718        *
*  LANCASTER. LA1 4YW            Fax  :  +44 (0) 1524 5 25113        *
*  England.                                                          *
*                                                                    *
*  My PC runs Linux/GNU, you still computing the Bill Gate$' way ?   *
----------------------------------------------------------------------
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Reply via email to