Re: [clutter] How do i get screen properties with clutter?

[Tomas Frydrych]

On 12/06/10 17:52, Ankur Sinha wrote:
 On Sat, 2010-06-12 at 17:36 +0100, Emmanuele Bassi wrote:
 On Sat, 2010-06-12 at 21:58 +0530, Ankur Sinha wrote:
 hey,

 I would like my stage to be say, 80% of the screen size. How would I
 find the size of the screen using pyclutter? I've been through the docs
 and I don't see any methods that would give me this info. 

 Also, how do I remove window decorations? for eg, I'm making a splash,
 which doesn't need the title bar etc. Is there a property that I can
 set?

 Clutter does not abstract a platform's windowing system - except to the
 extent that it needs to effectively paint the stage and handle events on
 it. the rest is left to the platform's own libraries.

 you can use clutter-gtk (and its python bindings) to get a Stage
 embedded inside a gtk+ window - and then use gtk+'s API to achieve what
 you want.

 I'm trying to *not* use the gtk bindings so the app stays DE
 independent.

As Emmanuele indicated, windowing is not platform-agnostic; you will
need to use whatever APIs given platform provides to do this, i.e., on
an X-based system, you will need to use xlib and follow the ICCM
(http://tronche.com/gui/x/icccm/) and the EWMH
(http://standards.freedesktop.org/wm-spec/wm-spec-1.4.html) protocols.

Tomas
-- 
To unsubscribe send a mail to clutter+unsubscr...@o-hand.com

Re: [clutter] Clutter-gst problem

[Damien Lespiau]

On Mon, 2010-06-14 at 06:26 +0100, Rob Kramer wrote:
 Hey all

Hi,

 I noticed the video-player example in clutter-gst is a bit broken in git 
 master. The video's colours are all wrong,

I assume you mean clutter master here.

  With some manual bisecting, I 
 found that it's introduced by:
 
   commit ce6e80315e17f2e671e2709268f580add757f596
   Author: Robert Bragg rob...@linux.intel.com
   Date:   Mon Apr 26 10:01:43 2010 +0100
 
   material: Adds backend abstraction for fragment processing
 
 Any idea what this issue could be? Could someone else test video-player 
 perhaps? This happens on both Intel and Nvidia GPUs btw.

Robert has basically rewritten the way Materials (The abstraction used
to fill geometry) work. While the conformance tests are passing, some
bugs still need to be crushed, it's so bleeding edge I did not even have
the opportunity to test clutter-gst against it (but knew it was likely
to break things).

Tracking clutter master can be dangerous at times, but thanks for
reporting this, it needs to be fixed indeed. Meanwhile, if you need some
stable version, can I suggest to use 1.2.10 instead? (1.3.x are
development versions leading to the 1.4.x stable versions).

-- 
Damien

-- 
To unsubscribe send a mail to clutter+unsubscr...@o-hand.com

RE: [clutter] Problem migrating from 1.0.10 to 1.2.8

[Kevin Cote]

Any thoughts on this email that I sent last week?

Thanks,
Kevin

-Original Message-
From: Kevin Cote [mailto:kc...@imsco-us.com]
Sent: Tuesday, June 08, 2010 5:19 PM
To: clutter@o-hand.com
Subject: RE: [clutter] Problem migrating from 1.0.10 to 1.2.8

Emmanuele:

In addition to the notes below I spent the day attempting to get my application 
running under the final Moblin 2.1 IVI release 
(moblin-2.1-PR-Final-ivi-201002090924.img).  This uses the IEGD v10.3 driver.  
To do this I upgraded my target platform with this release.

Running my application as built for clutter v1.0.10 on top of this Moblin 
release worked fine.  This release appears to be based on clutter v1.0.8.  I 
attempted to update this by the following method:
 - Installed and built v1.2.8 on my Ubuntu development environment.
 - Copied the v1.2.8 clutter library (libclutter-glx-1.0.so.0.200.8) onto the 
Moblin target system.
 - Created two links to this library (libclutter-glx-1.0.so.0, 
libclutter-glx-1.0.so)
 - Executed ldconfig on the folder that contained the above files
 - Built my application on my Ubuntu development environment.
 - Copied my application to the Moblin target system.

Now when I execute, I get the same errors that I noted in my earlier emails.

Any ideas?  If, as you say, this is a mipmapping support issue, what has 
changed within clutter to trigger this error?

Thanks,
Kevin Cote'

-Original Message-
From: Kevin Cote [mailto:kc...@imsco-us.com]
Sent: Tuesday, June 08, 2010 9:04 AM
To: clutter@o-hand.com
Subject: RE: [clutter] Problem migrating from 1.0.10 to 1.2.8


-Original Message-
From: Emmanuele Bassi [mailto:eba...@linux.intel.com]
Sent: Tuesday, June 08, 2010 3:13 AM
To: clutter@o-hand.com
Subject: Re: [clutter] Problem migrating from 1.0.10 to 1.2.8

On Mon, 2010-06-07 at 17:04 -0700, Kevin Cote wrote:

 I have an application that I have developed over the last 6 months on
 top of v1.0.10.  I am now trying to migrate this app to v1.2.8.  I
 have tried running the migrated app under Ubuntu 9.0.4 and also
 Moblin v2.  I get the same issues in both cases.  My symptoms are twofold:

 - Text is garbled.  By this I mean that each character is
 drawn almost like a block instead of the actual glyph.

which GPU and driver are you using?

Moblin is running on a 1.6GHz Atom with a US15W (Poulsbo) GPU.  I am running 
with the IEGD driver, v10.2.


 - Certain textures are not rendered (meaning I don’t see
 them), yet the app functions as if they are there (meaning if the
 texture is a button control the button still functions even though it
 is invisible).

again, these two seem connected (lack of mipmapping support).

 I tried executing some of the test-interactive programs and have seen
 two issues with v1.2.8.  These issues don’t exist in v1.0.10:

 1)  With the test-texture-async I get the following output in the
 console and see no output to the application window.

this has nothing to do with the rest of the issues; you have to pass a
file to the test otherwise it'll fail. I'll add a check that bails out
early instead of spewing errors.

Under v1.0.10 I didn't have to pass a file.  That was my confusion.  Now when I 
pass a file it works fine as you have stated.


 2)  With the test-texture-quality application I see the hand drawn
 properly on the first cycle, but for all other cycles, only a few
 pixels near the top are drawn.

there you go: lack of mipmapping support on your platform.

So, what has changed since v1.0.10?  This app has worked fine on various 
versions of the 1.0 branch.  It is my understanding from Intel that the driver 
I am using does have mipmapping support.

Thanks,
Kevin





---
This email and any files transmitted with it are confidential  proprietary to 
Systems and
Software Enterprises, Inc. (dba IMS). This information is intended solely for 
the use of
the individual or entity to which it is addressed. Access or transmittal of the 
information
contained in this e-mail, in full or in part, to any other organization or 
persons is not
authorized.
---