Re: why do constructors return GtkWidget?

Tristan Van Berkom wrote:

Im not exactly sure what your trying to say, my understanding is that
in the modern world you create widget subclasses when you need
composite/dynamic widgets, all widgets are generally layed out in some
kind of form, or multiple forms.

Thats my understanding of the bleeding edge of the GUI, I think the OSX tools
(Xcode/Interface Builder) are a little bit ahead of us on this front
... but not by
much, considering that what we can potentially pull off is not restricted to
Obj-C or any particular platform.

Ofcourse I dont always read the headlines, so I would love to hear what
other people think is the bleeding edge to strive for in the world of GUI
development, really.

Well that's pretty much how I see it, but creating new derived widgets is not always the same thing as dynamic interface manipulation. The issue that grabbed my attention more was the notion of always using GtkBuilder. I'm just saying I love the ability create and manipulate an entire interface in code the "old fashion way". Being old and crusty (I'm 29), I take pleasure in questioning fashionable, main stream, sacred cow, gratuitously overused, technology. Near the top of that list is anything to do with XML. I miss the more agitated-old-timer-at-the-bar C code or die attitude that once was synonymous with the way I perceived FOSS. So while some articulate clearly of bleeding edge, I'll keep mumbling about often forgotten romantic concepts of yesteryear like "fun".


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]