Re: [GnomeMeeting-devel-list] [DRAFT] Organization of the "find contact" task

[Julien PUYDT <jpuydt free fr>]

Damien Sandras a écrit :
> > we only know that view is a GtkWidget*, source a GmSource* and book a 
> > GmBook*, but still we'll have a nice display!
>
> Well, what if you have 2 views? (in terms of API).

Well, the "find contact" window must not know the details of what it 
manages, and hence gets a default view for each book type.

But the rest of the code can still access the books directly. For 
example the DBUS component will directly access the call history to 
export it (which is some sort of a view!).

> > > I think it should be a prerequisite. Searching has to be done
> > > transparently, without having to take care of where we are searching.
> > > Look at how KAddressbook or Evolution-Data-Server are doing things. You
> > > have several types of address books, but the API is the same for all of
> > > them.
> > Do they show presence ? Do they have to care if a contact has an 
> > authorize/revoke action ?
> >
> > Tell me just one thing that you could put in GmContact and would work 
> > for all types of contacts.
> Tell me just one thing that you could not put in GmContact and that
> wouldn't work for one type of contact.

The calling url, because not all contacts may be callable. Worse even, I 
may be callable when using one client, and not when using another!

> >  >
> > > Such code would be bad. I'm really not convinced by this part of your
> > > approach.
> > It isn't ; I sent you some sample code.
>
> The sample code is not doing anything very useful yet.

Indeed, it shows things.

> If we want to discuss further, please show me sample code that :
> - Search for "Damien Sandras" in all types of address books and returns
> a list of results

Cannot be done : not all contacts may have names attached to them. 
Notice that it isn't possible yet.

> - Imagine we have a callback triggered when some action is triggered on
> the contact allowing to call him. Please show me the sample code of that
> callback.

Actions are what I want to work on now that I think the view side is 
covered.

Snark