News for PISI opimd support - with release 0.4.10 PISI supports field
types. As the opimd news have not yet made it into the repositories, you
may configure for PISI, whether to use this new feature or not in your
config file (/home/root/.pisi/conf):

[opimd]
description=OPIMD Contacts
module=contacts_opimd
field_support=TRUE


Default is FALSE!

Best
Michael


On 12/17/2009 11:00 AM, Michael Pilgermann wrote:
> Hi all,
> 
> in terms of PISI you only need to make sure that in the config file
> (/root/.pisi/conf) the option is disabled:
> 
> [opimd]
> description=OPIMD Contacts
> module=contacts_opimd
> phone_autoprefix=FALSE
> 
> The code has been changed already; so the auto-prefixing will not take
> place any longer (with the next minor release of PISI).
> 
> For applying the changes to PISI for the attributes
> (http://wiki.openmoko.org/wiki/Opimd_redesign#Changes_in_fields) I am a
> bit lost. I have upgraded to latest SHR-T last night; though I haven't
> been successful in accessing the types information under Python
> (although I understood the theory behind) ...
> 
> 1) Maybe the news have not yet made it into SHR-Testing?, or
> 2) Can anybody provide a working Python-Script accessing this kind of info??
> 
> Thx in advance, best
> Michael
> 
> 
> On 12/06/2009 08:39 PM, Tom Hacohen wrote:
>> Hello,
>>
>> In response to http://wiki.openmoko.org/wiki/Opimd_redesign dos1
>> improved opimds type handling.
>> I'm sending this to shr-devel since there are many shr apps that use
>> opimd, and I also CCed the PISI devs, as they should probably change a
>> thing or two in pisi in order to support this change.
>> This change brought a lot of sanity into opimd and it's API and will let
>> us have a lot of control, and soon after, major performance improvements.
>>
>> The change is described in the following section:
>> http://wiki.openmoko.org/wiki/Opimd_redesign#Changes_in_fields
>>
>> Summary of the wiki page:
>> You now can (and should) state the type of every non generic field, for
>> instance "Phone" and "cellphone" will have the type "phonenumber" and
>> "Name", "Surname" and "Nickname" will have the type "name". "Work-Email"
>> will have the type "email" etc.
>> This will let both the UI apps and opimd itself to handle things more
>> correctly (For a more full description read the wiki page).
>> But most importantly, you should now ***DROP*** the "tel:" prefix from
>> the phone numbers fields.
>>
>> We'll provide (dos1 will write) a script that drops all the "tel:"
>> prefixes from all the fields with names that contain "phone" (case
>> insensitive) and will add the them to types.
>>
>>
>> Please ask here if there's something you don't understand.
>>
>> Although I stated it enough in the wiki page, I really think it's
>> important to make sure you understand how crucial it is to add types to
>> your opimd using apps, so please do.
>>
>> Again, a lot of thanks to dos1 that did a great job implementing those
>> changes and in a very short period of time. :P
>>
>> This change is not yet in master branch but will get there soon, so get
>> ready and wait for further notices.
>> -- 
>> Tom.
> 
> _______________________________________________
> Shr-devel mailing list
> [email protected]
> http://lists.shr-project.org/mailman/listinfo/shr-devel

_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel

Reply via email to