bitpim-devel — For bitpim developers

[Bitpim-devel] bitpim (CVS) and wxPython 2.5.x (CVS) do not get along...

[Steven P. <n9...@n9...>]

A thousand curses on me for not using the mail-list before I filed this 
as a bug, but I have no time machine so apologies will have to do.

Here is my issue:

Maybe this something nobody has interest in, but I am using wxWindows 
for other programs on MacOSX and I required the latest CVS version 
(2.5.x) to make them work.

So, in trying to get bitpim to work with that version of 
wxWindows/wxPython I am running into a few problems, and it all appears 
to be based on this note from the migration notes file in wxPython:

"The import-startup-bootstrap process employed by wxPython was changed 
such that wxWindows and the underlying gui toolkit are not initialized 
until the wx.App object is created (but before wx.App.OnInit is 
called.) This was required because of some changes that were made to 
the C++ wxApp class.

There are both benefits and potential problems with this change. The 
benefits are that you can import wxPython without requiring access to a 
GUI (for checking version numbers, etc.) and that in a multi-threaded 
environment the thread that creates the app object will now be the GUI 
thread instead of the one that imports wxPython. Some potential 
problems are that the C++ side of the "stock-objects" (wx.BLUE_PEN, 
wx.TheColourDatabase, etc.) are not initialized until the wx.App object 
is created, so you should not use them until after you have created 
your wx.App object. (In fact, until I find a better solution trying to 
use one of the stock objects before the app is created will probably 
result in a crash.)

Also, you will probably not be able to do any kind of GUI or bitmap 
operation unless you first have created an app object, (even on Windows 
where most anything was possible before.)"

Indeed, this is the case, becuase the calendarcontrol.py module is 
causing a segfault when it is imported due to the following:

class CalendarCellAttributes:
def __init__(self):
# Set some defaults

self.cellbackground=wxTheBrushList.FindOrCreateBrush(wx
Colour(230,255,255), wxSOLID)
.
.
.

This happens even when trying to run the calendarcontrol.py module 
standalone. However, when running standalone, if you create the wxApp 
instance at the top of the module, it doesn't crash which is in line 
with the notes posted above.

I am just learning Python, and don't know enough yet to find a 
workaround for this issue. Is there any interest in making this forward 
compatible with the upcoming 2.5.x release of wxPython??  It shouldn't 
affect it's ability to run with 2.4.x at all.

Thanks!

-. ----. -.-- - -.--
Steve Palm - n9...@n9...
-. ----. -.-- - -.-- 

[Bitpim-devel] News updates December 2003

[Roger B. <ro...@ro...>]

[This information is also available in at http://bitpim.sf.net]

I would love to improve the packaging of BitPim on the Mac. If you are
a Mac developer type, know how to build packages (I think you use 
bundlebuilder) and can also build shared libraries, then please contact 
ro...@us.... 

Work on BitPim 0.7 is progressing well. There should be a test release 
in the next few weeks. There are several improvements: 

- Support for more phones 
- The phonebook editor is drastically better 
- Import from CSV with pre-defined profiles for Palm Desktop, Mozilla, 
  Windows Address Book. (There is also incomplete code for Vcard import 
  which may make the release) 
- The protocols are all decoded and encoded based on description files, 
  as opposed to hand written code in prior releases. This makes the code 
  more robust and reliable, as well as easier to extend. There is even a 
  protocol analyser builtin for the curious. 
- Direct USB support for Linux (and Mac if anyone helps) 

I have found a usb library that can be used on Windows, Linux and Mac. It 
allows bypassing the drivers (if any) and talking straight to the device. 
Initial tests on Windows and Linux went well, although I still have to do 
a full blown session. Unfortunately the Windows version of the library is 
still a little too rough to use in a production version of BitPim at the 
moment.

BitPim 0.7 will also work on more phones (ie phonebook, calendar, 
wallpapers, ringtones etc): 

- LG XV-6000. RPI Wireless have been a huge assistance by loaning me the 
  phone and one of their combined data/charge cables. You can thank them 
  for supporting BitPim in this way by ordering stuff from their site at 
  www.rpiwireless.com. Don't forget to tell them BitPim sent you :-)
  
- Sanyo SCP 4900 and SCP 8100 

Roger

[Bitpim-devel] VX10/TM520

[Roger B. <ro...@ro...>]

So what happened to the folks working on the LG VX10/TM520?

Roger

Re: [Bitpim-devel] Updates

[Stephen W. <sa...@us...>]

The next release of Bitpim will include support for reading and writing
the Sanyo 4900/8100 phonebook.  It may also contain some support for the
calendar.  (At least reading the calendar from the phone.).

				Steve


On Sat, 2003-11-29 at 03:06, Roger Binns wrote:
> mrmailer wrote:
> > great, know of any progress for sanyo 4900?:)
> 
> Stephen works on the specifics of those phones.  It
> does however depend on the main phonebook etc code.
> With the current dev version you can't even edit
> an entry :-)
> 
> Roger

Re: [Bitpim-devel] Updates

[Roger B. <ro...@ro...>]

mrmailer wrote:
> great, know of any progress for sanyo 4900?:)

Stephen works on the specifics of those phones.  It
does however depend on the main phonebook etc code.
With the current dev version you can't even edit
an entry :-)

Roger

RE: [Bitpim-devel] Updates

[mrmailer <mrm...@my...>]

great, know of any progress for sanyo 4900?:)









 --- On Fri 11/28, Roger Binns < ro...@ro... > wrote:

From: Roger Binns [mailto: ro...@ro...]

To: bit...@li...

Date: Fri, 28 Nov 2003 16:37:13 -0800

Subject: [Bitpim-devel] Updates



I have spent the last few days learning more about USB than<br>I ever wanted to.  The good news out of all this is that I<br>am now able to talk to the phone using the straight USB cable<br>on both Windows and Linux.  It would also work on a Mac as<br>the library I use is cross platform, but I don't actually<br>have a Mac to test with.<br><br>On Windows, it bypasses the broken FutureDial driver.  On<br>Linux and Mac no driver is needed.<br><br>I haven't done a complete test or hooked in lots of code.<br>My current plan is to finish the code for editing a phonebook<br>entry (all new in 0.7) and release a test of 0.7 which<br>has the new phonebook viewer, editor and import code.<br>After that I will return back to USB issues.<br><br>Roger<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: SF.net Giveback Program.<br>Does SourceForge.net help you be more productive?  Does it<br>help you create better code?  SHARE THE LOVE, and help us help<br>YOU!  Click Here: http://sourceforge.net/donate/<br>_______________________________________________<br>Bitpim-devel mailing list<br>Bit...@li...<br>https://lists.sourceforge.net/lists/listinfo/bitpim-devel<br>

_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com

[Bitpim-devel] Updates

[Roger B. <ro...@ro...>]

I have spent the last few days learning more about USB than
I ever wanted to.  The good news out of all this is that I
am now able to talk to the phone using the straight USB cable
on both Windows and Linux.  It would also work on a Mac as
the library I use is cross platform, but I don't actually
have a Mac to test with.

On Windows, it bypasses the broken FutureDial driver.  On
Linux and Mac no driver is needed.

I haven't done a complete test or hooked in lots of code.
My current plan is to finish the code for editing a phonebook
entry (all new in 0.7) and release a test of 0.7 which
has the new phonebook viewer, editor and import code.
After that I will return back to USB issues.

Roger

Re: [Bitpim-devel] Pictures on VX6000

[Roger B. <ro...@ro...>]

> I have a VX6000.
> If your talking about the graphics that come with the phone they are
...
> Now if you talking about under menu, go to 9, 2, 3, 1,  under wallpaper
> go to more then default then there is

Thanks for the lists.  The second set is the same as the 4400.  The first
set seemed somewhat cheesy which is why I didn't know if it was builtin
or not.

Roger

Re: [Bitpim-devel] Bitpim on MAC

[Roger B. <ro...@ro...>]

> 1) Can you supply to me, or to the Bitpim site a bp.py that is the
> latest version? (I cannot use the .rpm or the .exe, of course, but the
> .py file seems to actually work 

bp.py has been unchanged since almost the begining.  BitPim is actually
scattered across a rather large number of files, including code files,
images, help files etc

I recommend you work from CVS instead (details are on the developer
page).

The reason why there isn't a prepackaged Mac version is quite
simply because I don't have a Mac, and none of the Mac owners
have stepped forward to put the effort in to package it all
up.  There are no technical or other reasons why it hasn't
been done.

> (even though it seems targeted to the WinTel environment!)

Not in the slightest.  The only WinTel specific code deals with audio
format conversion and that is only because Qualcomm only releases
a binary for Windows.

All of the code is platform neutral although it does work around
various quirks on various platforms.

Actually I lied slightly.  You need to do right clicks in the
filesystem view.  I assume that works fine on multi-buttoned
Mac mice.  I have no idea what you do if you have a single
button.

> 2) I already have a Qualcom driver loaded. It directly conflicts with
> the python serial extensions (which have a BSD Un*x driver!) 

The Python serial extensions do not include a driver.  They are merely
a convenient way to access the ports from BitPim code without having
to deal with platform specific issues.  Things such as setting 
timeouts are quite horrid to deal with on each platform.

> This Qualcom driver allows OS-X to see
> the phone as a modem.

That isn't a Qualcomm driver.  What you are seeing is that the
phone's USB interface is actually a composite interface with
two sub interfaces.  One of them is a standard modem interface
and the Mac operating system (as well as Linux) have a default
driver interface for that.

The other interface is a bulk serial interface that you do need
special drivers for.  To my knowledge those drivers are only
available on Windows.  It is that interface (labelled "Diagnostic
Serial interface" on Windows drivers) which BitPim talks to.

The other alternative is to get a USB to serial interface, since
the serial interface in the phone combines access to the modem
interface and the diagnostics interface.

> Is there something that I can do (as a
> non-programmer) that can get you info that, knowing Bitpim, can assist
> me in going further towards an OS-X solution? 

If you work from CVS I would like to know about any bugs or 
other visual glitches.

Other than that, finding someone who has developer skills on a Mac
to make a bundled distribution.  They need to know how to make Mac
packages which I believe is a tool called Bundle Builder.  They
will also have to know all about Framework installs of libraries and
how to build the bundles off them.

Roger

[Bitpim-devel] Bitpim on MAC

[Bob R. <ro...@co...>]

Roger (and the group)

Using a guide on another webpage, piecing together Python 2.3 for OS-X, 
etc I got Bitpim 1.9 to work (sort-of). So here it goes:
1) Can you supply to me, or to the Bitpim site a bp.py that is the 
latest version? (I cannot use the .rpm or the .exe, of course, but the 
.py file seems to actually work (even though it seems targeted to the 
WinTel environment!)
2) I already have a Qualcom driver loaded. It directly conflicts with 
the python serial extensions (which have a BSD Un*x driver!) The 
Qualcom driver shows up as tty.usbmodem191 or tty.usbmodem181 (191 for 
USB port 2, 181 for USB port 1). This Qualcom driver allows OS-X to see 
the phone as a modem. Is there something that I can do (as a 
non-programmer) that can get you info that, knowing Bitpim, can assist 
me in going further towards an OS-X solution? I'll be glad to publish 
here and at http://videogamexchange.com/sites/lg4400/ (The OS-X 
step-by-step site I mentioned)

* Caed Mille Failte (100,000 Welcomes) *
*                Shalom!               *
*            73 from W6HIM             *
*            Bob Rosenberg             *
*       San Juan Capistrano, CA.       *
*        mailto:ro...@co...         *

[Bitpim-devel] Pictures on VX6000

[Pamela R. <spa...@ea...>]

I have a VX6000.
If your talking about the graphics that come with the phone they are
1. bear_heart
2. elvis_birthday_sm
3. hi_pig_sm
3. love_you_cat_sm
4. martini
5. party_time_sm
6. roses
7. sorry_monster_sm
8. sun
9. surfing


Now if you talking about under menu, go to 9, 2, 3, 1,  under wallpaper 
go to more then default then there is
1. Beach Ball
2. Towerbridge
3. Sunflower
4. Beach
5. Fish
6. Sea
7. Snowman

Hope this will help. If you need to know anything else just e-mail me 
back.

    Pamela 

[Bitpim-devel] sanyo 4900

[mrmailer <mrm...@my...>]

sorry, I was spammed to death on yahoo address, so I moved over here.



Just wondering if there was anything new on the progress of sanyo 4900 support, primarily for dealing with contacts on it and transfer of sounds/images.

thanks



_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com

Re: [Bitpim-devel] Anyone with a LGVX6000?

[Robert R. <ro...@fe...>]

My daughter has a VX6000.
This is being cc'd to her. I know she can help here.

Pam, please send a message to Roger using the e-mail address in the to: =
box with the pictures your vx6000 came with.=20
Thanks,
--=20
***************************
*         Shalom          *
*     Caed Mille Failte   *
*     100,000 Welcomes!   *
*      Bob Rosenberg      *
* San Juan Capistrano, CA *
*   mailto:ro...@fe...   *
***************************

Original message:
Is there anyone on this list with an LG VX6000?  I am busy adding
suport for it and have been loaned a phone.  I need to know if
some of the images come with the phone or were added by the phone's
owner.  Please email me if you have one.

And for anyone who is curious:  The software inside the 6000 is
very similar to the 4400.  It just looks like a more modern=20
version.  The phonebook format and capabilities is identical.

But just to make life that little bit more challenging, there
are no less than 5 different locations images are stored and
a similar number for ringtones.

On the USB side, its product and vendor ids are identical to the
4400.  And to gouge owners the cable connector is different.  The
camera is pretty crappy IMHO.

I can use both LG drivers as well as the FutureDial straight USB
VX4400 drivers (they are associated with the same USB ids).  I
haven't hit the driver bugs in the FutureDial drivers yet, but
have had mysterious hangs.  The LG drivers have worked well.

It has been 16 extra lines of code so far to support this phone.

Roger


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Bitpim-devel mailing list
Bit...@li...
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

Re: [Bitpim-devel] Any call releated features?

[Roger B. <ro...@ro...>]

>  1. Make an originating call
>  2. Answering Incomming call

You can do that with data calls.  I don't think you can do it as voice
calls.  Use your operating systems modem stuff.  It is all done as
standard AT commands.

>  3 Get a call_id information  and so on..

I assume you mean you want a call history.  If you go into filesystem
view, look at pim/incoming_log.dat, missed_log.dat and outgoing_log.dat.
My intention is to add all that to BitPim but it is lower down on 
my priority list than the current features.

> if so,, can I get any information ?  I would like to add those feature
> to BitPim project...

Follow the instructions at http://bitpim.sourceforge.net/developer.html
so that you are working from CVS and let us know.  We will take it from
there.

Roger

[Bitpim-devel] Anyone with a LGVX6000?

[Roger B. <ro...@ro...>]

Is there anyone on this list with an LG VX6000?  I am busy adding
suport for it and have been loaned a phone.  I need to know if
some of the images come with the phone or were added by the phone's
owner.  Please email me if you have one.

And for anyone who is curious:  The software inside the 6000 is
very similar to the 4400.  It just looks like a more modern 
version.  The phonebook format and capabilities is identical.

But just to make life that little bit more challenging, there
are no less than 5 different locations images are stored and
a similar number for ringtones.

On the USB side, its product and vendor ids are identical to the
4400.  And to gouge owners the cable connector is different.  The
camera is pretty crappy IMHO.

I can use both LG drivers as well as the FutureDial straight USB
VX4400 drivers (they are associated with the same USB ids).  I
haven't hit the driver bugs in the FutureDial drivers yet, but
have had mysterious hangs.  The LG drivers have worked well.

It has been 16 extra lines of code so far to support this phone.

Roger

[Bitpim-devel] Any call releated features?

[Sungwon B. <tae...@ya...>]

Hi, there,
It is my first time to post my message in the mailist..
Too many errors encountered; the rest of the message is ignored:
Anyway, I am wondering if you guys have tried the following :
  
 1. Make an originating call
 2. Answering Incomming call
 3 Get a call_id information  and so on..
  
 Anything related to Call managing stuff...  I am wondering if it is 
possible thru sending packet in DM mode or not if it is possible by sending AT command...
 
if so,, can I get any information ?  I would like to add those feature 
to BitPim project...
  
 -sungwon

Re: [Bitpim-devel] URL's

[Roger B. <ro...@ro...>]

> I
> noticed that in the new phonebook display gui, you can only successfully
> click on properly formed urls with the http://.

That code is actually currently incomplete.  I will be adding a click handler
that will actually invoke your main browser and feed it the URL doing
URL transmogrification as needed.

Roger

[Bitpim-devel] URL's

[Stephen W. <sa...@us...>]

My phone's browser will accept urls without http:// in front of them. 
So generally, the urls in my phonebook don't have the http://.  I
noticed that in the new phonebook display gui, you can only successfully
click on properly formed urls with the http://.

When I read the phone book from the phone, should I add the http:// to
urls that are missing it?  (I would only do it strings that could be
urls, name that match stuff1.stuff2[/morestuff] where stuff1 and stuff2
have not whitespace.  Or should the phonebook display be modified to
work with urls without the http://?

				Steve

Re: [Bitpim-devel] small patches for phonebook.py

[Roger B. <ro...@ro...>]

Patrick Tullmann wrote:
> Appended below is small patch for phonebook.py.  The first patch
> (checking the indexes in PhoneDataTable.GetValue) seems to prevent an
> infinite recursion of exceptions.

I did a different change earlier.  What is actually happening is
that the grid thinks there are more rows than there actually
are.  It starts asking for non-existent ones which generate an
exception.  The exception dialog is a modal dialog (ie the
ShowModal function starts a new message loop and doesn't
return until the dialog is closed).  The phonebook tries to
display the next cell, and causes another exception which causes
another modal exception dialog to appear etc.  It isn't infinite - 
there will just be one exception per cell, but it is a reasonable
approximation of infinity :-)

A future enhancement I will need to do is to make new exceptions
append to the existing dialog if it is visible rather than
cause a new dialog to be displayed.

The root cause was that the message to tell the grid that rows were
deleted was being ignored.  That was because it has to be told which
rows were deleted, not just how many.  The appending of rows worked
fine however, so it just kept growing each time new entries were
read in.

I have now fixed the code to do the correct deletion and all works
fine.  I do however want to use a custom widget at some point.  The
grid does lots of nasty stuff I don't like.  For example try pressing
the arrow keys to see how broken that is.

> The second patch is just because wxPython doesn't word-wrap its dialog
> boxes, so I manually wrapped the long message.  The "python way"
> probably doesn't involve +='ing string constants...

I do it all the time :-)  The actual problem is that there isn't an
auto-sizing word wrapping text widget in wxWindows.  I did however
find that the HTML widget will at least wrap its text, but it won't
shrink or expand its size.  Try the import dialog after selecting
a file and resize the dialog, paying attention to the instructions
at the top.

Now, if anyone wants a little project then a self sizing HTML widget
would be great.  It shouldn't be too much work, and the wxPython
community would be very grateful :-)  Let me know if you or anyone
else wants to tackle this.

I would use it all over the place.

> My phone is an LGVX4400, I'm running bitpim out of CVS (sync'd as of
> AM Nov. 09), 

The public CVS servers are now synced every 5 hours with the main ones
according to SourceForge.

> on Linux (Debian/testing, 2.4.22 kernel).  I've got
> wxpython version 2.4.2.4, python 2.3, pyserial 2.0, and DSV 1.4.0.
> I'm using the USB cable.

On Linuxm, I use Redhat 8 which is the same versions as above except
Python is 2.2.  As that machine suffers from kernel panics when closing
the USB serial device (a known kernel bug), I don't actually talk to the
phone with it.  I then use my dual boot XP/RH9 box for testing that
actually involves the phone.

>  I'm really hoping the palm<->lg
> sync stuff will let me migrate my contact info out of jpliot...

The CSV import is coming on nicely.  I am just working on code to display
an entry (that is the right hand side in the main phone book tab).
The idea is that the last part of the import process will work much
like personal finance programs.  It will show you what was supplied
from the import, what record already existed, and the result.

I also found a Python library function that makes working out matches
a real cinch. Run experiments/matching.py to see it in action.  According
to the doc, a figure of 60 or greater should be considered a match.  My
first attempt is just going to convert each record to text and run
that function.  I suspect it will give pretty decent results.

And if you want some real fun, turn on protocol logging, read from the
phone and then press Ctrl-Alt-P while viewing the protocol log.

Roger

Re: [Bitpim-devel] How to handle speed dial index

[Roger B. <ro...@ro...>]

Stephen Wood wrote:
> I'll add an attribute 'speeddial' to each number that has a speed dial
> number.
> 
> 'numbers': [{'type': 'cell', 'number': '1234567890', 'speeddial': 3}],
> 
> (Should the speed dial key/index be a number or string?)


A number (unless we discover a problem with that).  I have added speeddial
as an attribute to the doc at the top of phonebook.py

Roger

[Bitpim-devel] ANN: BitPim 0.62 released

[Roger B. <ro...@ro...>]

BitPim 0.62 has now been released.  You only need to upgrade
if you are using the USB cable and drivers supplied with the
Verizon Mobile Office Kit.

http://bitpim.sourceforge.net/#download

Changes since 0.61:

 - Scrolling in the log windows now always leaves text 
   visible 
 - Absurd dates on files in filesystem view no longer cause 
   an exception 
 - Work around the LGE buggy driver which has difficulty with 
   the concept of timeouts.  This driver is the one that comes
   with the Mobile Office Kit from Verizon and is written by
   LG themselves.  The bugs in the FutureDial driver remain
   and cannot be worked around.
 - Updated to pySerial 2, wxPython 2.4.2.4 on all platforms 
   and Python 2.3.2 on Windows 

Roger

Re: [Bitpim-devel] How to handle speed dial index

[Stephen W. <sa...@us...>]

I'll add an attribute 'speeddial' to each number that has a speed dial
number.

'numbers': [{'type': 'cell', 'number': '1234567890', 'speeddial': 3}],

(Should the speed dial key/index be a number or string?)

I won't deal with voice dial now since the actual voice files are
available and can be read and written and kept track of which makes it
all the more complicated.

Steve

On Sun, 2003-11-09 at 14:24, Roger Binns wrote:
> > I wonder how Bitpim should handle Speed dial
> > indices.
> 
> There are two choices.  One would be to store it as a seperate
> table alongside phonebook.  Groups is already done this way,
> although I do want to get rid of that.
> 
> The other is to add speed and voice dial information to each
> phone number if needed.  This is what I would prefer to happen.
> The only side effect is that the speed dial then becomes a
> property of the number, not the phone.  As an example if you
> read from one phone and then wrote to another, the second
> phone would end up with the same speeddials.
> 
> The second approach is what I prefer.
> 
> Roger
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Bitpim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel

[Bitpim-devel] small patches for phonebook.py

[Patrick T. <tul...@fl...>]

Appended below is small patch for phonebook.py.  The first patch
(checking the indexes in PhoneDataTable.GetValue) seems to prevent an
infinite recursion of exceptions.  (I think its trying to invoke
GetValue on something in an exception handler, which causes another,
etc.  Eventually I get Python's equivalent of a stack overflow.)
Returning "" if an index is bad seems to not cause any problems, but
I've no idea if its safe...  (FYI, the explosion of exceptions dialogs
happens at the end of getting the phonebook contents.  I can get the
log contents before/after the patch if that might help.) It might be
worth adding code to notice exceptions during the exception display
and suppress them... heh, you could even pop up a bitpim-BSOD... :)

The second patch is just because wxPython doesn't word-wrap its dialog
boxes, so I manually wrapped the long message.  The "python way"
probably doesn't involve +='ing string constants...

With these two changes I can read my existing phonebook entries off my
phone.  I haven't taken the plunge and actually written anything back
yet.  :)

My phone is an LGVX4400, I'm running bitpim out of CVS (sync'd as of
AM Nov. 09), on Linux (Debian/testing, 2.4.22 kernel).  I've got
wxpython version 2.4.2.4, python 2.3, pyserial 2.0, and DSV 1.4.0.
I'm using the USB cable.

I haven't had a chance to play with bitpim for about 6 months.  Its
progressed impressively since then!  I'm really hoping the palm<->lg
sync stuff will let me migrate my contact info out of jpliot...

-Pat

----- ----- ---- ---  ---  --   -    -      -         -               -
Pat Tullmann                                     tul...@fl...
  Techs in white lab coats are the primary cause of cancer in rats.


Index: phonebook.py
===================================================================
RCS file: /cvsroot/bitpim/bitpim/phonebook.py,v
retrieving revision 1.9
diff -u -b -u -r1.9 phonebook.py
--- phonebook.py	8 Nov 2003 11:53:29 -0000	1.9
+++ phonebook.py	10 Nov 2003 04:47:43 -0000
@@ -190,7 +190,16 @@
         return res
 
     def GetValue(self, row, col):
-        entry=self.main._data[self.rowkeys[row]]
+        if row >= len(self.rowkeys):
+            return ""
+        else:
+            key=self.rowkeys[row]
+
+        if key >= len(self.main._data):
+            return ""
+        else:
+            entry=self.main._data[key]
+
         if col==0:
             names=entry.get("names", [{'full': '<not set>'}])
             name=names[0]
@@ -278,7 +287,12 @@
 
         # 1 to 2 etc
         if version==1:
-            wx.MessageBox("BitPim can't upgrade your old phone data stored on disk, and has discarded it.  Please re-read your phonebook from the phone.  If you downgrade, please delete the phonebook directory in the BitPim data directory first", "Phonebook file format not supported", wx.OK|wx.ICON_EXCLAMATION)
+            msg="BitPim can't upgrade your old phone data stored on disk,\n"
+            msg+="and has discarded it.  Please re-read your phonebook from\n"
+            msg+="the phone.\n\n"
+            msg+="If you downgrade, please delete the phonebook directory in\n"
+            msg+="the BitPim data directory first\n"
+            wx.MessageBox(msg, "Phonebook file format not supported", wx.OK|wx.ICON_EXCLAMATION)
             version=2
             dict['phonebook']={}
             

[Bitpim-devel] @users.sf.net email addresses

[Roger B. <ro...@ro...>]

This is just to let people who use their SourceForge email
addresses (@users.sf.net) that SourceForge keeps rejecting
mail for you.  I have now had this problem with several
different users in the last week.  The problems are usually
intermittent lasting a day or two.  The SourceForge
mail servers report '550 Unrouteable address' and
refuse the mail.

From now on, please do not email me with the reply/from being
@users.sf.net.  Either send directly to the mailing list,
or mail me with a different address.  It is getting very
frustrating having emails back at me.

Roger

Re: [Bitpim-devel] How to handle speed dial index

[Roger B. <ro...@ro...>]

> I wonder how Bitpim should handle Speed dial
> indices.

There are two choices.  One would be to store it as a seperate
table alongside phonebook.  Groups is already done this way,
although I do want to get rid of that.

The other is to add speed and voice dial information to each
phone number if needed.  This is what I would prefer to happen.
The only side effect is that the speed dial then becomes a
property of the number, not the phone.  As an example if you
read from one phone and then wrote to another, the second
phone would end up with the same speeddials.

The second approach is what I prefer.

Roger