bitpim-devel — For bitpim developers

Re: [Bitpim-devel] Phonebook/Calendar sync w/external programs?

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

On Dec 18, 2003, at 10:27 PM, Roger Binns wrote:
>> I haven't seen any hints of beginnings of
>> code in bitpim to deal with this.
>
> Look harder :-)  There is a module named importexport almost
> 500 lines long and a whole bunch of code in phonebook.py!

  I did find that, sorry for not referencing it. I was looking for 
beginnings of integration with your WAB code into bitpim, which I 
didn't find. That's easy, it's not there. ;-) Given the roadmap for the 
project, it makes sense, I guess I'm just jumping the gun a little bit 
trying to get too much in too quickly. Roll over, Crawl, Walk, Run... 
That's it. :-)

> The intention is for 0.7 to have the ability to import.  (This isn't
> the same thing as synchronization, but is an important first step).

  Yes, I agree. For now, then, I will focus on a convenient way that 
enables users to pull the AddressBook/iCal information into bitpim.

> If anyone actually wants to design synchronization then that would
> be a good idea.  The actual process would have to recognising changes
> in various data sources and applying them to others.  Overall trivial
> big picture but really difficult when you get down to nuts and bolts.
> It is also an absolute prerequisite that it isn't stupid.  I would
> rather not have the feature at all, than have one that magically
> duplicates data.

  Indeed. The MacOS AddressBook and iCal program have (as I suspect do 
most others) UID's attached to the main entries. In the case of the 
address book, for a given name you can have, of course, multiple 
addresses, and bits of contact information. Each address has it's own 
UID, as does each piece of contact information (phone number, email, 
Instant Messenger handle, URL, etc...). Each iCal event also has a UID.

  Obviously, this is a careful line to walk... I see the bits to store 
serial numbers and source in bitpim. It would take careful work, 
though, to deal with entries created on the phone v computer, as well 
as created on one device, modified on the other, etc... And that is 
only assuming one device and one source of each type of data on the 
computer.

  This is where I often tend to go for a certain base level of 
functionality and call it "good enough" for me. That's the difference 
between programming something becuase YOU want it versus trying to meet 
the (real or perceived) needs of users.

> Anyway, let us know what tickles your fancy. #2 (both gui and 
> mechanism)
> is what needs to be completed for the 0.7 release.  Everything else
> can be later.

  I'll ponder the list and soak up the code a bit. Since my Python 
skills are still being formed, I'm leary of doing a whole lot just 
yet... No reason to put a bunch of shoddy code in there until I grok 
the "Pythonic way" to do things. I'm much more comfortable at this 
point with making the Mac version well supported and integrated in it's 
own right. I enjoyed the libusb stuff and packaging up a distribution, 
and my current work on getting data out of the other programs on the 
Mac.

  Thanks again, Roger, for a great program. It's nice to be able to do 
even a little bit to help.

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

Re: [Bitpim-devel] sanyo 4900 news

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

mrmailer wrote:
> I see it says on the bitpim website under other phones that in .7 
> image/ringer support will be available for the sanyo 4900.

At this point Stephen is saying "I told you so".  I didn't want to
litter the text with lists of exceptions of what would and would
not be supported for each phone, so it is concise and misleading :-)

When 0.7 actually gets released you will see if there is image/ringer
support for the Sanyo.  I don't believe there is any code at
the moment.

Roger

Re: [Bitpim-devel] Images and ringtones in CVS version

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

On Dec 11, 2003, at 6:45 AM, Roger Binns wrote:
> The wallpaper tab will now read data from multiple locations.
> This is needed for the VX6000 which has 3 different locations
> for images (Brew, MMS and DRM) as well as the camera, plus of
> course the builtin images.

  I notice that the wallpaper images brought in from the phone do not 
get scaled to the thumbnails on the Mac (no other platforms to compare 
with here). However, images I drop into the wallpaper view from the 
computer do get scaled properly to fit the view icon size. Particularly 
annoying are photos snapped using the camera, which are at 640x480 and 
you only see a fragment of the upper corner in the wallpaper view.

  Also, wxMimeTypesManager seems to be broken or at least not fully 
implemented on the Mac. If I double click on an image it simply tells 
me I have no program associated with .jpg, .bmp, etc... I just looked 
through the 2.5.x CVS code tree I have on my system and even in that 
version this module is almost entirely stubbed out. Oh well... :-(

  Maybe we could add an item to the contextual menu there to at least 
allow you to pick an image and save it to some location on the disk. 
That, coupled with the drag-n-drop to add the images would provide at 
least some GUI way for Mac users to pull images out of the wallpaper 
repository, change it, and put it back. Just a thought.

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

Re: [Bitpim-devel] Phonebook/Calendar sync w/external programs?

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

> I haven't seen any hints of beginnings of
> code in bitpim to deal with this.

Look harder :-)  There is a module named importexport almost
500 lines long and a whole bunch of code in phonebook.py!

The intention is for 0.7 to have the ability to import.  (This isn't
the same thing as synchronization, but is an important first step).

If anyone actually wants to design synchronization then that would
be a good idea.  The actual process would have to recognising changes
in various data sources and applying them to others.  Overall trivial
big picture but really difficult when you get down to nuts and bolts.
It is also an absolute prerequisite that it isn't stupid.  I would
rather not have the feature at all, than have one that magically 
duplicates data.

> but I'm not sure the best way to slip this into bitpim. 

Start with importing address information.  There are two stages,
both of which are present in importexport and phonebook
respectively.

Try importing a CSV file to get a feel for the process.

The first stage is handled in importexport.py and allows the user
to choose what they want to import.  It is currently missing a
category checklistbox which I will be adding.

In the case of CSV files, the user also gets to define the columns.
For other data sources (vcard, WAB, etc) we already know what the
columns are and the column header stuff won't be present.

The user will be able to filter what gets imported (eg requiring
at least a phone number, or for the entry to be in a particular category).

The importexport code then converts the entry into the bitpim python
dictionary format and supplies it to importdata() in phonebook.py.
That then brings up another dialog that controls the merging of
the imported entries with what you already have.

The process is very similar to reconciling transactions in programs
like Quicken or Microsoft Money.  An imported entry could match
an existing entry and be 'merged' or it could be a new entry.
The code takes its best guess and then lets the user override what
happens.  I have also tried to put a numerical 'certainty' value
on each match and merge, but will probably remove that as it isn't
user friendly.  (The code should just get it right).

That code mostly works at the moment.  However there is an edit control
for each line missing (to allow you select a different match or to
say an entry should be new or deleted).  I also needed a entryeditor.
So I went off and wrote one.  But that needed the publish/subscribe
system in order to deal with wallpapers and ringtones correctly.
And the VX4400/6000 code wasn't in any fit shape to cooperate so
I went in and fixed that.  I am in the final throes of that 
and then will be able to go back to what I was working on in the
first place before the several week detour :-)

So there are several things you can do:

1  - Get various data sources working but not hooked into the bitpim
     code (ie they are ready for 0.8)
2  - Complete the code for the current import phonebook code (gui and 
     mechanism)
3  - Write new code for importing calendar (gui and mechanism)
4  - Write code for generic phonebook export (gui and mechanism)
5  - Write code for generic calendar export (gui and mechanism)
6  - Design and completely think through a synchronisation algorithm.
     It should be able to cope with multiple phones (eg people wanting
     it to work with both their and their partners phones), and not
     be stupid.  There should also be some sort of design for an
     undo/redo system in there as well, as I suspect this would 
     all be based on some sort of transactioning and differencing
     engine.  I would also expect it to need some sort of real
     database behind the scenes, and have already selected sqlite
     (and pysqlite as the wrapper) for those purposes

I'll be completing the gui bit of #2 so don't bother working on that.
However the mechanism bit is what needs the most work, I would be
very happy for someone else to do it.  Start at the MergeEntries
function in phonebook.py.

Anyway, let us know what tickles your fancy. #2 (both gui and mechanism)
is what needs to be completed for the 0.7 release.  Everything else
can be later.

Roger

Re: [Bitpim-devel] sanyo 4900 news

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

I see it says on the bitpim website under other phones that in .7 image/ringer support will be available for the sanyo 4900.

I can just wait till then:)









 --- On Thu 12/18, mrmailer < mrm...@my... > wrote:

From: mrmailer [mailto: mrm...@my...]

To: bit...@li...

Date: Thu, 18 Dec 2003 05:18:40 -0500 (EST)

Subject: Re: [Bitpim-devel] sanyo 4900 news



<br>no, but if I can help in any other way I'd be glad to.  I showed bitpim to a friend tonight who has vx-4400 and it works great, I was interested in it myself cuz it's free and for linux:)<br><br><br><br><br><br><br><br><br><br> --- On Wed 12/17, Chris Cleeland < cle...@oc... > wrote:<br><br>From: Chris Cleeland [mailto: cle...@oc...]<br><br>To: bit...@li...<br><br>Date: Wed, 17 Dec 2003 20:50:08 -0500 (EST)<br><br>Subject: Re: [Bitpim-devel] sanyo 4900 news<br><br><br><br>On Wed, 17 Dec 2003, mrmailer wrote:<br><br>> <br>> I see, does it support midi and picture transfer?<br><br>Not yet.  Do you have snapmedia software?<br><br><br>-- <br>  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris<br>     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066<br>      Support Me Supporting Cancer Survivors in Ride for the Roses 2002<br>    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: IBM Linux Tutorials.<br>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's<br>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.<br>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click<br>_______________________________________________<br>Bitpim-devel mailing list<br>Bit...@li...<br>https://lists.sourceforge.net/lists/listinfo/bitpim-devel<br><br><br>_______________________________________________<br>No banners. No pop-ups. No kidding.<br>Introducing My Way - http://www.myway.com<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: IBM Linux Tutorials.<br>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's<br>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.<br>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click<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

Re: [Bitpim-devel] Phonebook/Calendar sync w/external programs?

[Chris C. <cle...@oc...>]

On Thu, 18 Dec 2003, Steven Palm wrote:

> I have wrapped methods in Python to allow the ability to interact with 
> both AddressBook and iCal on MacOS X. I can retrieve/set information in 
> both applications, but I'm not sure the best way to slip this into 
> bitpim. (Actually, I have code that works, but to make it user friendly 
> I should wrap it into modules that abstract the details to a simpler 
> higher level API. My current approach is to use Python to wrap 
> AppleScript to actually talk to the respective applications. Works 
> pretty well in my initial testing.)

Cool.  Those higher level APIs should be designed such that they could be 
useful for accessing any external calendar, including things like Yahoo! 
calendar, etc.  Basically, the existing modules you designed would be 
replicated for other calendar backends, and the higher level API (that 
doesn't yet exist) would be the generic API.

> One thought I had on the phonebook was that you may not want to have 
> your entire computer address book in the phone. Perhaps there should be 
> a setting somewhere for a particular group name that gets synchronized? 
> Just a thought...  Same thing with calendars... You can have multiple 
> calendars in iCal, I suspect only one would synchronize to your phone.

This is definitely the same way I was thinking.  I would also like to be able 
to import schedule information from somebody else's calendar, e.g., my 
wife's, and have each entry auto-prefixed with some character or string so 
that I can easily discern my events from hers.

As far as pushing schedules onto the phone, I can think of several ways in 
which one might want to constrain/filter a calendar, e.g., by date range, by 
time slot, etc.  Maybe the best way to allow this is to allow arbitrary 
python code to be written?  However, that could be a giant security hole...


-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

[Bitpim-devel] OT: Myths Article regarding Open Source Development

[Jim <Ji...@ja...>]

http://www.onlamp.com/pub/a/onlamp/2003/12/11/myths.html

Jim West
www.jameswest.com

The box said Windows 95 or better, so I installed Linux.

[Bitpim-devel] Phonebook/Calendar sync w/external programs?

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

I'm just trying to get a feel for the direction things are going to 
sync the phonebook and calendar to external programs. I know Roger has 
been doing some work on getting into the Windows Address Book stuff, 
but on a quick once-over, I haven't seen any hints of beginnings of 
code in bitpim to deal with this.

I have wrapped methods in Python to allow the ability to interact with 
both AddressBook and iCal on MacOS X. I can retrieve/set information in 
both applications, but I'm not sure the best way to slip this into 
bitpim. (Actually, I have code that works, but to make it user friendly 
I should wrap it into modules that abstract the details to a simpler 
higher level API. My current approach is to use Python to wrap 
AppleScript to actually talk to the respective applications. Works 
pretty well in my initial testing.)

One thought I had on the phonebook was that you may not want to have 
your entire computer address book in the phone. Perhaps there should be 
a setting somewhere for a particular group name that gets synchronized? 
Just a thought...  Same thing with calendars... You can have multiple 
calendars in iCal, I suspect only one would synchronize to your phone.

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

Re: [Bitpim-devel] sanyo 4900 news

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

no, but if I can help in any other way I'd be glad to.  I showed bitpim to a friend tonight who has vx-4400 and it works great, I was interested in it myself cuz it's free and for linux:)









 --- On Wed 12/17, Chris Cleeland < cle...@oc... > wrote:

From: Chris Cleeland [mailto: cle...@oc...]

To: bit...@li...

Date: Wed, 17 Dec 2003 20:50:08 -0500 (EST)

Subject: Re: [Bitpim-devel] sanyo 4900 news



On Wed, 17 Dec 2003, mrmailer wrote:<br><br>> <br>> I see, does it support midi and picture transfer?<br><br>Not yet.  Do you have snapmedia software?<br><br><br>-- <br>  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris<br>     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066<br>      Support Me Supporting Cancer Survivors in Ride for the Roses 2002<br>    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: IBM Linux Tutorials.<br>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's<br>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.<br>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click<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] Another little project

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

I have another little project for anyone who wants something
well defined and simple to learn Python and help bitpim.

I need code that can parse the following file:

   http://www.linux-usb.org/usb.ids

I need to be able to lookup vendor, product and interface information.
Note also that about 2/3 of the way down it has definitions for
device classes which would be nice to parse as well.  The audio and
HID stuff doesn't matter.

The idea will be to hook this code into the com/usb port browser so
that meaningful names are displayed for the various devices found.
I will probably ship a copy of that file with bitpim.

Roger

[Bitpim-devel] A note about comscan

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

Steven,

I noticed you updated comscan.py.  What you didn't know is that the
master comscan code is actually in the comscan module, and a copy
is made into bitpim.

However since we now support USB, the utility of a seperate
comscan module and program (see the download site) is significantly
diminished, so I have decided to junk the comscan module.

What is definitely needed is to be able to save the contents
of the browsing ports dialog so that users can email it along
with any problem reports.

Roger

[Bitpim-devel] List for CVS checkins

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

There is a new mailing list for cvs checkins.  All cvs checkins result
in a unified diff sent to the list, which is useful for tracking
what changes everyone is making.  Followups/Replyto are sent to
bitpim-devel.  To subscribe, go to:

http://lists.sourceforge.net/lists/listinfo/bitpim-cvs-checkins

Roger

Re: [Bitpim-devel] sanyo 4900 news

[Chris C. <cle...@oc...>]

On Wed, 17 Dec 2003, mrmailer wrote:

> 
> I see, does it support midi and picture transfer?

Not yet.  Do you have snapmedia software?


-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

Re: [Bitpim-devel] sanyo 4900 news

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

I see, does it support midi and picture transfer?









 --- On Wed 12/17, Chris Cleeland < cle...@oc... > wrote:

From: Chris Cleeland [mailto: cle...@oc...]

To: bit...@li...

Date: Wed, 17 Dec 2003 15:31:19 -0500 (EST)

Subject: Re: [Bitpim-devel] sanyo 4900 news



On Wed, 17 Dec 2003, mrmailer wrote:<br><br>> <br>> the same:)  just wondering status of bitpim support for it(transferring<br>> phone #'s. media, etc)<br><br>Worked for me the other day on my 8100--at least sucking them out.  I haven't <br>tried pushing them back yet.<br><br><br>-- <br>  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris<br>     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066<br>      Support Me Supporting Cancer Survivors in Ride for the Roses 2002<br>    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: IBM Linux Tutorials.<br>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's<br>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.<br>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click<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

Re: [Bitpim-devel] Another developer added to the fold

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

> (Is there a SMS gateway where
> you can send to nu...@so... without having to do something
> different for different carriers).

Of course not!  That would allow people to move easily amongst
carriers :-)

Roger

Re: [Bitpim-devel] Another developer added to the fold

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

On Wed, 2003-12-17 at 03:44, Roger Binns wrote:

> For SMS it is easy.
Of course.

...
> Here is what an ordinary call would look like, assuming the number 
> had been phone in your phonebook
> 
> ======
> From: 555555555 (Mary Brown)
> To: John Smith
> Date: Jan 1 2003, 10:43am
> Subject: Phone call: 25 minutes  # could also be Missed Call, Outgoing call etc
> 
> The same information in the body
> ======
I still think call history makes more sense going into a/the calendar,
but putting it in email has possibilities.  If the phone number is in
the phonebook and there is an email address for that name, the email
address can be used as the "From".  Also, if the phone number was a
mobile, we could generate an SMS address.  (Is there a SMS gateway where
you can send to nu...@so... without having to do something
different for different carriers).

			Steve

Re: [Bitpim-devel] sanyo 4900 news

[Chris C. <cle...@oc...>]

On Wed, 17 Dec 2003, mrmailer wrote:

> 
> the same:)  just wondering status of bitpim support for it(transferring
> phone #'s. media, etc)

Worked for me the other day on my 8100--at least sucking them out.  I haven't 
tried pushing them back yet.


-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

Re: [Bitpim-devel] sanyo 4900 news

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

the same:)  just wondering status of bitpim support for it(transferring phone #'s. media, etc)









 --- On Wed 12/17, Chris Cleeland < cle...@oc... > wrote:

From: Chris Cleeland [mailto: cle...@oc...]

To: bit...@li...

Date: Wed, 17 Dec 2003 14:03:47 -0500 (EST)

Subject: Re: [Bitpim-devel] sanyo 4900 news



On Wed, 17 Dec 2003, mrmailer wrote:<br><br>> Just wondering if there's any new news on sanyo 4900 support.<br><br>What is it you want to know?<br><br><br>-- <br>  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris<br>     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066<br>      Support Me Supporting Cancer Survivors in Ride for the Roses 2002<br>    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<<br><br><br>-------------------------------------------------------<br>This SF.net email is sponsored by: IBM Linux Tutorials.<br>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's<br>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.<br>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click<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

Re: [Bitpim-devel] sanyo 4900 news

[Chris C. <cle...@oc...>]

On Wed, 17 Dec 2003, mrmailer wrote:

> Just wondering if there's any new news on sanyo 4900 support.

What is it you want to know?


-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

[Bitpim-devel] sanyo 4900 news

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

Just wondering if there's any new news on sanyo 4900 support.



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

Re: [Bitpim-devel] Another developer added to the fold

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

> At this point, there's only one protocol file for sanyo; are you suggesting
> that it should be broken up, or just offering this as a suggestion?

The email was mostly directed at Stephen who would know exactly what to
do :-)

Roger

Re: [Bitpim-devel] Another developer added to the fold

[Chris C. <cle...@oc...>]

On Wed, 17 Dec 2003, Stephen Wood wrote:

> What I will do is move most of the code from com_sanyo4900.py into
> com_sanyo.py, and then create mostly empty com and protocol files for
> the three phones.

That sounds like a good plan.  What about the Profile class that's in there?

Should there also be separate protocol specs for each phone, similar to 
what's being done for the communications?

-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

Re: [Bitpim-devel] Another developer added to the fold

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

On Wed, 2003-12-17 at 10:26, Chris Cleeland wrote:

> On Wed, 17 Dec 2003, Roger Binns wrote:
> 
> > BTW it is really easy to make a seperate module for the 8100 and share
> > all code, with any exceptions you want to make.  I did it for the 
> > VX6000 and VX4400.  Here is how:
> > 

I will create a module for the 8100 in the next few days.  While I
believe that the 8100 interface is identical to the 4900 in those
matters that have been put into BitPim, it is time to do it.  And who
knows, we may somehow figure out how to download camera pictures from
the 8100, and since the 4900 doesn't have a camera, that's a
difference.  I will also make a module for the Sanyo SCP-5300 since I
also believe that is similar.

What I will do is move most of the code from com_sanyo4900.py into
com_sanyo.py, and then create mostly empty com and protocol files for
the three phones.

				Steve

Re: [Bitpim-devel] Another developer added to the fold

[Chris C. <cle...@oc...>]

Okay, forgive the python ignorance...

On Wed, 17 Dec 2003, Roger Binns wrote:

> > You can see changes on individual files with the viewcvs.  The code for
> > the Sanyo 4900/8100 is in the files com_sanyo4900.py, com_sanyo.py, and
> > p_sanyo.p.
> 
> BTW it is really easy to make a seperate module for the 8100 and share
> all code, with any exceptions you want to make.  I did it for the 
> VX6000 and VX4400.  Here is how:
> 
> com_sanyo4900:
> ======
> class Phone(...):
> 
>      protocolclass=p_sanyo4900
>      desc="Sanyo 4900"
>     
>      def calendar(self):
>          # whereever you need protocol objects, instantiate them like this
>          req=self.protocolclass.calendarentry()
> ======
> 
> p_sanyo8100:
> ======
> %{
> # This brings all objects from sanyo4900 into this namespace
> from p_sanyo4900 import *
> %}
> 
> # you can put any overrides here, eg if the calendarentry is
> # a different size
> 
> PACKET calendarentry:
>      99 STRING description
> ======


At this point, there's only one protocol file for sanyo; are you suggesting 
that it should be broken up, or just offering this as a suggestion?

> com_sanyo8100:
> ======
> class Phone(com_sanyo4900.Phone):
> 
>      protocolclass=p_sanyo8100
>      desc="Sanyo 8100"
>      def __init__(self):
>          com_sanyo4900.Phone.__init__(self)
> =======

There's another class declared at the end of this file: class Profile.  Does 
that need to be inherited, too?  Or, does it need to be broken out into a 
separate class, or perhaps phonebook.py needs to be massaged to allow 
individual phones to decorate a phone book entry?

-- 
  Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris
     Principal Software Engineer, Object Computing, Inc., +1 314 579 0066
      Support Me Supporting Cancer Survivors in Ride for the Roses 2002
    >>>>>>>>>    Donate at http://www.milodesigns.com/donate    <<<<<<<<<

Re: [Bitpim-devel] Another developer added to the fold

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

> You can see changes on individual files with the viewcvs.  The code for
> the Sanyo 4900/8100 is in the files com_sanyo4900.py, com_sanyo.py, and
> p_sanyo.p.

BTW it is really easy to make a seperate module for the 8100 and share
all code, with any exceptions you want to make.  I did it for the 
VX6000 and VX4400.  Here is how:

com_sanyo4900:
======
class Phone(...):

     protocolclass=p_sanyo4900
     desc="Sanyo 4900"
    
     def calendar(self):
         # whereever you need protocol objects, instantiate them like this
         req=self.protocolclass.calendarentry()
======

p_sanyo8100:
======
%{
# This brings all objects from sanyo4900 into this namespace
from p_sanyo4900 import *
%}

# you can put any overrides here, eg if the calendarentry is
# a different size

PACKET calendarentry:
     99 STRING description
======

com_sanyo8100:
======
class Phone(com_sanyo4900.Phone):

     protocolclass=p_sanyo8100
     desc="Sanyo 8100"
     def __init__(self):
         com_sanyo4900.Phone.__init__(self)
=======

The above will let you have seperate files for the phones, but share
all the code except whatever you decide to override.  It also means
the user will see the correct phone model in any log messages.

Roger