Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

Then is it possible that MeeGo could provide some API to differentiate different UX? From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of ext Thiago Macieira [thi...@kde.org] Sent: Wednesday, December 15, 2010 9:30 PM To: meego-dev@

[MeeGo-dev] How to create image that has installed whole debuginfo rpms?

Dear all, I would like to see all system debug messages. Is there any way to create image that has installed whole debuginfo rpms? For example, if I use "rpm -qa | grep kernel", then I can see kernel-n900-2.6.35.3-10.3.armv7l.rpm and kernel-n900-debuginfo-2.6.35.3-10.3.armv7l.rpm. Thanks.

Re: [MeeGo-dev] Do any one know daemon is fail in ohm package

I believe currently not all necessary packages of OHMng are in the image, especially the rule sets. And the rule sets are critical for ohmd to run. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of JK Sent: Thursday, December 16, 2010 10:30 AM To: MeeGo-dev@meeg

[MeeGo-dev] Do any one know daemon is fail in ohm package

Hi, I use newly 12/14 netbook image to run ohmd. It always a error at daemon(0,0) return -1 in init stage. How to solve this daemon(0,0) ? Thanks, ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Fwd: [MeeGo-touch-dev] Target specification in meegotouch reference UX gconf

On Tue, 14 Dec 2010 16:58:34 -0700 Eugene Seah wrote: > Since this goes into some gconf setting in meego... trying meego-dev > as well, does anyone know how the target "device profile" gets > specified post 1.1? This is now set in the gconf key /meegotouch/target/name If this is not set, then t

Re: [MeeGo-dev] Application Icon not visible in Application list : MeeGo 1.1

On Wed, 15 Dec 2010 16:12:23 +0100 Dave Neary wrote: > Hi, > > Thiago Macieira wrote: > > The entire hierarchy of /usr/share/applications should be searched. > > The subdirs are simply an organisation trick. > > > > hildon/example.desktop is tracked as if it were > > hildon-example.desktop. >

[MeeGo-dev] MIC-image-creator failure on Ubuntu, latest weekly N900 KS

Hi, We're getting a new failure on Ubuntu mic-image-creator 0.22.2 with the latest N900 KS, that did not occur before... errors look like this: Installing: filesystem # [ 2/551] error: unpacking of archive failed on file /boot: cpio: chown ... Instal

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of >ext Thiago Macieira >[thi...@kde.org] >Sent: Wednesday, December 15, 2010 9:30 PM >To: meego-dev@meego.com >Subject: Re: [MeeGo-dev] Writing code in Qt for MeeGo platform > >On W

[MeeGo-dev] Does any one know how to test the sensors on Moorestown platform?

Hi, I have Meego-1.1 running on Moorestown platform. I could see, one sensor daemon running once board boots up. I tried to run the test apps which comes with sensorfw-0.6.19.p.git82de2729-2.38.src.rpm package. When I tried to run test app, I got the logs mentioning only ALS sensor is up. So I trie

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: Yes, we've seen this happen with previous hardware where we are stuck with 2.6.22 and a kernel config that clashes with newer udev. That's the moment where we either find a way to patch in the needed feature or say 'tough luck, no cookie for us'. I

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

2010/12/15 Arjan van de Ven > On 12/15/2010 11:28 AM, Carsten Munk wrote: > >> 2010/12/15 Thomas B. Ruecker > dm8...@openaos.org>> >> >> >>On Wed, Dec 15, 2010 at 09:47:33AM -0800, Arjan van de Ven wrote: >>> On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: >>>> Now at least Nokia for

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

On Wednesday, 15 de December de 2010 14:19:00 Bernd Stramm wrote: > This seems to be the current situation, applications take a wild guess > to decide what they are running on. > > This means different applications take different guesses. > > It would be really really nice if there was a better w

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 11:28 AM, Carsten Munk wrote: 2010/12/15 Thomas B. Ruecker > On Wed, Dec 15, 2010 at 09:47:33AM -0800, Arjan van de Ven wrote: > On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: >> Now at least Nokia for the N900 provides a much newer kernel

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

2010/12/15 Thomas B. Ruecker > On Wed, Dec 15, 2010 at 09:47:33AM -0800, Arjan van de Ven wrote: > > On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: > >> Now at least Nokia for the N900 provides a much newer kernel for MeeGo, > >>> so those of us who own N900's are in good shape, but the conflict

Re: [MeeGo-dev] MeeGo migration path?

On 12/15/10 05:14, Wichmann, Mats D wrote: meego-dev-boun...@meego.com wrote: Em Terça-feira, 14 de Dezembro de 2010, às 16:45:28, Jechlitschek, Christoph escreveu: Hi all, I was wondering if there exists a migration path from MeeGo 1.0 to MeeGo 1.1 and later to MeeGo 1.2. This is very interest

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On Wed, Dec 15, 2010 at 09:47:33AM -0800, Arjan van de Ven wrote: > On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: >> Now at least Nokia for the N900 provides a much newer kernel for MeeGo, >>> so those of us who own N900's are in good shape, but the conflict I'm >>> trying to point out is real...

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

On Wed, 15 Dec 2010 20:35:35 +0200 "Ville M. Vainio" wrote: > On Wed, Dec 15, 2010 at 8:28 PM, Andrew Flegg wrote: > > >> May be best choice is to make app UI using Qml / Qt Components and > >> load right Qml file depending what UX you would like to have > > > > And how does an app determine th

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

On Wed, Dec 15, 2010 at 8:28 PM, Andrew Flegg wrote: >> May be best choice is to make app UI using Qml / Qt Components and load >> right Qml file depending what UX you would like to have > > And how does an app determine that? It can't use #ifdef, as discussed above. It can determine this at run

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

On Wed, Dec 15, 2010 at 15:56, wrote: > > May be best choice is to make app UI using Qml / Qt Components and load > right Qml file depending what UX you would like to have And how does an app determine that? It can't use #ifdef, as discussed above. Cheers, Andrew -- Andrew Flegg -- mailto:an

Re: [MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On 12/15/2010 9:26 AM, Thomas B. Ruecker wrote: Now at least Nokia for the N900 provides a much newer kernel for MeeGo, so those of us who own N900's are in good shape, but the conflict I'm trying to point out is real... and there will be a point where, even if you ignore the hard compliance top

Re: [MeeGo-dev] compass sensor plugin

I can see the status page using this URL from inside Intel, but it is not accessible from outside Intel as Dave has indicated. For internal releases it sounds correct but should not be restricted on released versions of MeeGo since the greater community can aid in problem solving these issues.

[MeeGo-dev] Community hardware adaptations (Was: Comments on proposed kernel policy)

On Wed, Dec 15, 2010 at 07:02:17AM -0800, Arjan van de Ven wrote: > On 12/14/2010 10:53 PM, Thomas B. Ruecker wrote: >> >>> I don't see the difference between a vendor maintaining a kernel package >>> and a community of people maintaining a kernel package >> Being involved in a relatively small

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of >ext Thiago Macieira >[thi...@kde.org] >Sent: Wednesday, December 15, 2010 5:51 PM >To: meego-dev@meego.com >Subject: Re: [MeeGo-dev] Writing code in Qt for MeeGo platform > >On

Re: [MeeGo-dev] Writing code in Qt for MeeGo platform

On Wednesday, 15 de December de 2010 15:13:51 Stylianou, Costas wrote: > Hi, > Is there a way to differentiate for the MeeGo platform when writing code in > Qt? No. MeeGo is standard X11. > > E.g. if writing for Symbian, we can use > #ifdef Q_OS_SYMBIAN > or >

[MeeGo-dev] Writing code in Qt for MeeGo platform

Hi, Is there a way to differentiate for the MeeGo platform when writing code in Qt? E.g. if writing for Symbian, we can use #ifdef Q_OS_SYMBIAN or #ifdef Q_WS_S60 in my source code. And I can use: symbian { symbia

Re: [MeeGo-dev] Application Icon not visible in Application list : MeeGo 1.1

Hi, Thiago Macieira wrote: > The entire hierarchy of /usr/share/applications should be searched. The > subdirs are simply an organisation trick. > > hildon/example.desktop is tracked as if it were hildon-example.desktop. Interesting! How do you explain that moving the .desktop file to /usr/shar

Re: [MeeGo-dev] Comments on proposed kernel policy

On 12/14/2010 10:53 PM, Thomas B. Ruecker wrote: I don't see the difference between a vendor maintaining a kernel package and a community of people maintaining a kernel package Being involved in a relatively small OSS community around Archos portable media players I can tell you that it ma

Re: [MeeGo-dev] how to run connman test script?

Hi, On Wed, Dec 15, 2010 at 07:21:34PM +0530, Karthick wrote: > Hi, > > I have installed connman-test package which has python test script > executables on meego running device. > when i ran those executable, i was getting error like > Usuage: ./backtrace [binary] [log] If you're looking at the b

[MeeGo-dev] how to run connman test script?

Hi, I have installed connman-test package which has python test script executables on meego running device. when i ran those executable, i was getting error like Usuage: ./backtrace [binary] [log] I don't know what argument i have to give while ran those executable. Even i couldn't find any docum

Re: [MeeGo-dev] MeeGo migration path?

meego-dev-boun...@meego.com wrote: > Em Terça-feira, 14 de Dezembro de 2010, às 16:45:28, Jechlitschek, > Christoph escreveu: >> Hi all, >> I was wondering if there exists a migration path from MeeGo 1.0 to >> MeeGo 1.1 and later to MeeGo 1.2. This is very interesting for >> companies that have dev

[MeeGo-dev] symlink package missing form Trunk

Hi, I would like to use the symlink utility[1] for my package building, it is available in MeeGo 1.0 core and MeeGo 1.1 core, but not in Trunk/Trunk-Testing... what is the reason for that? If there is a replacement for it, what's the name? thx and br Reto [1] https://build.meego.com/package

Re: [MeeGo-dev] Application Icon not visible in Application list : MeeGo 1.1

Em Terça-feira, 14 de Dezembro de 2010, às 22:37:16, Dave Neary escreveu: > > /usr/share/applications/hildon/.desktop > > Are you sure that this directory is searched for .desktop files on MeeGo? > [snip] > > The presence of "hildon" in the path looks suspicious to me, in any case... The entire hi

Re: [MeeGo-dev] compass sensor plugin

> -Original Message- > From: Dave Neary [mailto:nea...@gmail.com] On Behalf Of Dave Neary > Sent: Wednesday, December 15, 2010 10:58 AM > To: Lemoine, Philippe > Cc: Jia-Chi Lai; meego-dev@meego.com > Subject: Re: [MeeGo-dev] compass sensor plugin > > > > Lemoine, Philippe wrote: > > You

Re: [MeeGo-dev] compass sensor plugin

Lemoine, Philippe wrote: > You can check latest status on : BMC 8649 > http://bugs.meego.com/show_bug.cgi?id=8649 "You are not authorized to access bug #8649." :( Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org __

Re: [MeeGo-dev] compass sensor plugin

> -Original Message- > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On > Behalf Of Jia-Chi Lai > Sent: Wednesday, December 15, 2010 6:47 AM > To: meego-dev@meego.com > Subject: [MeeGo-dev] compass sensor plugin > > hi~~ > > > Sensorfw can not load the compass sens

[MeeGo-dev] [PATCH] a patch to quickly support component summary feature

Sorry to forget the attaches For resolving the Bug#9922, I made a patch to quickly support component summary. Please check the enclosed file, and help to review it. Any comments are warmly welcome. Why we want to change made? A brief summary/comments

Re: [MeeGo-dev] Packaging the MeeGo stack on Debian - Use the name ?

On 12/12/10 23:30, David Greaves wrote: I'm cc'ing th meego-community list as I think there are a lot of people there who are having similar conversations. On 09/12/10 19:12, Ibrahim Haddad wrote: > The MeeGo Project members devoted quite a bit of time discussing these > questions to make sure

[MeeGo-dev] [PATCH] a patch to quickly support component summary feature

For resolving the Bug#9922, I made a patch to quickly support component summary. Please check the enclosed file, and help to review it. Any comments are warmly welcome. Why we want to change made? A brief summary/comments is necessary in the test repor