One of the secrets of palm development is you really are writing two programs.
The palm application and the conduit.
There is a freeware product that attempts to eliminate the conduit part, but
I didn't find it useful, and the developer hasn't touched it for a couple of
years and claims to have no intention of doing so.
(I did exchange e-mails with him earlier this year)
It has always seemed to me a gaping hole in HotSync(r) that you couldn't
just simply configure it to move text files up and down for your application.
Some people use MemoPad format files, and perhaps that's the simplest way,
but that has its own restrictions, and doesn't take advantage of the
application segregation that is actually a strength of the Palm OS (tm) design.
Another issue is the compiler for conduit programming. I greatly prefer
Borland's C++ Builder for Win32 development, but I can't use for conduits
because 3Com used Microsoft's string classes in the function calls instead
of the standard C++ string class. An unthinking, arbitary, unnecessary
decision that forces you to use the Microsoft C++ compiler.
Roger Stringer
Marietta Systems, Inc.
-----------------------------------------------------------
>Date: 23 Sep 1999 02:31:28 -0700
>From: [EMAIL PROTECTED]
>Subject: Small sync solution wanted
>Hi there,
>With regard to a one-time-small development I would like to know if there
>are easy and cheap ways to sync data (in fact just transfer data) from the
>pilot to the PC and from the PC to the pilot without the need to develop a
>conduit (the conduit SDK is too expencive for my purpose).
>Is there a "standard" conduit or a "default" conduit avail that just moves
>plain data files back and forth or is the only alternative to directly
>communicate via the serial port ??
>Any tips, clues or ideas are appreciated.
>Thanks for help in advance
>Ole
