Re: [MeeGo-dev] SF2011 BoF notes: Reinvigorating MeeGo Netbook
On Do, 2011-06-23 at 19:58 +0200, Carsten Munk wrote: § Sync Functionality □ We are missing the whole connected device options in MeeGo - need to be able to connect to the Cloud to get to my own data and other devices As someone who has worked on sync, the obvious question is: which parts of the cloud? The term is, well, a bit fluffy and vague... Note that some parts of the Cloud, some data and some other devices already work with SyncEvolution: * SyncML servers + contacts, events, tasks, notes * SyncML-capable peers (which includes MeeGo devices that run SyncEvolution + obexd) + contacts, events, tasks, notes * CalDAV/CardDAV servers + contacts + events (in MeeGo 1.2 update resp. 1.3) * ActiveSync servers + contacts, events, tasks, notes (code written in SyncEvolution, untested and in progress) It would be nice if additional protocols were supported. For example, Google's SyncML support is rudimentary (only a subset of the supported data mapped to the vCards in SyncML); using their gdata protocol would probably work better. But that depends on people helping with the development instead of just waiting for it to happen. -- 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 MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] qml components
Hi, how to use qml components within QtSDK to develop with N900 Meego community edition. N. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] qml components
Instructions and packages will be provided at later time. On Fri, Jun 24, 2011 at 4:05 AM, nic...@nicoladefilippo.it nic...@nicoladefilippo.it wrote: Hi, how to use qml components within QtSDK to develop with N900 Meego community edition. N. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Problem in chroot Environment
Hi all, I created my own image by taking .ks file from http://download.meego.com/MeeGo/snapshots/testing/1.2.0/1.2.0.90.0.20110517.82/images/meego-tablet-ia32-mfld/ Modified repos to repo --name=1.2-oss --baseurl= http://download.meego.com/MeeGo/snapshots/testing/1.2.0/1.2.0.90.0.20110517.82/repos/oss/ia32/packages/--save --debuginfo --source --gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego repo --name=1.2-non-oss --baseurl= http://download.meego.com/MeeGo/snapshots/testing/1.2.0/1.2.0.90.0.20110517.82/repos/non-oss/ia32/packages/--save --debuginfo --source --gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego After successfully creating the image, chrooted to it sudo mic-chroot ./tablet/ Now I am facing two prblems: zypper install meego-simulator-launcher-handset Problem: meego-simulator-launcher-handset-1.0.4-1.1.i586 requires mesa-libEGL, but this requirement cannot be provided uninstallable providers: mesa-libEGL-7.9.1-8.3.i586[1.2-oss] Solution 1: Following actions will be done: deinstallation of pvr-bin-mdfld-5.3.0.0041-2.2.i586 deinstallation of psb-video-mdfld-5.3.0.0041-2.2.i586 Solution 2: do not install meego-simulator-launcher-handset-1.0.4-1.1.i586 Solution 3: break meego-simulator-launcher-handset by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): (II) startmeego bash: startmeego: command not found Can some one please point me what got wrong. Appreciate your help in advance. Thanks, Kalinga ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines