[MeeGo-dev] [ANNOUNCE] New release 0.22 of spectacle

[Jian-feng Ding]

Hi, all

New release 0.22 of spectacle is available now.

New features and fixings:

   - Enhanced arch namespace support, more precise expand values for arm
   ix86 => "%{ix86}"
   arm => "%{arm}"
   armv5 => "armv5el armv5tel armv5tejl"
   armv7 => "armv7el armv7tel armv7l armv7hl armv7nhl"
   - "autogen" as the "Configure" will run "./configure automatically
   - More friendly warning message for YAML syntax errors (BMC#11262, BMC#11766)
   - Data file GROUPS and pkgconfig-provides.csv were updated to latest
   - No keyword "NoIconCache" to avoid inserting 'gtk-update-icon-cache' lines
   - Let keyword "Description" to be mandatory and more strict checking
   - And the following bugs were fixed:
 - BMC#10495: handling of tarfile and its filename
 - BMC#11166: Added missing initialize extra flags for AutoSubPackages
 - BMC#11619: skip %exclude files in when it parse extras from filelists
 - BMC#12975: need not gtk-update-icon-cache for Qt based pkg
 - BMC#12235: crash with subpkg without Name
 - BMC#12720: crash with empty %files section in .spec
 - BMC#11661: more generic services files matching

The packages of all the supported Linux distros can be found in the repos:
http://repo.meego.com/MeeGo/tools/repos

Useful links:
Git: git://gitorious.org/meego-developer-tools/spectacle.git
Home: http://meego.gitorious.org/meego-developer-tools/spectacle
Wiki: http://wiki.meego.com/Spectacle

Bugzilla section in bugs.meego.com:
Product: Development Tools
Component: Packaging Tools

Regards,
jf.ding
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] package install cause the screen orientation can't work

[Jia-Chi Lai]

hi~

I build the  qt-mobility package on OBS and install the rpm files of the
package.
then I launch the setting application but the screen orientation can't work.

I also build orientation-contextkit-sensor package and install it.
the home screen can't launch

Are there any trick of install those rpm?? why the screen orientation can
not work after I install the rpm built by myself??

thanks.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] mic-image-creator dies with message 'No such file or directory: '/var/cache/meego-bootstrap/usr/bin/mic''

[Teabag Meego]

Hello All,

I failed to create image using MIC2 with the following command:

sudo mic-image-creator --config=meego-netbook-ia32-1.1.ks --format=raw 
--cache=mycache

I always get the below error:

...
...
Installing rpm...
Installing rpm-python...
Installing libxml2...
Installing yum-metadata-parser...
Installing yum...
Installing mic2...
Installed total of 133 packages to bootstrap located in 
/var/cache/meego-bootstrap.
Traceback (most recent call last):
  File "/usr/local/bin/mic-image-creator", line 949, in 
    ret = main()
  File "/usr/local/bin/mic-image-creator", line 743, in main
    imgcreate.bootstrap.check_mic(options.bootstrap)
  File "/usr/lib/pymodules/python2.6/mic/imgcreate/bootstrap.py", line 639, in 
check_mic
    copy_mic2(bootstrap, bin_path = bin_path, python_lib_path = pythonlib)
  File "/usr/lib/pymodules/python2.6/mic/imgcreate/bootstrap.py", line 608, in 
copy_mic2
    os.unlink(bootstrap + "/usr/bin/mic")
OSError: [Errno 2] No such file or directory: 
'/var/cache/meego-bootstrap/usr/bin/mic'


My environment is Ubuntu 10.04,  mic2 version - 0.22.13.
The kickstart file used is:

http://repo.meego.com/MeeGo/releases/1.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.ks

Can anyone suggest what is going wrong here and what can I do to fix this? 

Thanks.







  ___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] does the mcompositor support xrandr setting?

[Chen, Jacob]

Hi here,

I have a netbook which installed with a handset image.
On the netbook, I installed an external display and used xrandr to set the 
external display as an extended screen which on the right of the local display 
by below command.
# xrandr --output VGA1 --auto --right-of LVDS1

I ran the xrandr without parameter and get the result:
--
Screen 0: minimum 320 x 200, current 2304 x 1024, maximum 4096 x 4096
LVDS1 connected 1024x600+0+0 (normal left inverted right x axis y axis) 223mm x 
125mm
   1024x600   60.0*+
   800x60060.3 56.2  
   640x48059.9  
VGA1 connected 1280x1024+1024+0 (normal left inverted right x axis y axis) 
376mm x 301mm
   1280x1024  60.0*+   75.0  
   1152x864   75.0  
   1024x768   75.1 60.0  
   800x60075.0 60.3  
   640x48075.0 60.0  
   720x40070.1  


I wrote a simple program to create a window with setting CWOverrideRedirect 
flag and set the position to (1024, 0) intend to show the window on the 
external display.

I got the result as :
On the external screen, I can see X cursor but the window.

**I tried only run X without mcompositor, the window can show properly.

My question is, does mcompositor support xrandr setting?


Regards,
Jacob
___
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] tablet release...

[Dan Leinir Turthra Jensen]

On Wednesday 02 Mar 2011 06:28:22 Sousou, Imad wrote:
> Hi everyone... I know there are a lot of questions about the open sourcing
> of the meego tablet pre-alpha that was shown couple of weeks ago... I just
> want to let you know that we are planning on open sourcing the tablet UX
> code in the next few weeks.  This was planned to go open source at the
> same time we showed it, but given few complications, we had to delay this
> a bit... -imad

  Thanks! That's some brilliant news there :) Is there any reason this was not 
mentioned on the list? Presumably it was a case of being busy, forgetting or a 
similar excuse, i'm just interested in knowing why, with no wish to 
incriminate anybody - knowing that you do plan to open it up is good :) i know 
how attached you get to code, and how unwilling you can get at times to 
release code that you're not happy with the aesthetics of :)

-- 
..Dan // Leinir..
http://leinir.dk/

  Co-
existence
  or no
existence

  - Piet Hein
___
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] does the mcompositor support xrandr setting?

[Max Waterman]

On 03/02/2011 12:13 PM, Chen, Jacob wrote:


My question is, does mcompositor support xrandr setting?


I am pretty confident from other discussions that it does not, but in 
order to find something to back it up, I used a search engine for 
'mcompositor' and 'xrandr'.


It seems to back up my assertion :



I hope it answers your question.

Max.
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[sakari.poussa]

On 02/03/11 9:51 AM, "ext Ville M. Vainio"  wrote:

>On Wed, Mar 2, 2011 at 1:13 AM, Gabriel M. Beddingfield
> wrote:
>
>> On Tue, 1 Mar 2011, Victor Vu wrote:
>>
>>> Is MeeGo Touch Framework here to stay?
>>
>> Yes.
>
>Is this based on some new information that hasn't been shared
>elsewhere? MTF is widely understood to be deprecated for third party
>use.

Yes. That is the case. More specifically, the MTF widgets will be
deprecated for 3rd party use.

>
>Of course Intel may have more ambitious plans for MTF than Nokia did,
>but from where I'm looking at it Qt Quick still seems to be the
>future.

QML and Qt components are the future toolkit and APIs.

-sakari 

>___
>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

Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Gabriel M. Beddingfield]

On Wednesday, March 02, 2011 01:51:51 am Ville M. Vainio 
wrote:
> On Wed, Mar 2, 2011 at 1:13 AM, Gabriel M. Beddingfield
> 
>  wrote:
> > On Tue, 1 Mar 2011, Victor Vu wrote:
> >> Is MeeGo Touch Framework here to stay?
> > 
> > Yes.
> 
> Is this based on some new information that hasn't been
> shared elsewhere? MTF is widely understood to be
> deprecated for third party use.

The OP's question didn't specifically ask about 3rd party 
use.  However, if you read the rest of my e-mail... I *did* 
add a very strong indication that it's deprected for 3rd 
party use.

However, the MTF includes things like mcompositor, 
mdecorator, duicontrolpanel, etc...  These are fundamental 
parts of the Handset UX, the IVI UX, and the Tablet UX.  So, 
if the MTF is scheduled for termination... then I missed a 
memo somewhere.

-gabriel
___
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] does the mcompositor support xrandr setting?

[Hämäläinen Kimmo]

On Wed, 2011-03-02 at 18:13 +0800, ext Chen, Jacob wrote:
...
> My question is, does mcompositor support xrandr setting?

As Max said, it does not support it.  But it should be quite easy to
add. It would be enough to track ConfigureNotifys for the root window
--- since its size changes when XRandR rotates, and recreate the
offscreen pixmaps in this case.

If somebody is willing to look at it, please send your merge request
against the 'staging' branch of
http://meego.gitorious.org/meegotouch/meegotouch-compositor

The Nokia phone we are working on does not support XRandR so the support
is not done yet.

-Kimmo 

> 
> 
> Regards,
> Jacob
> ___
> 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

Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Thiago Macieira]

On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote:
> However, the MTF includes things like mcompositor,
> mdecorator, duicontrolpanel, etc...  These are fundamental
> parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
> if the MTF is scheduled for termination... then I missed a
> memo somewhere.

You're right: before it can be terminated, an alternative needs to come along.

My guess (and it's a guess!) is that we'll see these things move away when 
Wayland moves in.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Arjan van de Ven]

On 3/2/2011 4:52 AM, Gabriel M. Beddingfield wrote:

On Wednesday, March 02, 2011 01:51:51 am Ville M. Vainio
wrote:

On Wed, Mar 2, 2011 at 1:13 AM, Gabriel M. Beddingfield

  wrote:

On Tue, 1 Mar 2011, Victor Vu wrote:

Is MeeGo Touch Framework here to stay?

Yes.

Is this based on some new information that hasn't been
shared elsewhere? MTF is widely understood to be
deprecated for third party use.

The OP's question didn't specifically ask about 3rd party
use.  However, if you read the rest of my e-mail... I *did*
add a very strong indication that it's deprected for 3rd
party use.


yeah don't use MTF in your own applications.

However, the MTF includes things like mcompositor,
mdecorator, duicontrolpanel, etc...


We're "stuck" with mcompositor for now, but many of these other items 
are very aggressively being worked on in terms of removing

them as soon as possible (some even for 1.2)

___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Gabriel M. Beddingfield]

On Wed, 2 Mar 2011, Arjan van de Ven wrote:


However, the MTF includes things like mcompositor,
mdecorator, duicontrolpanel, etc...


We're "stuck" with mcompositor for now, but many of these 
other items are very aggressively being worked on in terms 
of removing them as soon as possible (some even for 1.2)


Thank you.

This is news to me.  Is there a roadmap somewhere?  And if 
someone wanted to track this sort of thing (MTF, Handset UX, 
Tablet UX) -- where should he be hanging out?


-gabriel

___
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] package install cause the screen orientation can't work

[Rusty Lynch]

On 03/02/2011 12:50 AM, Jia-Chi Lai wrote:

hi~
I build the  qt-mobility package on OBS and install the rpm files of 
the package.
then I launch the setting application but the screen orientation can't 
work.

I also build orientation-contextkit-sensor package and install it.
the home screen can't launch
Are there any trick of install those rpm?? why the screen orientation 
can not work after I install the rpm built by myself??




I have no idea what hardware you running on, but mobility depends on a 
backend that actually retrieves the sensor data (like the sensor 
framework.)  If that doesn't work then mobility doesn't have a chance.


You __shouldn't__ need orientation-contextkit-sensor since the 
libqtsensors1 package does the translation of contextkit to QSensor's 
for you, but the reason orientation-contextkit-sensor exist is because I 
was having issues getting the translation to happen (and up till a 
couple of months ago libqtsensors1 would even segfault on initialization.)


With that said... if you know contextkit values are being published for 
orientation changes, then you can install orientation-contextkit-sensor 
and manually remove /usr/lib/qt4/plugins/sensors/libqtsensor_meego.so.


Note... orientation-contextkit-sensor is just a work around while 
figuring out why the libqtsensor_meego.so sensor plugin is borked on 
some systems.  Ideally orientation-contextkit-sensor would not exist.


--rusty



___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[kate.alhola]

>
>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of 
>ext Thiago >Macieira [thi...@kde.org]
>Sent: Wednesday, March 02, 2011 4:14 PM
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework 
>for MeeGo tablets
>
>On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote:
>> However, the MTF includes things like mcompositor,
>> mdecorator, duicontrolpanel, etc...  These are fundamental
>> parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
>> if the MTF is scheduled for termination... then I missed a
>> memo somewhere.
>
>You're right: before it can be terminated, an alternative needs to come along.

Let's make difference, duicontrolpanel is just an application that is made with 
MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
can be removed, all of them need to be rewritten with Qt Components. 

MtF and Qt Components can work side by side. Compositor is just compositor.
MtF and Qt Components applications work as well even with N900 Clutter based
compositor.

>My guess (and it's a guess!) is that we'll see these things move away when
>Wayland moves in.

My Guess is that MtF is no longer needed for application programming when we
get even Qt Components alpha out. There will be MtF UI toolkit applications 
so long that it takes re-write all of them with Qt Components.

It is completely other question rewrite outside of application frameworks like 
compositor
and system UI.

Kate
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Clark, Joel]

On Wednesday, March 02, 2011 4:53 AM Gabriel M. Beddingfield wrote

> However, the MTF includes things like mcompositor, 
> mdecorator, duicontrolpanel, etc...  These are fundamental 
> parts of the Handset UX, the IVI UX, and the Tablet UX.  So, 
> if the MTF is scheduled for termination... then I missed a 
> memo somewhere.

> -gabriel

Small correction.  The current IVI images don't include mcompositor and the 
current IVI home screen uses QT and matchbox2. 

Also can't mcompositor be separated from MTF and run on other frameworks?

regards
Joel

___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Rusty Lynch]

On 03/02/2011 04:52 AM, Gabriel M. Beddingfield wrote:

On Wednesday, March 02, 2011 01:51:51 am Ville M. Vainio
wrote:
   

On Wed, Mar 2, 2011 at 1:13 AM, Gabriel M. Beddingfield

  wrote:
 

On Tue, 1 Mar 2011, Victor Vu wrote:
   

Is MeeGo Touch Framework here to stay?
 

Yes.
   

Is this based on some new information that hasn't been
shared elsewhere? MTF is widely understood to be
deprecated for third party use.
 

The OP's question didn't specifically ask about 3rd party
use.  However, if you read the rest of my e-mail... I *did*
add a very strong indication that it's deprected for 3rd
party use.
   


The original question was simply asking about which components are safe 
for application development.  While MTF covers many things, the actual 
GUI library (i.e. deriving your application class from MApplication, 
using MButtons and all the other QGraphicsObject/QGraphicsWidget derived 
classes) should not be recommended (3rd party or otherwise.)


Of course... the libs are there so there is nothing stopping you from 
using them, but you better strap yourself in tight and follow each 
change in libmeegotouch because it's going to be a bumpy ride.  If you 
are deeply involved in libmeegotouch then this might not be a big deal 
to you.



However, the MTF includes things like mcompositor,
mdecorator, duicontrolpanel, etc...  These are fundamental
parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
if the MTF is scheduled for termination... then I missed a
memo somewhere.
   


This is what I have come to hate about our lumping so many technologies 
into one term.  MTF covers a lot of stuff that is really of no concern 
to the guy just trying to write an application.


There are some areas in addition to the GUI classes that effect app 
developers (like how you insert your application settings into the 
system wide settings app), but I expect most of these will be smoothed 
out with a QML components library.


--rusty


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] Wayland Timeline

[Mark Constable]

On 03/03/11, Thiago Macieira wrote:
> My guess (and it's a guess!) is that we'll see these things
> move away when Wayland moves in.

Good to hear. Is there any guesstimate as to when we can start
to see and use a Wayland backend for Qt?

What would be the implications for the likes of mutter, mcompositor
and matchbox etc?

--markc

___
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] tablet release...

[Robin Burchell]

On 02/03/11 16:09, Mark Constable wrote:
> On 03/03/11, Thiago Macieira wrote:
>> My guess (and it's a guess!) is that we'll see these things
>> move away when Wayland moves in.
>
> Good to hear. Is there any guesstimate as to when we can start
> to see and use a Wayland backend for Qt?

One already exists 
(http://virtuousgeek.org/blog/index.php/jbarnes/2010/09/20/qt_on_wayland_first_clock) 
and was merged into Qt this January, IIRC.



> What would be the implications for the likes of mutter, mcompositor
> and matchbox etc?

Given that all of them are X11 window managers, probably obsolescence, 
at least in part.


> --markc

Robin
___
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] Wayland Timeline

[Michael Leibowitz]

On Wed, 2011-03-02 at 08:09 -0800, Mark Constable wrote:
> On 03/03/11, Thiago Macieira wrote:
> > My guess (and it's a guess!) is that we'll see these things
> > move away when Wayland moves in.
> 
> Good to hear. Is there any guesstimate as to when we can start
> to see and use a Wayland backend for Qt?

Although I can't directly answer that question, I can at least point you
to work in progress:
http://qt.gitorious.org/~krh/qt/qt-wayland

Cheers
-- 
Michael Leibowitz 

___
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] Wayland Timeline

[Mark Constable]

On 03/03/11, Michael Leibowitz wrote:
> > Good to hear. Is there any guesstimate as to when we can
> > start to see and use a Wayland backend for Qt?

I should have added... "within MeeGo"

> Although I can't directly answer that question, I can at
> least point you to work in progress:
> http://qt.gitorious.org/~krh/qt/qt-wayland

Promising but a little bit lonely with a sole developer and no
commits for the past 3 weeks. I sense Wayland will be a serious
game changer that will affect MeeGo in a big way. If so then I
don't want to invest too much time and resources using anything
else unless there is no way(land) around it in the mean time.

--markc
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Arjan van de Ven]

On 3/2/2011 7:31 AM, Gabriel M. Beddingfield wrote:



On Wed, 2 Mar 2011, Arjan van de Ven wrote:


However, the MTF includes things like mcompositor,
mdecorator, duicontrolpanel, etc...


We're "stuck" with mcompositor for now, but many of these other items 
are very aggressively being worked on in terms of removing them as 
soon as possible (some even for 1.2)


Thank you.

This is news to me.  Is there a roadmap somewhere?  And if someone 
wanted to track this sort of thing (MTF, Handset UX, Tablet UX) -- 
where should he be hanging out?



we're currently scrambling a bit deciding on various pieces what to do 
in the new situation; expect a more comprehensive email soon.


(all these pieces are connected so it's not easy to take one out)
___
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] Wayland Timeline

[Arjan van de Ven]

On 3/2/2011 8:09 AM, Mark Constable wrote:

On 03/03/11, Thiago Macieira wrote:

My guess (and it's a guess!) is that we'll see these things
move away when Wayland moves in.

Good to hear. Is there any guesstimate as to when we can start
to see and use a Wayland backend for Qt?



while I'd love to say "it'll be there for 1.3"...  in practice I think 
it'll be the 1.4 release before we see it in widespread use in MeeGo.




What would be the implications for the likes of mutter, mcompositor
and matchbox etc?


Different world; pretty much all of those will be obsolete. Something 
new will be there (and likely we'll be using pieces of matchbox, but 
that's TBD)



___
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] traffic in traffic out in conmanprovider.cpp

[Yung, Winson W]

Michael, do you have any update on this?

/Winson

>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>On Behalf Of Michael Leibowitz
>Sent: Tuesday, February 08, 2011 12:33 AM
>To: Mathew, JohnX
>Cc: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] traffic in traffic out in conmanprovider.cpp
>
>On Tue, 2011-02-08 at 00:25 -0800, Mathew, JohnX wrote:
>> The implementation of traffic counters in
>> http://meego.gitorious.org/meego-handset-ux/contextkit-
>meego/blobs/master/internet/connmanprovider.cpp seems to be using a
>timer which triggers every 5 secs which is causing power management
>issues.
>>
>> Also it seems to be giving random values as traffic in and traffic
>> out. What is the plan with the implementation of this feature. If it
>> is not used can the timer be removed?
>
>This is a dirty hack for which I am guilty.  BMC#3672
>
>We're working on figuring out which contextkit properties we need to
>provide and which we don't.  There is a proper way to do this.  If we
>choose to provide it, then we'll do it the right way.  If we don't,
>we'll remove it.
>
>Cheers
>
>--
>Michael Leibowitz 
>
>___
>MeeGo-dev mailing list
>MeeGo-dev@meego.com
>http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] LIRC, Pulseaudio, && Meego

[Nasa]

Hi guys,

Does anyone know if the lirc module for pulseaudio is included
in any of the pulseaudio packages?  I don't see it anywhere,
but I have been know to miss stuff...

Nasa
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[karoliina.t.salmi...@gmail.com]

>>On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote:
>>> However, the MTF includes things like mcompositor,
>>> mdecorator, duicontrolpanel, etc...  These are fundamental
>>> parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
>>> if the MTF is scheduled for termination... then I missed a
>>> memo somewhere.
>>
>>You're right: before it can be terminated, an alternative needs to come along.
>
> Let's make difference, duicontrolpanel is just an application that is made 
> with
> MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
> can be removed, all of them need to be rewritten with Qt Components.

I have been already thinking of duicontrolpanel2 (maybe we can name it
now properly m).
It would most likely use Qt components for UI and C++ for the "backend".
I have been thinking separation of the UI layer and "engine" so that
there is some further flexibility
in UI customization over the traditional applet approach where the UI
is integral part of each applet.

This is just on idea stage at the moment, nobody has started coding it
yet. If somebody has by the way
great ideas for it, feel free to contribute, I am listening!

Best Regards,
Karoliina Salminen
the caretaker of duicontrolpanel
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Kevron Rees]

On Wed, 2011-03-02 at 22:04 +0200, karoliina.t.salmi...@gmail.com wrote:
> >>On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote:
> >>> However, the MTF includes things like mcompositor,
> >>> mdecorator, duicontrolpanel, etc...  These are fundamental
> >>> parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
> >>> if the MTF is scheduled for termination... then I missed a
> >>> memo somewhere.
> >>
> >>You're right: before it can be terminated, an alternative needs to come 
> >>along.
> >
> > Let's make difference, duicontrolpanel is just an application that is made 
> > with
> > MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
> > can be removed, all of them need to be rewritten with Qt Components.
> 
> I have been already thinking of duicontrolpanel2 (maybe we can name it
> now properly m).

If you are thinking of creating a settings/control panel application,
there is already one in the Tablet UX (that I understand will be open
sourced in a 'couple weeks').  It supports loading 'applets' similarly
to how duicontrolpanel did.

That said, there's always need for individual settings applets that do
various things ;).

-Kevron

___
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] Wayland Timeline

[Thiago Macieira]

On Thursday, 3 de March de 2011 02:43:39 Mark Constable wrote:
> On 03/03/11, Michael Leibowitz wrote:
> > > Good to hear. Is there any guesstimate as to when we can
> > > start to see and use a Wayland backend for Qt?
> 
> I should have added... "within MeeGo"
> 
> > Although I can't directly answer that question, I can at
> > least point you to work in progress:
> > http://qt.gitorious.org/~krh/qt/qt-wayland

Look no further, it's already in master:

http://qt.gitorious.org/qt/qt/trees/master/src/plugins/platforms/wayland

> Promising but a little bit lonely with a sole developer and no
> commits for the past 3 weeks. I sense Wayland will be a serious
> game changer that will affect MeeGo in a big way. If so then I
> don't want to invest too much time and resources using anything
> else unless there is no way(land) around it in the mean time.

You know that one developer got Qt running on Android, right? Wayland 
shouldn't be _that_ hard...

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[karoliina.t.salmi...@gmail.com]

>> > Let's make difference, duicontrolpanel is just an application that is made 
>> > with
>> > MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
>> > can be removed, all of them need to be rewritten with Qt Components.
>>
>> I have been already thinking of duicontrolpanel2 (maybe we can name it
>> now properly m).
>
> If you are thinking of creating a settings/control panel application,
> there is already one in the Tablet UX (that I understand will be open
> sourced in a 'couple weeks').  It supports loading 'applets' similarly
> to how duicontrolpanel did.
>
> That said, there's always need for individual settings applets that do
> various things ;).

Sure there is, but I was just thinking of adding one more layer and separating
the UI.

E.g. display applet now has brightness slider, but what if you wanted to place
brightness slider elsewhere than in the applet (this happened, there
have been several rounds of new design
decisions of where different settings should be placed). This idea is
to give freedom to
not limit certain settings to certain applets but provide additional
layer of flexibility.
I will check tablet ux, but I have a feeling it may not give the
solution we were after but rather is more like the
current generation of duicontrolpanel.

With Qt Components being the UI abstraction, this would not come even
with any significant
complication, quite in contrary for the applet developers. I have not
yet finalize the idea, but
I have been just prototyping with the Qt components + C++ to get idea
how the api could work.

Best Wishes
Karoliina

P.S. Our datetime applet looks horrible on MeeGo because it uses
placeholder on place of closed source
time picker and date picker. Making datetime applet really great would
be a low hanging fruit.
Would someone be interested innovating a community replacements for
those components?
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Randall Arnold]

> - Original message - 
> From: "karoliina.t.salmi...@gmail.com‎" 
> To: "Kevron Rees‎" 
> cc: meego-dev@meego.com
> Subject: Re: [MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework 
> for MeeGo tablets
> Date: Thu, 3 Mar 2011 00:08:31 +0200
> 
> 
>>> > Let's make difference, duicontrolpanel is just an application 
> >> that is made with
> >> > MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
> >> > can be removed, all of them need to be rewritten with Qt Components.
> >>
> >> I have been already thinking of duicontrolpanel2 (maybe we can name it
> >> now properly m).
> >
> > If you are thinking of creating a settings/control panel application,
> > there is already one in the Tablet UX (that I understand will be open
> > sourced in a 'couple weeks').  It supports loading 'applets' similarly
> > to how duicontrolpanel did.
> >
> > That said, there's always need for individual settings applets that do
> > various things ;).
> 
> Sure there is, but I was just thinking of adding one more layer and separating
> the UI.
> 

> 
> With Qt Components being the UI abstraction, this would not come even
> with any significant
> complication, quite in contrary for the applet developers. I have not
> yet finalize the idea, but
> I have been just prototyping with the Qt components + C++ to get idea
> how the api could work.
> 

I agree Karoliina-- this makes the most sense for flexibility and 
maintainability.  Should be the default approach IMO.

Basically applet code ---> wrapper ---> control panel (or any other host, 
actually, including the desktop)

Heck, Microsoft managed this with the Windows control panel, so... ; )

Randy

--
Ovi Mail: Making email access easy
http://mail.ovi.com

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] Anyone knows how to enable logging in libQtCore

[Yung, Winson W]

Hi all, I need to debug something related to system wakeup in msyncd, in order 
to get more info on what's the code is doing inside libQtCore. I want to see it 
is possible to enable the logging for Qt.

/Winson.
___
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] package install cause the screen orientation can't work

[Jia-Chi Lai]

2011/3/2 Rusty Lynch 

>  On 03/02/2011 12:50 AM, Jia-Chi Lai wrote:
>
>> hi~
>> I build the  qt-mobility package on OBS and install the rpm files of the
>> package.
>> then I launch the setting application but the screen orientation can't
>> work.
>> I also build orientation-contextkit-sensor package and install it.
>> the home screen can't launch
>> Are there any trick of install those rpm?? why the screen orientation can
>> not work after I install the rpm built by myself??
>>
>>
> I have no idea what hardware you running on, but mobility depends on a
> backend that actually retrieves the sensor data (like the sensor framework.)
>  If that doesn't work then mobility doesn't have a chance.
>
> You __shouldn't__ need orientation-contextkit-sensor since the
> libqtsensors1 package does the translation of contextkit to QSensor's for
> you, but the reason orientation-contextkit-sensor exist is because I was
> having issues getting the translation to happen (and up till a couple of
> months ago libqtsensors1 would even segfault on initialization.)
>
> but I use 2011.03.01 release tablet image which include both libqtsensors1
rpm and orientation-contextkit-sensor rpm in it and the screen is work fine.
but I just use the both two rpm get from public repo, and built with OBS,
then use command line "rpm -Uvh orientation-contextkit-sensor " "rpm
-Uvh qt-mobility libqtsensor1 "
to install those rpm. but the screen can't work.

It's strangedo you have any idea??
How could I do to make the screen orientation work again??
Remove  i/usr/lib/qt4/plugins/sensors/libqtsensor_meego.so and install
orientation-contextkit-sensor? or any idea??

With that said... if you know contextkit values are being published for
orientation changes, then you can install orientation-contextkit-sensor and
manually remove
Note... orientation-contextkit-sensor
i/usr/lib/qt4/plugins/sensors/libqtsensor_meego.so.s just a work around
while figuring out why the libqtsensor_meego.so sensor plugin is borked on
some systems.  Ideally orientation-contextkit-sensor would not exist.

   --rusty
___
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] package install cause the screen orientation can't work

[Jia-Chi Lai]

2011/3/3 Jia-Chi Lai 

>
>
> 2011/3/2 Rusty Lynch 
>
>   On 03/02/2011 12:50 AM, Jia-Chi Lai wrote:
>>
>>> hi~
>>> I build the  qt-mobility package on OBS and install the rpm files of the
>>> package.
>>> then I launch the setting application but the screen orientation can't
>>> work.
>>> I also build orientation-contextkit-sensor package and install it.
>>> the home screen can't launch
>>> Are there any trick of install those rpm?? why the screen orientation can
>>> not work after I install the rpm built by myself??
>>>
>>>
>> I have no idea what hardware you running on, but mobility depends on a
>> backend that actually retrieves the sensor data (like the sensor framework.)
>>  If that doesn't work then mobility doesn't have a chance.
>>
>> You __shouldn't__ need orientation-contextkit-sensor since the
>> libqtsensors1 package does the translation of contextkit to QSensor's for
>> you, but the reason orientation-contextkit-sensor exist is because I was
>> having issues getting the translation to happen (and up till a couple of
>> months ago libqtsensors1 would even segfault on initialization.)
>>
>> but I use 2011.03.01 release tablet image which include both libqtsensors1
> rpm and orientation-contextkit-sensor rpm in it and the screen is work fine.
> but I just use the both two rpm get from public repo, and built with OBS,
> then use command line "rpm -Uvh orientation-contextkit-sensor " "rpm
> -Uvh qt-mobility libqtsensor1 "
> to install those rpm. but the screen can't work.
>
> It's strangedo you have any idea??
> How could I do to make the screen orientation work again??
> Remove  i/usr/lib/qt4/plugins/sensors/libqtsensor_meego.so and install
> orientation-contextkit-sensor? or any idea??
>
>

I tried to remove the /usr/lib/qt4/plugins/sensors/libqtsensor_meego.so and
screen orientation can work now...seen the qt-mobility works now.
thanks a lot.^^





>  With that said... if you know contextkit values are being published for
> orientation changes, then you can install orientation-contextkit-sensor and
> manually remove
> Note... orientation-contextkit-sensor
> i/usr/lib/qt4/plugins/sensors/libqtsensor_meego.so.s just a work around
> while figuring out why the libqtsensor_meego.so sensor plugin is borked on
> some systems.  Ideally orientation-contextkit-sensor would not exist.
>
>--rusty
>
>
>
>
___
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] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets

[Sivan Greenberg]

Is backend here referring to the system wide settings framework that
is part of meego gitorious or scheduled to be open sourced?

-Sivan

On Wed, Mar 2, 2011 at 10:04 PM, karoliina.t.salmi...@gmail.com
 wrote:
>>>On Wednesday, 2 de March de 2011 06:52:34 Gabriel M. Beddingfield wrote:
 However, the MTF includes things like mcompositor,
 mdecorator, duicontrolpanel, etc...  These are fundamental
 parts of the Handset UX, the IVI UX, and the Tablet UX.  So,
 if the MTF is scheduled for termination... then I missed a
 memo somewhere.
>>>
>>>You're right: before it can be terminated, an alternative needs to come 
>>>along.
>>
>> Let's make difference, duicontrolpanel is just an application that is made 
>> with
>> MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
>> can be removed, all of them need to be rewritten with Qt Components.
>
> I have been already thinking of duicontrolpanel2 (maybe we can name it
> now properly m).
> It would most likely use Qt components for UI and C++ for the "backend".
> I have been thinking separation of the UI layer and "engine" so that
> there is some further flexibility
> in UI customization over the traditional applet approach where the UI
> is integral part of each applet.
>
> This is just on idea stage at the moment, nobody has started coding it
> yet. If somebody has by the way
> great ideas for it, feel free to contribute, I am listening!
>
> Best Regards,
> Karoliina Salminen
> the caretaker of duicontrolpanel
> ___
> 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

Re: [MeeGo-dev] Enabling multi-touch on arm (on the Samsung Galaxy Tab)

[Zhang, Austin]

If you are using the QT from current meego, then it has support MT by XI2. So, 
if you cannot get anything from mtev, seemed like your panel driver didn't send 
_right_ event up, so mtdev or mtev cannot identify those events. 

Why you have to stick with that .32 kernel rather than port your driver (if it 
is possible) to meego kernel, so that MT support can be done in decent method 
like various vertical had done in meego?

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Simon Pickering
Sent: Thursday, February 24, 2011 6:56 AM
To: meego-dev@meego.com
Subject: [MeeGo-dev] Enabling multi-touch on arm (on the Samsung Galaxy Tab)

Hi all,

I'm "porting" Meego to the Samsung Galaxy Tab (not such a problem, just
sorting out the initramfs and various drivers.)

Anyway I've got Meego booting and up to showing the handset "desktop"
and understand that I should be able to recompile Qt to support
multitouch input events as produced by mtev (currently with mtev I
receive no inputs so can't do much other than admire the desktop
wallpaper), but I've really no idea which version of Qt and/or the
multitouch driver one should use, and which combinations work, etc. 

I'm running a 2.6.32-9 kernel (so pre-xinput2 changes afaiu) and am
happy to base my ARM image on anything (stskeeps suggests using 1.1.90
so I was thinking of 1.1.90.4.20110222.2 assuming no-one has any
arguments, I've previously been using a 1.1.80 image, not knowing the
status of Meego ARM.)

Anyway I've just had an OBS account setup by lbt and I'd appreciate any
advice on what/how to build Qt to support multitouch on the Tab (using
whatever versions are thought to be appropriate to go with my kernel
version.)

Any other general multitouch commentary also welcomed for the future
(i.e. porting Samsung kernel patches to a newer kernel if required.) 

Thanks,


Simon


___
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

Re: [MeeGo-dev] Anyone knows how to enable logging in libQtCore

[Thiago Macieira]

On Wednesday, 2 de March de 2011 17:13:25 Yung, Winson W wrote:
> Hi all, I need to debug something related to system wakeup in msyncd, in
> order to get more info on what's the code is doing inside libQtCore. I want
> to see it is possible to enable the logging for Qt.

MeeGo has a special patch I made that logs all warnings to the syslog.

If the code is properly written, there will be no warnings. Qt has no tracing 
or debugging messages.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
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] Anyone knows how to enable logging in libQtCore

[Yung, Winson W]

Can you please provide some insight on how to enable/use the patch?

/Winson

>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>On Behalf Of Thiago Macieira
>Sent: Wednesday, March 02, 2011 10:25 PM
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] Anyone knows how to enable logging in libQtCore
>
>On Wednesday, 2 de March de 2011 17:13:25 Yung, Winson W wrote:
>> Hi all, I need to debug something related to system wakeup in msyncd,
>in
>> order to get more info on what's the code is doing inside libQtCore. I
>want
>> to see it is possible to enable the logging for Qt.
>
>MeeGo has a special patch I made that logs all warnings to the syslog.
>
>If the code is properly written, there will be no warnings. Qt has no
>tracing
>or debugging messages.
>
>--
>Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>  Senior Product Manager - Nokia, Qt Development Frameworks
>  PGP/GPG: 0x6EF45358; fingerprint:
>  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
___
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] Wayland Timeline

[Mark Constable]

On 03/03/11, Thiago Macieira wrote:
> Look no further, it's already in master:
> http://qt.gitorious.org/qt/qt/trees/master/src/plugins/platforms/wayland

Apologies for asking about generic git-lore but how do I get the
above included with a "git clone git://gitorious.org/qt/qt.git"?

I just tried but I don't even have a src/plugins/platform/ folder
and I'm not sure where else to find instructions, or even the
right keywords to google for.

> You know that one developer got Qt running on Android, right?

No, I didn't know that. Very impressive.

--markc
___
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] Anyone knows how to enable logging in libQtCore

[Thiago Macieira]

On Wednesday, 2 de March de 2011 23:35:26 Yung, Winson W wrote:
> Can you please provide some insight on how to enable/use the patch?

It's already enabled if you're using the MeeGo build of Qt.
-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

[MeeGo-dev] How to tracker the media folder(such as automount SD) under root

[yinxb]

I am analysing the meego-handset-video code,but I cannot find where set
the tracker directory to /home/meego/Video?and my project need to
tracker the automount SD/USB directory.

Anyone can help me?

---
Confidentiality Notice: The information contained in this e-mail and any 
accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential 
and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of 
this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, 
disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this 
communication in error,please 
immediately notify the sender by return e-mail, and delete the original message 
and all copies from 
your system. Thank you. 
---
___
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] Wayland Timeline

[Thiago Macieira]

On Thursday, 3 de March de 2011 16:39:12 Mark Constable wrote:
> On 03/03/11, Thiago Macieira wrote:
> > Look no further, it's already in master:
> > http://qt.gitorious.org/qt/qt/trees/master/src/plugins/platforms/wayland
> 
> Apologies for asking about generic git-lore but how do I get the
> above included with a "git clone git://gitorious.org/qt/qt.git"?

You don't need to do anything.

It's in src/plugins/platforms/wayland, in the master branch. The default 
branch when you clone is 4.7.

> I just tried but I don't even have a src/plugins/platform/ folder
> and I'm not sure where else to find instructions, or even the
> right keywords to google for.
> 
> > You know that one developer got Qt running on Android, right?
> 
> No, I didn't know that. Very impressive.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
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] Anyone knows how to enable logging in libQtCore

[fathi.boudra]

Hi,

> Can you please provide some insight on how to enable/use the patch?

You need to set QT_USE_SYSLOG environment variable.

Cheers,

Fathi
___
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] Anyone knows how to enable logging in libQtCore

[Yung, Winson W]

What do I set it to? I did "export QT_USE_SYSLOG=1", and it doesn't work.

/Winson

>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>On Behalf Of fathi.bou...@nokia.com
>Sent: Wednesday, March 02, 2011 11:21 PM
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] Anyone knows how to enable logging in libQtCore
>
>Hi,
>
>> Can you please provide some insight on how to enable/use the patch?
>
>You need to set QT_USE_SYSLOG environment variable.
>
>Cheers,
>
>Fathi
>___
>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