Simon C
2005-09-21 06:45:45 UTC
New autosync feature for bitpim.
The purpose is to make bitpim automatically sync up with your phone with
your outlook calendar every time you connect it to the PC or at a preset
interval if it is left connected, if the phone supports bluetooth you just
have to be close to the PC for it to sync up as long as bitpim is running.
There is a new menu option "autosync" to configure and run the feature.
The implementation stores the Auto sync folder and filter settings in the
bitpim database, it uses the existing calendar code to import the calendar
from the PC and to send the data to the phone. The existing import calendar
feature still worksas it used to. You can use it with vcal, csv and outlook
calendars. To avoid that annoying "permission" dialog that pops up with
outlook, the autosync feature does not import the body of the calendar
events from outlook, so you only get the event title on the phone, not an
issue with LG phones as they don't support a memo for events anyway.
I and one other person have been testing for a couple of weeks with outlook
and it seems to be working OK. Tested on 4400, 6100 & 8100 although the code
is not phone specific.
It only works in one direction, i.e. outlook calendar copied into phone,
events added to the phone will be lost, a future enhancement would be to
push these back into outlook or at least not loose them. Another improvement
would a way to minimise bitpim and hide it, like bitfling does, this would
make leaving bitpim running easier, also auto starting with user login so it
is completely automatic.
I enhanced the alarm options in the calendar filter so you can choose the
ringtone, vibrate and force the alarms to on for all events, this affects
the existing import feature as well because the filter code is shared.
I included some 8100 calendar enhancements that are independent from the
rest of the code and should be comitted regardless of whether this feature
is.
If you decide to add this I can write up a help page for it.
One new source (auto_sync.py) and 8 edits with diffs attached. It is merged
with the latest code from CVS.
Some of the code changes in Part 2, message too big for sourceforge if I
attach all at the same time.
Simon
The purpose is to make bitpim automatically sync up with your phone with
your outlook calendar every time you connect it to the PC or at a preset
interval if it is left connected, if the phone supports bluetooth you just
have to be close to the PC for it to sync up as long as bitpim is running.
There is a new menu option "autosync" to configure and run the feature.
The implementation stores the Auto sync folder and filter settings in the
bitpim database, it uses the existing calendar code to import the calendar
from the PC and to send the data to the phone. The existing import calendar
feature still worksas it used to. You can use it with vcal, csv and outlook
calendars. To avoid that annoying "permission" dialog that pops up with
outlook, the autosync feature does not import the body of the calendar
events from outlook, so you only get the event title on the phone, not an
issue with LG phones as they don't support a memo for events anyway.
I and one other person have been testing for a couple of weeks with outlook
and it seems to be working OK. Tested on 4400, 6100 & 8100 although the code
is not phone specific.
It only works in one direction, i.e. outlook calendar copied into phone,
events added to the phone will be lost, a future enhancement would be to
push these back into outlook or at least not loose them. Another improvement
would a way to minimise bitpim and hide it, like bitfling does, this would
make leaving bitpim running easier, also auto starting with user login so it
is completely automatic.
I enhanced the alarm options in the calendar filter so you can choose the
ringtone, vibrate and force the alarms to on for all events, this affects
the existing import feature as well because the filter code is shared.
I included some 8100 calendar enhancements that are independent from the
rest of the code and should be comitted regardless of whether this feature
is.
If you decide to add this I can write up a help page for it.
One new source (auto_sync.py) and 8 edits with diffs attached. It is merged
with the latest code from CVS.
Some of the code changes in Part 2, message too big for sourceforge if I
attach all at the same time.
Simon