Hello folks,
I tried to summarize the discussion we had about the new API for
libframeworkd-phonegui.
This mail is only a sum-up and in a few days, if all seems ok, I will
suggest an API.
First, we discussed about "session-based" and "one-method call".
It seems that we will first keep it simple and only create the screen
and let them do whatever they like until they send an event to the
framework or the caller. Way 2, then.
Then, there are several functionnal contexts:
-Dialer
-Call
-Contacts
-Messages
-Tasks
-Phonelog
(More to come)
Now, we need to agree on names.
Julien proposed name conventions for the functions and it was commented:
(XXX is the name of the context)
DisplayXXX for displaying a simple screen. When a list is to be
displayed, the function can take a filter as argument.
SelectXXX for displaying a screen that will (asynchronously) return a
selection (ie. the dialer will call SelectContacts)
CreateXXX is self-explaining. The screens may receive informations to
pre-fill the "create" form, if any.
EditXXX for screens that will edit informations. These screens should
receive a pointer to the object that should be modified. (I couldn't
find any use case where a Delete screen could be useful, so I didn't put
DeleteXXX)
Now, what screens and calls do we need; what functionnal need should
they answer ? Here is a minimal set
Dialer:
- Show the dialer
- with a pre-filled number
Call:
- Show an incoming call
- Show a running call
Contacts:
- Show a contact
- Show the list of contacts (for simple display or selection, see above)
- based on a filter
- Show a screen for adding a contact
- prefilled (either the name, the number, or any other field we
could imagine)
- Show a screen for editing a contact
Messages:
- Show a message
- Show the list of messages (for simple display or selection, see above)
- based on a filter
- Show a screen for writing a message
- prefilled (either the message, the number(s), or any other
field we could imagine)
Tasks:
- Show a Calendar/Todo/<fill in the blank>
- Show the list of calendars/todos/...
- based on a filter
- Show a screen for editing a calendar/todo/...
- Show a screen for adding a contact
- prefilled
Phonelog:
- Show the list of calls
- filtered
How do you feel about it ? I hope I got everybody's point; If I missed
some use cases, please suggest :)
Don't foget that we now have to focus on what is missing, pinpoint what
is unclear and then on the API itself.
Deubeuliou
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
