Re: [pygtk] Python 3 and introspection hackfest

2010-03-06 Thread Tomeu Vizoso
On Fri, Mar 5, 2010 at 20:56, David Malcolm dmalc...@redhat.com wrote:
 On Tue, 2010-02-09 at 16:47 +, Tomeu Vizoso wrote:
 On Fri, Feb 5, 2010 at 22:22, Zachary Goldberg zgold...@gmail.com wrote:
  On Fri, Feb 5, 2010 at 1:16 PM, John Palmieri jo...@redhat.com wrote:
 
  - Tomeu Vizoso to...@tomeuvizoso.net wrote:
 
  Hi,
 
  there's interest in having a hackfest sponsored by the GNOME
  Foundation that would give a push to some issues that are important
  to
  the Pygtk community: support for Python 3.x and
  gobject-introspection.
 
  How does it sound?
 
  Regards,
 
  Tomeu
 
  Hey everyone,
 
  I'm adding a couple of more people directly who have worked with Python 2 
  to 3 module conversions to this mail and who might be interested in 
  helping.
 
  The way a GNOME Foundation hackfest works is we need to figure out the 
  best location to hold it and get estimates on how much it will cost to 
  get people to that location.  We can then ask the Foundation board for 
  the money to cover costs.  I've already got a query into the board so 
  they know this is coming.
 
  The first step is finding out how many people are interested in this and 
  what their locations are.  Because of the costs involved the location of 
  the hackfest should be based on where we can get a room big enough to 
  hold everyone and its proximity to the majority of the core contributors.
 
  --
  John (J5) Palmieri
  Software Engineer
  Red Hat, Inc.
 
 
  This sounds awesome, I would love to attend.   I'm currently in the
  USA, sometimes in Philadelphia sometimes in new York City.

 Great, can you please add yourself to the wiki page?

 http://live.gnome.org/Hackfests/Python2010

 I guess you will work on callbacks, any other task that you would suggest?

 I'd like to attend this hackfest; I've just added myself to the attendee
 list on the wiki page.  (I'm local, but I don't have crash space).

 Sorry about the belated response, still digging out from under my
 post-PyCon inbox...

Awesome, I think we have a very good team and we are close to have
everything set up.

Thanks all,

tomeu

 Dave


___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/


Re: [pygtk] How to write an agenda view?

2010-03-06 Thread Martin Drautzburg
Thanks to all.
___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/


[pygtk] How to place widgets on a grid?

2010-03-06 Thread Martin Drautzburg
Hello all,

I've been struggeling with the following problem: I want to have a grid in the 
background and I want to put Buttons (or other Widgets) on the  Grid.

I tried painting the grid using a DrawingArea. Which works. But I don't know 
how to place other widgets on top. 

I tried using a gtk.Layout. This allows me to e.g. place two Button on the 
screen so they overlap. The stacking order seems to be last added widgets on 
top. But this does not seem to work with the drawing area. The drawing area 
is ALWAYS on top and hides my other widgets.

If you tell me, that this shouldn't be, I'll go and look for glitches in my 
code, but I suspect a more fundamental problem.


-- 
Martin
___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/


[pygtk] Resizable rectangles, where to start?

2010-03-06 Thread Martin Drautzburg
Hello all,

For my agenda view I need some dragable and resizable widgets, which primarily 
contain text. I don't quite know where to start. Can anyone give me a clue?

-- 
Martin
___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/


[pygtk] Wnck: Switching to and reporting current workspace (desktop) number.

2010-03-06 Thread Osmo Maatta

Hello,
This question is about the Wnck library. I still hope someone here can 
shed light on this issue.


The following code snippet loops though all active workspaces/desktops.
It then tries to report the actual desktop/workspace number, but the 
current workspace num does not change.


The code is here: http://www.futuredesktop.com/tmp/desktop_test.py

Look at the last three lines.
  ws  = screen.get_active_workspace()
  ws_num = ws.get_number()
  print i=, i,current workspace num=, ws_num

I reports something like this:
  i= 0current workspace num= 1
  i= 1current workspace num= 0
  i= 2current workspace num= 0
  i= 3current workspace num= 0
  i= 4current workspace num= 0

The current workspace num is totally wrong.
Why does Wnck behave like this?

BTW: I run this code on 64bit Ubuntu 9.10 with GNOME + Metacity Window 
Manager (not Compiz WM).

$ metacity --replace

References: http://library.gnome.org/devel/libwnck/stable/
http://library.gnome.org/devel/libwnck/stable/WnckScreen.html#wnck-screen-get-active-workspace

I may start to use the wmctrl command directly.
It rocks but I would rather not be dependent on external tools, 
subprocess'ing that from my Python modules.


Cheers,
  Osmo (Moma) Antero
  Grønland







___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/

Re: [pygtk] Wnck: Switching to and reporting current workspace (desktop) number.

2010-03-06 Thread Pietro Battiston
Il giorno sab, 06/03/2010 alle 20.16 +0100, Osmo Maatta ha scritto:
 Hello,
 This question is about the Wnck library. I still hope someone here can
 shed light on this issue.
 
 The following code snippet loops though all active
 workspaces/desktops.
 It then tries to report the actual desktop/workspace number, but the
 current workspace num does not change.
 
 The code is here: http://www.futuredesktop.com/tmp/desktop_test.py
 
 Look at the last three lines.
   ws  = screen.get_active_workspace()
   ws_num = ws.get_number()
   print i=, i,current workspace num=, ws_num
 
 I reports something like this:
   i= 0current workspace num= 1
   i= 1current workspace num= 0
   i= 2current workspace num= 0
   i= 3current workspace num= 0
   i= 4current workspace num= 0
 
 The current workspace num is totally wrong.
 Why does Wnck behave like this?
 
 BTW: I run this code on 64bit Ubuntu 9.10 with GNOME + Metacity Window
 Manager (not Compiz WM).
 $ metacity --replace
 
 References: http://library.gnome.org/devel/libwnck/stable/
 http://library.gnome.org/devel/libwnck/stable/WnckScreen.html#wnck-screen-get-active-workspace
 
 I may start to use the wmctrl command directly.
 It rocks but I would rather not be dependent on external tools,
 subprocess'ing that from my Python modules.


http://lists.gulp.linux.it/pipermail/gulp/2009-September/035843.html

That's in Italian, but I guess the code logic is quite understandable...
and works (you can verify by adding a print).

If I recall correctly, I too at the time had problems that had to do
with the gtk main loop not running.

cheers

Pietro

___
pygtk mailing list   pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/