Talk:GObject

message: I removed some things that made the article C++-centric:
Unlike C++, object orientation with GObject does not allow multiple inheritance.
Important drawbacks of the GObject framework are the absence of operator overloading, exceptions and namespaces. Despite some missing features GObject is easier to learn and get started with than object orientation in C++.
If you want C++ (in the STL and Boost's heavily templated style) features, look at gtkmm, the C++ binding of GTK.
Perhaps some mention of alterative C OO libraries would be appropriate. Do such libraries exsist?
GObject is heavily runtime oriented, and as such interfaces very badly with compile-time type systems such as C++.
GTKmm is a possible wrapper of GObject/Glib/GTK+, but it's not perfect.
Internal link "class structure" send user to wrong page.  —Preceding unsigned comment added by 83.21.0.21 (talk) 16:49, 5 October 2007 (UTC)
thread_title: Untitled

message: Many developers/admins have issues with icons installed that are "not found" or "G_IS_OBJECT",  Feature improvements have added complication before fixing the issues, resulting in "icons wont load" bugs since the 1990's still being an issue, for both non-gobject developers or users.
It's true depending on gdk gtk used to be simple, and still works trivially.  However to get most any today's apps happy (ie, able to present a button with an icon), an insideous cross-dependancy problems arise in building gtk (then part of gnome for icons) which requires several not one build of serveral packages and still fails without "middle-man special configurations" (ie, c++ namespace for X11 Display failure).  When trying to find help one is merely told to try a newer version, when trying to find help on newest version one is told "use the binary, not all fixes are out".  Lack of acknowlegement also has been a gnome issue since 90's.
Simple apps (ie, eog image viewer) now require ld.so to load 100 dependancy libs before showin a simple image on X11 (which requires 0 depends and a small binary).  Apps that were avalable when all else fails (ie, gedit basic editor) now are hacked to be broken with depends as well (ie, gedit now wont load if gobject-instrospection, and many other 5th toe features, are not ready), in other words it's all-in-each or none, is your choice.  
In the past Gnome had warned programmers not to depend on gnome libs except for gnome-specific desktop items - however today they seem to ignore this and suggest apps be made and also libraries be inserted which will create a need to n-fold compile the gtk toolchain to absorb cross-depends.
Today gdk/gtk is heraled as cross-platform to microsoft product.  However it's history is copy lefted from the Gimp project (GW usa., unix software from a university, allot of linux is, that and gleened from commercial unix products).  Cross platform meant cross-unix platform: not "microsft may hack in any kind of changes into competing product for their purposes" (i would say win32 wasn't even released when Gimp was being made).
In summary gnome,gtk,gdk etc began as open source GPL however it quickly became and still is a thing which works for, and is controlled by, un-named few.  Everyone else gets build failures and continual chaffed when trying to find answers.  Like so many things these days: there is simply no accountability or reasoning to choices made that impact ... too many things.
As a "great way to save time using X11 wrappers instead of using X11 code" ... it may be for some but not all, and some problems seem to be intentionally never fixed and made worse.
In short: it's a legacy that's been depreciated for everyone but a few before it's been released  — Preceding unsigned comment added by 72.219.201.25 (talk) 16:49, 27 August 2015 (UTC)
thread_title: Problems