Gatti Lorenzo schrieb:
In C, "properties" are unusual enough that using the word in a specialized
context like GTK+ is acceptable.
In Python "property" is not only a keyword, it is a generic OOP concept that
cannot be appropriated by some library for its specific purposes.
I would prefer a map attribute with a tagged name like gtk_properties or
gtkProperties:
mylabel.gtk_properties.use_markup
Property names should be consistently the same as GTK+ to avoid any uncertainty
about capitalization, underscores etc.
As I understand Gustavo, the reason for this discussion is, to shorten
the code for setter and getter methods for the (gtk|gobject|..)
properties. One could be to use the target language as the base. Then we
should use label.text and use this generic OO concept of the target
language. All the stuff at gtk-level should be solved in the mapping
area. Or we use the source level, gtk, than nothing needs to change, as
this is the state of the art.
I disagree with Lorenzo to introduce an unusual level which breaks the
current implementation.
--maik./
--
Mit freundlichem Gruß /
with best regards
Maik Hertha
--------------------------------------
maik [dot] hertha [at] berlin [dot] de
--------------------------------------
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
