Re: __gtype and constants

On Sat, 14 Aug 2004, Alan Knowles wrote: > __type seems a bit odd - is it a little clearer to follow the existing API > > GType::from_object($object)->type > GType::from_class('GtkButton')->type Hmm, that's an idea. PyGtk implements other special proprerties, like __doc__ (which gives you back class documentation including signals, properties, etc), __signals (user-registered signals), __properties (user-registered properties), etc. What should we do about those? > -- definatly move them to the class :) - I dont think that would be the > bottleneck for performance (eg. compared to the rendering on the screen > of the widget) Okay. They'll actualy be in top-level class namespace, that is Gtk::TOOLBAR_TEXT, rather than GtkToolbar::TEXT. I was also thinking about registering classes for each enum type, for example GtkAttachOptionsType that will have ->enum_values property that lists all enums belonging to the type, and also a method to take an integer enum and give you back its name (debugging). Thoughts? -Andrei <yaragn> ever seen that movie? The Matrix? <yaragn> with those green lines of flying text? <yaragn> *THAT'S* Perl