On Di, 2011-03-29 at 20:47 +0100, Robin Burchell wrote:
> On Tue, Mar 29, 2011 at 7:59 PM, <[email protected]> wrote:
> > If we agreed to handle libcommhistory by indexing contacts to tracker, then
> > eventually IM/VoIP contacts could continue staying in tracker as well and
> > everything would continue working via libcommhistory.
>
> I don't mean to throw fuel on the fire, but I have to re-ask something
> which was hinted at by Arjan earlier (I think): does anything actually
> use libcommhistory yet?
The dialer in Handset would be the obvious candidate. But when Shane
tried to use libcommhistory for dialer, it did not work for him and
therefore he kept the current approach (QSettings as storage). I don't
know whether bugs were filed; if not, then probably because it looked
like work in progress which would be fixed eventually anyway. I also
asked about UI features and designs which explicitly depend on features
offered by libcommhistory. Shane wasn't aware of any.
So in a nutshell, libcommhistory is not used in MeeGo as far as I know,
and therefore not having it working for a while until it is really
needed is acceptable.
<offtopic>
Obviously I'm not succeeding with keeping this thread on topic ;-} So
here are some of my own thoughts on the meta aspect:
* In the past, meego.com was a dumping ground for technology
developed and used elsewhere. Often it wasn't properly tested
there. I have heard arguments that this testing can't be done
without the apps in MeeGo using the middleware. IMHO this is
just a lame excuse for not doing proper QA on middleware
compoments, and leads to situations as with
Dialer/libcommhistory were an app developer would have to stop
working on his main task to investigate problems in someone
else's code. Not cool.
* Now the situation is hopefully different, but still, the focus
has to be on the code which really is needed. "You can do
anything you set your mind to when you have vision,
determination, and an endless supply of expendable labor." -
http://despair.com/achievement.html. We don't have that endless
supply of expendable labor, so work needs to be prioritized. Of
course that doesn't stop anyone from doing whatever he wants in
his own time.
The current planning for EDS focuses on core features, PIM storage.
There are ideas how the rest of the features could be added again in a
MeeGo based on EDS, and for me that is good enough to go ahead with
improving EDS first. One has to start somewhere. Boiling the ocean
hardly ever succeeds.
</offtopic>
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
