Re: Letter to Community

On Wed, 21 Jul 2004 07:48:26 +0200 cweiske@cweiske.de (Christian Weiske) wrote: > > object orientation and we can build a very slick interface to GTK+ > > if we start from scratch. I am going to start thinking about it and > > posting RFCs on the mailing list in hopes of soliciting feedback > > from users as to how this interface can be best structured. Consider > > the connect() and connect_object() functions (a source of much > > confusion apparently): There is no reason that the second one needs > > to be called connect_object() aside from the fact that that is what > > GTK+ uses. So, one of the first questions will be, do we stick to > > GTK+ API rigidly or do we replace/rename some methods to suit us > > better? > > I think we should keep the Gtk API, simply because the Gtk people will > have thought about it before implementing it. > On the other hand it may be nice to have a really cool oo-interface to > > all the classes - with the ability to get information per reflection. > But I think the original interface should be there as well, just to > not break compatibility. > > A thing which caught my eye while writing the docs for GtkCList and > GtkCTree is that the api is somehow inconsistent; there are setters, > but no getters or instead of the getter a class variable which can be > accessed from outside (so called "Properties" in the manual). We > should take care that this doesn't happen in PHP-Gtk2. > > I for myself prefer functionNamesWithCaptitalSeparators, but php seems > to have the standard with function_names_with_lines, so we shouldn't > change the function names. > > Perhaps you've got heard enough of this; but I vote for an own php-gtk > resp. "php-with-graphial-windows" file extension as it is a pain to > start php-gtk scripts on windows if you have no way to distinguish > between "normal" php scripts and windowed php scripts. I've written a > long mail on this list half a year ago, but there were many voices > (Alan, Frank, ...) which didn't want it. But I think this is essential > > to make the usage easy for normal people. > And we should deliver a php_win.exe which takes care of registering > that particular extension (my vote for ".phpw" or ".phw" [windowed > php]) so that the user can start the script with one single click. Just like .rb and .rbw for Ruby. :) > > On windows, it is not possible to set the icon of a single window. > This is a feature which definitely should be in php-gtk2. > Not to forget the often asked "maximize window" function... Well, that kinda is up to Gtk2, not anything that can be implemented from the PHP side... Of course some low-level Gdk-hack might be done, but that would create a non-standard API, which isn't exactly what I'm hoping for. But as luck would have it Gtk2 has both the set_icon() (don't know if it works on Windows though) and the maximize(), so that's all good. Personally I think that sticking as much to the original API is the best option... Of course a single hack or two might be implemented, but in general I think it's best to stick to the standard... That is what it's there for, right? Well, a couple of cents dropped. :) Madsen > > > Documentation is worth it just to be able > > to answer all your mail with 'RTFM'. -- Alan Cox > I have this hope, one day.. > > > Regards/MfG, > Christian Weiske > -- > XMMS is playing now: > Sportfreunde Stiller - Laut Anhören > -- Anders K. Madsen --- http://lillesvin.linux.dk "There are 10 types of people in the world. Those who understand binary - and those who don't."

Attachment: [application/pgp-signature]