Post by Stephen WoodI would like to polish up the help files a bit. I have some stuff I
have been working on that is not checked in yet. I'll try to submit
that tomorrow.
Cool. A large amount of the help needs updating anyway so you will be
way ahead of the curve there :-)
Post by Stephen WoodFor the Sanyo phonebook, the ringer and wall paper assignments are just
indices (numbers).
They are also that on the LG phones as stored in the phonebook.
There are other files that then get read that map from indices
to names.
The getfundamentals code for LG reads the wallpaper and ringtone
index information, and sets wallpaper-index and ringtone-index
keys.
The getphonebook code then converts the numbers as it reads in
each phonebook entry and publishes them as the filenames (string).
savephonebook converts the other way when it writes out.
So if you can do all that, it will work perfectly.
If you really only have numbers and no names can ever be recovered,
then I think the best way is to make a synthetic name. I would
recommend using "Index" plus the number (or "Sanyo4900Index" plus
number).
The header at the top of phonebook.py does allow for the use
of 'wallpaper' or 'index' for each wallpaper, but the phonebookentryeditor
doesn't pay any attention to index, and will fall over if wallpaper
isn't a string. I think it will be just too complicated at the moment
having both around and would prefer only one (alternately you are
welcome to try and fix the code everywhere :-)
Post by Stephen WoodIf this should be done, it would be good to change it for the
test release to minimize file incompatibilities between the test release
an a final release.
Fortunately file formats aren't an issue. Every file has a version
number in it. On reading, a routine is called that will convert
to a newer version. The function is named 'versionupgrade' by
convention and you can find it in a few places. That makes it
trivial to make content changes. (That said I still haven't
written the routine to convert from phonebook in BitPim 0.62 to
phonebook in 0.7 :-)
The only other piece missing is downgrades. Currently older versions
of BitPim will just try to use the new data and fall over in various
ways. I do need to add code that will ignore more recent versioned
data.
Roger