Re: New addressbook backend.


> Yeah, I'm saying there may be backends which want to return matches
> which have different categories.

I wondered about this, but figured that it was pretty unlikely that a
single backend would have multiple categories of match.  Not a problem to
change internally, though.

> Getting the frontend to structure the cluepacket is part of the
> problem.  Maintaining that structure information as you pass the
> cluepacket around, chain the clues, and find matches is another part.
> They are both important.

Do you still want the frontend and cluepacket information available to
each match when it's in the engine, or just when it's being gathered from
the backend?  The former is currently in the code, the latter is not a
problem to implement but in this case we're starting to hold an awful lot
of information for each match, especially if there has been extensive
cluechaining going on.  I'm not sure that a match, once it has been
processed and inserted in to the display list, needs that much context,
but if you think it does then fair enough.
   I have implemented the fixes that we've been talking about here, so
   I'll dump them into CVS once 0.1 has been finalised.  In the meantime
   I'll put together another patch this weekend so that people can see
   what's going on.
> Nat

Jim McDonald - Jim mcdee net

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]