Hello,
I have been doing some more investigation to see if I can achieve what I
want to do. and after reading your message that you posted concerning
what you want to do with pilot-link 0.9.6 and beyond and I have been
thinking about it a bit more, and learning more about the palm itself.
I have been thinking that maybe what would be a good idea to turn the
existing conduits into dynamically link libs that can be loaded when you
you need them by the program. These libs I think would only need 3 main
subroutines to be called by the main program, but I do need to look at
it a bit more, These would be
init() - this would set up the conduit
sync() - this would do the main syncing
cleanup() - this would tidy up after itself.
As for the programs, I would like to keep the best of both worlds, At
the moment you can sync an indivdual conduit, from the command line. And
also maybe a daemon that would sit on /dev/pilot and wait for the
hotsync button to be pressed. and sync everything, or based upon the
hotsync settings.
Basically the individual programs would work as they do now, but slight
differnt, but from the user point of view nothing would have changed. so
pilot-mail would work something like this
load mail conduit library
Establish connection with palm or hotsync daemon.
call init()
call sync()
call cleanup()
close connection with palm or hotsync daemon.
unload conduit library
end.
This would work similarly for all the existing conduits, now I haven't
really looked but in theory after the connection the code would be moved
to the conduit libary.
Then hopefully the hotsync daemon would work similarly except it would
be able to load and process more than one conduit libraries based upon
the hotsync parameters, but there would be only one connection, so in
theory more than one conduit could be run.
At this stage I just wanted to get my ideas out there, and then see if I
can do anything to realise this, and make hopefully better support for
the palm on unix.
David A. Desrosiers ([EMAIL PROTECTED]) wrote:
>
> > 1. is it possible to sync more than one thing at a time from one hotsync.
> You could easily whip up a conduit to sync to multiple applications if
> you wanted to, but remember there are two ways:
>
> 1. Grab the data as it comes across the Palm/port and move it to where
> the applications expect it (custom conduit required)
>
> 2. Sync multiple times, once for each conduit (not desirable, battery
> life, time suffers)
>
> 3. Some sort of export/import conduit, with a smart script on the
> other side (desktop side) to import the data exported from the Palm
> at sync time into your apps of choice.
>
I think that if we do it right we should have to combine programs, but
enable there to be reused by many programs
> This begs the question about one uniform data storage format for the
> Palm on the desktop side, which all applications can use to read/write to,
> independant of their own propeietary local storage or manipulation formats.
>
> > 2. Is it possible to hot sync over the internet from a windows pc. I am
> > going away and I would like to be able to read my mail. I can get access
> > to windows PC's with internet connections and I can get to my server with
> > pilot-link and pilot-mailsync and malsync, can I sync.. Is there a howto?
> > any sugestions etc.
>
> From Windows to linux? Hrm, never tried that one in an automated
> fashion. You could easily set up 'pilot-xfer -s' in a script looping, and just
> do a network hotsync from your Windows PC to that linux machine, I've done
> something similar to that before. You could also just munch some of the code
> in pilot-link and roll about 20 lines of daemon code into it to respawn it,
> and it would work that way also.
>
> I think the latest cvs version of gnome-pilot can handle this sort of
> daemon/respawn for network hotsync these days. I've never personally tried it
> though.
>
> I started a HOWTO on network hotsync awhile back, got distracted a
> bit, but I'll definately include this in the final version of it.
I started to look a little more at this, and some would would need to be
done in this area, maybe the hotsync daemon would enable this to happen,
as from what I can see on the palm side it will not be very different
from a hotsyncing to windows or pilot-link, they would have to be sort
of the same.
At this stage I have not really looked to hard to see if any of this
could be done, and I really don't want to fork the project, but I think
that this would be something that I would like to contribute to.
--
Gordon Heydon <[EMAIL PROTECTED]>
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix
