On Mo, 2011-06-06 at 11:02 +0100, Dumez, Christophe wrote:
>
> I understood from Patrick's earlier comments, that the EDS
> change would "just work" without the need to patch Qt
> mobility. Does not seem to case now?
>
> Patrick was hoping it would be possible to use EDS by default without
> patching qt-mobility. I looked into it but it does not seem to be
> possible (It explicitly uses tracker in the project file and the code
> would fallback to the "memory" backend if tracker is not installed).
> So patching qt-mobility seems to be the way to go (it is just a
> compile-time DEFINE is a project file).
The approach that I suggested after Chris found this snag is the
following:
* QtMobility will be compiled with QtContacts-EDS as default
engine, to ensure that it is used when multiple engines are
installed (already done in devel:meego-ux). This is the kind of
preferred treatment that Tracker enjoyed so far.
* The memory engine will be packaged separately and thus not be
installed by default (not done yet).
That way it is possible to switch back and forth between EDS and Tracker
without recompiling QtMobility or apps:
* To use Tracker, ensure that it is the only installed engine.
* To use EDS, install QtContacts-EDS.
One (unlikely) downside is that the memory backend will not be installed
anymore. That might be even be an advantage (smaller images) because I
don't think anyone really needs it (more a proof-of-concept than a real
engine?!).
Explicitly picking a manager of course always works in apps.
--
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
