gtk/cairo backend for the testbed.

[GoogleCodeExporter]

I made a cairo backend for the framework. It's very basic in functionality
but it's antialiased and shiny... :D
I don't know if I am going to work any more on it but I though I'd post it
here in case anyone else wants it or you want to include it.
You can basicaly just pan and zoom.

Original issue reported on code.google.com by giorg...@gmail.com on 10 Mar 2009 at 4:27

Attachments:

• cairo_main.py

[GoogleCodeExporter]

Nice work. I do love antialiasing. :)

I can't say I'd be willing to include it with the distribution in its current 
state.
However, if you work on it more to get it at least closer to the pygame/pyglet
backends, I'd be more than happy to! 

Either way, thanks for the contribution.

Original comment by sir...@gmail.com on 10 Mar 2009 at 5:00

• Changed state: Other
• Added labels: Type-Other, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Now with mousejoint and some of the settings in the gui (with gtk).
Still without all the features from the other backends.
I am probably going to add some more stuff and clean it up a bit more.

Is there a way to change the colors in the debugDraw?

Original comment by giorg...@gmail.com on 11 Mar 2009 at 5:26

Attachments:

• cairo_main.py
• cairo_main.glade

[GoogleCodeExporter]

Looking much better! The GUI is a very nice touch.

With portability in mind, would you mind replacing glib.timeout_add with
gobject.timeout_add (and removing the import itself)? It would appear that glib
doesn't exist for win32.

Colors are not customizable in the testbed currently. I didn't see it as much 
of a
priority, as it's mostly meant for testing/debugging. I wouldn't be adverse to 
having
it customizable, though. 

I'm looking forward to seeing this alongside pygame and pyglet. Keep up the 
great work!

Original comment by sir...@gmail.com on 12 Mar 2009 at 1:20

[GoogleCodeExporter]

There really is no reason to have to colors customizable, but I really dislike 
the
black background. I does a look a bit better when there is no antialiasing but 
that's
debatable to. Anyway since there will be no other use that I can think of for
customizable colors other than the cairo backend it's ok if it changes the 
colors in
a hackish way...

I added a python console now. Copyied it from epiphany-extensions it can access 
the
"world" and "framework" variables and interact with them.

the keycodes file has the pygame.locals this way the cairo backend will work 
without
pygame installed (I hope at least). It is easy to do without it.

Original comment by giorg...@gmail.com on 13 Mar 2009 at 12:59

Attachments:

• cairo_main.py
• cairo_main.glade
• console.py
• keycodes.py

[GoogleCodeExporter]

Sure is coming along quickly.

I love the idea of the console in there, but it is under the GPL. I'm not an 
expert
on licensing schemes, I'll admit. Should a user want to use the cairo backend 
in some
closed-source endeavor, it'd be necessary to distribute just that console.py, 
right?  

The keycode file is fine, but I would prefer it if we could merge the pyglet and
cairo keymappers somehow...

Keep up the great work. :)

Original comment by sir...@gmail.com on 13 Mar 2009 at 2:17

[GoogleCodeExporter]

Original comment by sir...@gmail.com on 13 Mar 2009 at 2:17

[GoogleCodeExporter]

I don't think it would be a problem even if the whole framework was GPL as long 
as
pybox2d is a less restrictive licence.

I am not sure either about GPL. It could be like you say or it could be that 
someone
would have to remove/replace the console to use it in a closed source project. 

Now that I look at the licence of the framework I am not even sure we could use 
GPL
code in it since it seems to add restrictions.

Original comment by giorg...@gmail.com on 13 Mar 2009 at 3:22

[GoogleCodeExporter]

I didn't realise it was the zlib license... We can include GPL. 
Anyway I still don't know what to do about it. It is not very usable as is but 
if you
are making a testbed example knowing it's there you could use it to tune stuff
interactively.
I favor adding a notice somewhere and including it...

Original comment by giorg...@gmail.com on 13 Mar 2009 at 5:25

[GoogleCodeExporter]

The main page says LGPL only because Google Code technically doesn't support 
the zlib
license (their reasoning apparently being that they want to encourage the usage 
of
the mainstream licenses). And pybox2d is zlib because Box2D is.

Anyway, putting a note in and leaving it in sounds good to me. 

Original comment by sir...@gmail.com on 13 Mar 2009 at 3:16

[GoogleCodeExporter]

commited
I renamed the keycode file to pygame_keycodes.py and used it for the pyglet 
backend
as well.

Original comment by giorg...@gmail.com on 14 Mar 2009 at 8:26

• Changed state: Done