On Ubuntu it is in libmutter-dev
/usr/lib/mutter/Meta-3.0.gir
On 18/05/12 09:37, Amy C wrote:
> On Fri, May 18, 2012 at 7:48 AM, Jasper St. Pierre
> wrote:
>> In Fedora, for me, they're provided by the mutter package. In some
>> distros, it's provided by the -dev package (the one that provides t
On Fri, May 18, 2012 at 7:48 AM, Jasper St. Pierre
wrote:
> In Fedora, for me, they're provided by the mutter package. In some
> distros, it's provided by the -dev package (the one that provides the
> headers)
>
Thanks. I'm in Ubuntu 12.04 and have already installed libmutter &
libmutter-dev & hav
In Fedora, for me, they're provided by the mutter package. In some
distros, it's provided by the -dev package (the one that provides the
headers)
On Thu, May 17, 2012 at 9:08 AM, Amy C wrote:
> On Thu, May 17, 2012 at 11:03 PM, Jasper St. Pierre
> wrote:
>> OK. Meta-3.0.gir should be in /usr/lib
On Thu, May 17, 2012 at 11:03 PM, Jasper St. Pierre
wrote:
> OK. Meta-3.0.gir should be in /usr/lib*/mutter.
>
> The general rule is that private girs go with their typelib dirs in
> lib*, and public girs go in /usr/share/gir-1.0
>
Well, it isn't. `find /usr -name Meta-3.0.gir` gives nothing, and
On Thu, May 17, 2012 at 8:54 AM, Amy C wrote:
> On Thu, May 17, 2012 at 10:46 PM, Jasper St. Pierre
> wrote:
>> girs don't go in /usr/lib*, they go in /usr/share/gir-1.0
>
> Ok, I do have a few .gir files in there. It's rather sparse though
> compared to the list of .typelibs I have - for example
On Thu, May 17, 2012 at 10:46 PM, Jasper St. Pierre
wrote:
> girs don't go in /usr/lib*, they go in /usr/share/gir-1.0
Ok, I do have a few .gir files in there. It's rather sparse though
compared to the list of .typelibs I have - for example Meta-*.gir
isn't there, so that brings me back to trying
On Thu, May 17, 2012 at 8:43 AM, Amy C wrote:
>> This info is reasonably concisely documented in .gir files (gobject
>> introspection somethingorother). For example,
>> /usr/lib64/mutter/Meta-3.0.gir contains info about mutter classes /
>> objects / signals.
>
> cheers, forgot about the .gir
> How
> This info is reasonably concisely documented in .gir files (gobject
> introspection somethingorother). For example,
> /usr/lib64/mutter/Meta-3.0.gir contains info about mutter classes /
> objects / signals.
cheers, forgot about the .gir
However, I only have .typelib files in my /usr/lib*.
I reca
On Thu, May 17, 2012 at 9:38 PM, Amy C wrote:
> On Thu, May 17, 2012 at 4:36 PM, Jasper St. Pierre
> wrote:
>> This is what the grab-op-begin/grab-op-end signals are for.
>
> A further question - how do I know what signals are available to
> connect to, is there something I can do in looking-glas
On Thu, May 17, 2012 at 4:36 PM, Jasper St. Pierre
wrote:
> This is what the grab-op-begin/grab-op-end signals are for.
A further question - how do I know what signals are available to
connect to, is there something I can do in looking-glass to get the
list?
Because I only learn about signals at
On Thu, May 17, 2012 at 4:36 PM, Jasper St. Pierre
wrote:
> On Thu, May 17, 2012 at 2:21 AM, Tim Cuthbertson wrote:
>> On Thu, May 17, 2012 at 2:00 PM, Amy C wrote:
>>> Hi all,
>>>
>>> I'm currently having fun porting xpenguins to a gnome shell extension
>>> (yes pointless I know, but fun), and
On Thu, May 17, 2012 at 2:21 AM, Tim Cuthbertson wrote:
> On Thu, May 17, 2012 at 2:00 PM, Amy C wrote:
>> Hi all,
>>
>> I'm currently having fun porting xpenguins to a gnome shell extension
>> (yes pointless I know, but fun), and I basically need to keep track of
>> where every window is on the
On Thu, May 17, 2012 at 2:00 PM, Amy C wrote:
> Hi all,
>
> I'm currently having fun porting xpenguins to a gnome shell extension
> (yes pointless I know, but fun), and I basically need to keep track of
> where every window is on the screen at all times. This is so that
> toons can walk on the win
13 matches
Mail list logo
