Opimd redesign

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(→‎Changes in fields)
(→‎Changes in fields)
Line 11: Line 11:
  
 
= Changes in fields =
 
= Changes in fields =
−
ATM opimd just lets you add fields as you wish, this is bad, since you can't really categorize fields and have to use weird hacks like the "tel:" prefix.
+
'''UPDATE: What we decided to go with: (now implemented)'''
  
−
I'm suggesting a move to a configuration you'll have the following dbus methods:
+
Per backend:
−
* ListFields
+
−
* AddFiled
+
−
* DelField
+
−
* GetField
+
−
 
+
−
each field will have a type (phone number would be a type for instance) that will guide opimd on how to compare items of this type, again, in the case of phone numbers, use normalization.
+
−
 
+
−
The user of the API will be able to add fields and their types whenever he wants (and also remove such) and that will let us control opimd in a sane manner.
+
−
 
+
−
I think we also need a couple of default fields of special types:
+
−
* Phone - returns the default phone (of all the cells with type phone)
+
−
* Name - returns  "First Last, nick" or something like that.
+
−
* SIP - returns default contact info for sip
+
−
* SMS - returns default phone number for SMS etc etc.
+
−
 
+
−
This will make everything easier for the users of the API to handle and will be sane!
+
−
 
+
−
 
+
−
'''Explanation of exactly what I meant (TAsn)'''
+
−
 
+
−
/org/freesmartphone/PIM/Contacts
+
  
 
org.freesmartphone.PIM.Type.Add(name, type) <--- Adds the name and type
 
org.freesmartphone.PIM.Type.Add(name, type) <--- Adds the name and type
Line 40: Line 19:
 
org.freesmartphone.PIM.Type.List() <---- returns the list of available fields, format name:type.
 
org.freesmartphone.PIM.Type.List() <---- returns the list of available fields, format name:type.
  
−
org.freesmartphone.PIM.Type.Delete(name) <-- return nothing
+
org.freesmartphone.PIM.Type.Delete(name) <-- returns nothing
−
 
+
−
org.freesmartphone.PIM.Type.Get(name) <--- returns type
+
−
 
+
−
org.freesmartphone.PIM.Types.List() <---- returns the list of available fields, format name:type.
+
−
 
+
−
Where Types.List() returns the same thing for all the domains.
+
−
 
+
−
 
+
−
'''Next section may be outdated:'''
+
−
 
+
−
I want anyone to be able to add future types (to search by) with no special opimd handling, i.e I want to be able to add IRC although you don't know how to handle it, name of the type will be irc, type of the type will be text(limited to X chars, he should state that when making the type, or maybe unlimited if he wants) or he can also set the type to "numeric", "int" etc etc.
+
−
 
+
−
This way he'll bind a type, called "IRC" that can contain text values only, this means that if he'll want to add a field called "Main-nick" he'll be able to set the type to "irc" (the one that we set earlier) that'll let him search in all the irc nicks easily and will also let opimd know what to expect in this type. (string limited to 300 chars for instance).
+
  
 +
org.freesmartphone.PIM.Type.Get(name) <--- returns the type of the field.
  
 +
General for all of opimd:
  
−
Continuing with the IRC example I'll be able to add to the conact tom the following fields:
+
org.freesmartphone.PIM.Types.List() <---- returns the list of available types in a tuple.
  
−
Main-nick : "TAsn"
+
Types.List() returns the same thing for all the domains.
  
−
Alt-nick  : "TAsnn"
+
==API==
 +
This is the complete API (in freesmartphone docs).
 +
There are a couple of default fields, those fields can be overwritten, but if no value exists for them, they are used (also listed in the docs)
  
 +
* http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.PIM.Types.html;hb=HEAD
 +
* http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.PIM.Fields.html;hb=HEAD
  
 +
===Existing Types===
 +
# objectpath
 +
# phonenumber
 +
# address
 +
# email
 +
# name
 +
# date
 +
# uri
 +
# photo
 +
# text
 +
# longtext
 +
# boolean
 +
# timezone
 +
# generic
  
−
Though I won't be able to do that before I add the type (like this:
 
  
−
org.freesmartphone.PIM.Fields.Add("Alt-nick", "IRC")
+
How to use:
 +
You can just use opimd like you have used it until now. '''BUT''' if you want opimd to work with number resolving (or any other field handling) you should add a matching type.
 +
So let's say to add support for the "Cellphone" field, we'll just have to:
  
−
And I won't be able to do that before I do:
+
Fields.Add("Cellphone", "phonenumber")
  
−
org.freesmartphone.PIM.Types.Add("IRC", "text") (phonenumber/text/date/etc will be predefined by opimd, maybe even add a method to expose what's available there, but that can not be changed by API the "text" and etc types are set by opimd and opimd only this should probably also include the calculated type type, i.e, create a type that calculates concat(Name, SurName) or something like that, like explained in this document.)
+
or for supporting "Nickname" we'll have to:
  
 +
Fields.Add("Nickname", "name")
  
 +
This will let opimd assume things about the values inside (for instance assume that phonenumber is important and should probably be an indexed property). But also will let you (and more importantly the UI apps) work in a sane number knowing the types (and let's say, adding icons per type).
  
−
This lets the APPS to easily set types for fields and for opimd to easily know where to search (When looking for IRC), what to expect when searching (a text field, not a number that's needed to be normalized, etc).
+
The Types.List() is just for helping you know what's currently supported in opimd.
  
−
So, in our example in order to know who of the contacts posses the nick "TAsn" we'll just need to search all of the fields with the type IRC (user of the API will know to ask it). That's about it, I think.
+
As I said, you can still use fields without types, but then the apps (and opimd) will not be able to search them correctly.
  
−
I hope it's clean enough, let me know.
+
==Future development==
 +
* Enable querying by type, i.e, query where "phonenumber" = 123 will search in all the fields that have the type phonenumber.
  
 
= Changes in query method =
 
= Changes in query method =

Revision as of 21:04, 6 December 2009

STATUS UPDATE: Got mickey and dos1's agreement (they are the "leaders" of opimd). Will start (actually will help dos1) working on it asap. If you want to add anything, please add now.

This page will gather all the suggestions (and will be a decent design sketch) for the redesign of opimd. After many discussions in IRC we decided opimd needs a redesign.

Main topics that came up are: switching opimd to use sqlite for internal operations and adding configuration for types instead of the use of URIs. Many of the ideas that came up concerning the second idea are represented in this IRC log: http://pastebin.com/mb7fbf10 and in the logs from #openmoko-cdevel@Freenode on 09-10 of october 2009.

Furthermore, it has been suggested than a change in the sqlite backend db design is also needed.


Info about those changes will be shown here as soon as we'll have time to write it down.

Contents

Changes in fields

UPDATE: What we decided to go with: (now implemented)

Per backend:

org.freesmartphone.PIM.Type.Add(name, type) <--- Adds the name and type

org.freesmartphone.PIM.Type.List() <---- returns the list of available fields, format name:type.

org.freesmartphone.PIM.Type.Delete(name) <-- returns nothing

org.freesmartphone.PIM.Type.Get(name) <--- returns the type of the field.

General for all of opimd:

org.freesmartphone.PIM.Types.List() <---- returns the list of available types in a tuple.

Types.List() returns the same thing for all the domains.

API

This is the complete API (in freesmartphone docs). There are a couple of default fields, those fields can be overwritten, but if no value exists for them, they are used (also listed in the docs)

Existing Types

  1. objectpath
  2. phonenumber
  3. address
  4. email
  5. name
  6. date
  7. uri
  8. photo
  9. text
  10. longtext
  11. boolean
  12. timezone
  13. generic


How to use: You can just use opimd like you have used it until now. BUT if you want opimd to work with number resolving (or any other field handling) you should add a matching type. So let's say to add support for the "Cellphone" field, we'll just have to:

Fields.Add("Cellphone", "phonenumber")

or for supporting "Nickname" we'll have to:

Fields.Add("Nickname", "name")

This will let opimd assume things about the values inside (for instance assume that phonenumber is important and should probably be an indexed property). But also will let you (and more importantly the UI apps) work in a sane number knowing the types (and let's say, adding icons per type).

The Types.List() is just for helping you know what's currently supported in opimd.

As I said, you can still use fields without types, but then the apps (and opimd) will not be able to search them correctly.

Future development

  • Enable querying by type, i.e, query where "phonenumber" = 123 will search in all the fields that have the type phonenumber.

Changes in query method

NOTE: keep the old way, but also implement this:

I don't get why we use this querying method, it just makes everything weird hard to handle.

Furthermore, it'll be easier and faster to get only "phone number" fields for matching (in opimd), the user of the API will just be able to tell it "find me a phone_number field that matches this number" and will not force us to check each field like we do atm.

Internal design

opimd should internally use sqlite for caching as it's faster, easier to handle and generally better.

Query improvements

It should really be possible to ask opimd for several contacts at once, i.e ask him for the contacts "Tom, dick and harry" or for the numbers "123, 435 and 546546" at one query, because querying opimd for 70 different contacts at one time (phonelog) is terribly slow.

Furthermore it should be able to ask for a "join" of backends when requesting from one. i.e, I want to be able to ask opimd for the messages and the corresponding contacts for each message in one query, or even ask opimd for all the messages that match all the numbers from the contact "Charley".

Query reply should be possible to sort differently depending on the national character encoding.

Retrieved from "http://openmoko.org/index.php?title=Opimd_redesign&oldid=77955"
Personal tools

STATUS UPDATE: Got mickey and dos1's agreement (they are the "leaders" of opimd). Will start (actually will help dos1) working on it asap. If you want to add anything, please add now.

This page will gather all the suggestions (and will be a decent design sketch) for the redesign of opimd. After many discussions in IRC we decided opimd needs a redesign.

Main topics that came up are: switching opimd to use sqlite for internal operations and adding configuration for types instead of the use of URIs. Many of the ideas that came up concerning the second idea are represented in this IRC log: http://pastebin.com/mb7fbf10 and in the logs from #openmoko-cdevel@Freenode on 09-10 of october 2009.

Furthermore, it has been suggested than a change in the sqlite backend db design is also needed.


Info about those changes will be shown here as soon as we'll have time to write it down.

Changes in fields

UPDATE: What we decided to go with: (now implemented)

Per backend:

org.freesmartphone.PIM.Type.Add(name, type) <--- Adds the name and type

org.freesmartphone.PIM.Type.List() <---- returns the list of available fields, format name:type.

org.freesmartphone.PIM.Type.Delete(name) <-- returns nothing

org.freesmartphone.PIM.Type.Get(name) <--- returns the type of the field.

General for all of opimd:

org.freesmartphone.PIM.Types.List() <---- returns the list of available types in a tuple.

Types.List() returns the same thing for all the domains.

API

This is the complete API (in freesmartphone docs). There are a couple of default fields, those fields can be overwritten, but if no value exists for them, they are used (also listed in the docs)

Existing Types

  1. objectpath
  2. phonenumber
  3. address
  4. email
  5. name
  6. date
  7. uri
  8. photo
  9. text
  10. longtext
  11. boolean
  12. timezone
  13. generic


How to use: You can just use opimd like you have used it until now. BUT if you want opimd to work with number resolving (or any other field handling) you should add a matching type. So let's say to add support for the "Cellphone" field, we'll just have to:

Fields.Add("Cellphone", "phonenumber")

or for supporting "Nickname" we'll have to:

Fields.Add("Nickname", "name")

This will let opimd assume things about the values inside (for instance assume that phonenumber is important and should probably be an indexed property). But also will let you (and more importantly the UI apps) work in a sane number knowing the types (and let's say, adding icons per type).

The Types.List() is just for helping you know what's currently supported in opimd.

As I said, you can still use fields without types, but then the apps (and opimd) will not be able to search them correctly.

Future development

  • Enable querying by type, i.e, query where "phonenumber" = 123 will search in all the fields that have the type phonenumber.

Changes in query method

NOTE: keep the old way, but also implement this:

I don't get why we use this querying method, it just makes everything weird hard to handle.

Furthermore, it'll be easier and faster to get only "phone number" fields for matching (in opimd), the user of the API will just be able to tell it "find me a phone_number field that matches this number" and will not force us to check each field like we do atm.

Internal design

opimd should internally use sqlite for caching as it's faster, easier to handle and generally better.

Query improvements

It should really be possible to ask opimd for several contacts at once, i.e ask him for the contacts "Tom, dick and harry" or for the numbers "123, 435 and 546546" at one query, because querying opimd for 70 different contacts at one time (phonelog) is terribly slow.

Furthermore it should be able to ask for a "join" of backends when requesting from one. i.e, I want to be able to ask opimd for the messages and the corresponding contacts for each message in one query, or even ask opimd for all the messages that match all the numbers from the contact "Charley".

Query reply should be possible to sort differently depending on the national character encoding.