Re: A few questions...

"Roger Binns" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <00f801c517cc$f1a2e940$3501a8c0@rogersqyvr14d3>
> I've got the files for the LG PM-325 getting and sending the basic phone book entries.  
> What's the preferred protocol for checking in?  

The amount of functionality doesn't matter.  What is there should be reasonably safe
in that it doesn't destroy user's data.  (ie it is better to get one thing working 
well rather than lots of things working badly)

Then post your changes to this group.  Make sure to include text for the versionhistory
file which sets expectations appropriately.

> I don't have ringers, speeddials or wallpaper ready yet.  

That doesn't matter.  Just make sure the phone profile turns them off in the user
interface.

> Next, the brew protocol for the phone book doesn't seem to have an entry for the 
> wall paper. 

The "brew protocol" does files in the embedded filesystem only.  The LG phonebook
protocol is at a higher level and operates on phonebook records.

> but if I have to update pbookcontact.dat then I might as well replace ALL of the 
> brew phonebook update functionality, and that looks to be way overkill.  

I always avoid modifying the files directly instead of using the sync protocol.
That means that you don't get caught out by other data dependencies - for example
the call history may link into the phonebook and if you directly update the
phonebook file, you could make the phone crash due to broken linkage.

One possibility is to update everything you can using the phonebook protocol and
then patching the file to update the wallpaper info.  That is far less risky.

Roger


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.