[Thread Prev][Thread Next][Thread Index]
Re: [PilotMgr] corrupting appinfo structure (plea for developer help)
>>>>> "RW" == Ronan Waide <waider@xxxxxxxxx> writes:
RW> On July 24, doug@xxxxxxxxx said:
>> I'm really in need of some help with my conduit. What's the best
>> way to debug Pilot-Manager? Is it possible to just run 'perl -d
>> pilot-manager'? I don't even know when my appinfo structure is
>> getting corrupted. It's sometime after the readFile callback. Any
>> help would be appreciated.
>>
>> Again, my project info (including source in html and downloadable)
>> is at http://www.lathi.net/services/syncemacstodo.html
RW> I've always found that the easiest way to debug Perl involves
RW> copious print statements.
I concur although some of the fancier perl debuggers are pretty
nice.
RW> You could also look up Thomas DeWeese's SyncBBDB conduit, which
RW> has a module (afaik) that allows you to run conduits independantly
RW> of PilotManager. Of course, I could be very, very wrong about
RW> this.
Only _mostly_ wrong :)
SyncBBDB includes a perl package SyncUtil which offers a layer of
abstraction from the PilotManager package. This means that the
important guts of your conduit (the part that does the
synchronization) can be independent from PilotManager (and I provide
an implementation of that abstraction layer that works with
PilotManager and with the command line).
However, If you have already implemented your conduit to be 'in
bed' with Pilot Manager it might be a bit of work to separate the two
(it's still something I would recommend doing, but it won't be a drop
in).
------------------------------------------------------------------------
***********************************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary information here! *
* - - - - - - - - - - - - - - *
* MoreInfo/Unsubscribe @ http://www.moshpit.org/pilotmgr *
***********************************************************