Conversation
Notices
-
@ronnypfannschmidt I would be happy to port !pygtk to !python 3.
-
@ronnypfannschmidt I'd be happy to.
-
@spacehobo like one with proper bindings that wasn't 30% boilerplate code? probably. i simply don't want qt because i like gtk.
-
Something that made good use of !python's sequence/mapping/etc. interfaces for appropriate collections of attributes, for example.
-
@spacehobo as long as it isn't still more complicated to understand
-
Er, I believe I argued for the opposite when I asked that it be *pythonic*
-
@spacehobo while pygtk is numbingly tedious to code in, it's not difficult to understand. rarely, but sometimes pythonesque != easy
-
@openuniverse So you think that using (say) dictionaries or lists is harder to understand than dozens of proxies for C function calls?
-
@spacehobo @openuniverse I think lists are pretty good, until you try to do anything multi-dimensional. It can be very annoying! !python
-
but surely they're clearer than calling foo.get_last() foo.get_next() foo.get_index(i) in a widget toolkit interface
-
@spacehobo absolutely not. i guess i was being pessimistic forno reason, sorry. and lists are the greatest thing ever.dictionaries are cool.
-
in particular, !python dictionaries are a great way to expose attribute lists in underlying libraries
-
@spacehobo yeah if you tried that with lists you'd have to account for possibility of duplicate names, dictionaries could prevent that.
-
Glad to hear that someone's thinking of doing more than just a 1:1 mapping of functions!
-
All Identi.ca content and data are available under the