I write my conduits in Visual C++ 6.0 but I usually just ignore the classes
(they have a few subtle bugs like memory leaks) and just call the sync
manager functions directly. This should work with any C compiler. I view the
classes for conduits as a convenience from 3Com for those who are writing in
that environment (which is, after all, fairly common)
-----Original Message-----
From: Stringer [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 24, 1999 7:43
To: [EMAIL PROTECTED]
Subject: Re: Small sync solution wanted
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.
