Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
(Nearly) full tickless operation in 3.10
In what (concrete) way?
>It really doesn't make much sense to build a GUI toolkit on top of C
>a GUI toolkit is crying for object oriented designs
Yes, and that's why it's object-based (GObject is the root object).
Sobotka: Why GIMP is inadequate
Posted Jan 13, 2011 5:54 UTC (Thu) by romanfi (guest, #72329)
> In what (concrete) way?
- compatibility between platforms
- structure of GUI components
- the designer IDE (here I'm not 100% sure)
A GUI is composed of elements that in some natural way inherit from each other. E.g. there are push buttons, radio buttons, which are all buttons. And buttons and many other elements are widgets. The main windows, dialogs and so on are frames or windows.
Motif already had an object oriented design, implemented using standard C. They even had public and private data members, faked using two header files defining two structures for every element, one of them for Motif itself, including the private members, the other one with just the public part, layout compatible. They've got virtual functions, implemented with function pointer arrays, and so on. And I can see the same thing in GTK.
So why not using the right tool for the job?
Posted Jan 13, 2011 20:09 UTC (Thu) by daniel (subscriber, #3181)
Posted Jan 13, 2011 20:55 UTC (Thu) by Trelane (subscriber, #56877)
Posted Jan 18, 2011 17:56 UTC (Tue) by daniel (subscriber, #3181)
I meant pointer casts that attempt to simulate a C++ class hierarchy using C structs with casts.
Posted Jan 13, 2011 20:53 UTC (Thu) by Trelane (subscriber, #56877)
This is pretty nebulous. Please be specific in what ways Qt is better than gtkmm in this regard.
Again, this is very nebulous. Be specific.
> structure of GUI components
Yet again, this is not at all specific. What precisely is better about Qt's "structure" than gtkmm's? List examples where you can.
> the designer IDE (here I'm not 100% sure)
This is simply a laundry list of things that are "better" (and most of the items aren't concrete examples of anything; they're categories) and nothing more. Please be specific with your argument and back it up with examples.
I'm going to learn Qt for maemo, so I hope to be less ignorant of Qt in the near future, as time permits. I do have a degree of experience in gtk and gtkmm, so I want to know what you think is failing (and perhaps even fix it). I can't fix "documentation"; I can fix the fact that there aren't any tutorials on how to frob the critical blort property in gtk/gtkmm, though.
> A GUI is composed of elements that in some natural way inherit from each other. E.g. there are push buttons, radio buttons, which are all buttons. And buttons and many other elements are widgets. The main windows, dialogs and so on are frames or windows.
Honestly, right here you sound like you haven't even looked at gtk+/gtkmm documentation, let *know* anything at all about it.
How about looking at the "Object Hierarchy"
> So why not using the right tool for the job?
I think you've confused me for you. I'm wondering why you think gtk+ is inferior to Qt in all situations (implicit in the statement "[gtkmm is]That's not as good as Qt." which is without qualifications. I don't mind Qt at all, and would like to improve gnome/gtk.
Posted Jan 13, 2011 21:00 UTC (Thu) by Trelane (subscriber, #56877)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds