[Shr-Devel] [Fwd: Re: Ophonekitd step to dbus / libframeworkd-phonegui dbusification]

[Klaus 'mrmoku' Kurzmann]

Am Mittwoch 03 Juni 2009 16:01:17 schrieb Julien Cassignol:
> Addenda:
>
> Let us agree on the following "use" paradigms we want to define for
> functions:
>
> Display : which will allow the developer to display data according to
> the functional context, filtered or unfiltered, e.g. DisplayMessages,
> DisplayContacts, DisplayDialer
>
> EditXXX : which will precise the level used to view something, and
> allow to edit it, e.g. EditContact, EditMessage. This includes high
> level management such as "adding", "removing" (e.g. :
> EditContact(actionType= Add)...)
>
> These two types of actions cover a great lot of functionnalities we might
> need. Then we are left with the handling of events, I think, such as
> incoming call. Do we want to define stuff to display incoming calls
> window through dbus? Do we have a use case for such a thing, or should
> the library/ophonekitd use it as it comes? In any case, we need
> prototypes for such a thing for ophonekitd inclusion, so we might as
> well do dbus stuff too...
>
> So I'd say:
>
> HandleXXX: Handle a non user initiated event, according to type.
> HandleCall(incoming, outgoing...). HandleMessage(Incoming, sending...)
> Etc.
>
> Do these "functional" paradigms & vocabulary sound stupid to any of you?

Sound fine to me.
-- 

Klaus 'mrmoku' Kurzmann