You seem to be under the impression that Gtk+ lacks classes and inheritance. This is not the case. Gtk+ uses a run-time based object system. This is somewhat similar in concept to what Objective C and python do, and in fact it has been argued that such systems have certain advantages compared to statically typed systems such as C++.
Sure, the interface sucks. But that's no reason to throw out a perfectly good HTML engine. Trust me, it's set up so that you could drop it into a standard GTK interface fairly easily.
Re:Would of had a KDE Gimp months ago
on
KDE 2.0 in Action
·
· Score: 1
This was back when Qt was still closed source -- it would have violated GPL to distribute it, which is why the gimp authors put their foot down. I think QPL may also be incompatible with GPL, soo...
GNOME (specifically, Havoc Pennington) is developing something similar to what you described, in which a single configuration API can output to different formats -- the default is XML, but in theory you could have such systems as LDAP used. In case you're interested, a prototype is available in cvs module gconf.
I don't see what this has to do with the main point of the previous poster, which is that gnome had CORBA from the very beginning. No matter the fact KDE may have had CORBA before GNOME, it did not have CORBA at its beginning.
libGlade is pretty cool -- it generates a gtk interface on the fly based on glade XML files. Add the fact that gnome-perl has bindings for it, and you've got a pretty nice deal.
If you like VCL, I'd suggest VDK, a C++ wrapper around Gtk which is similar to VCL/OWL. It also has an IDE, VDKBuilder, which is designed to feel like C++Builder from Borland. As for a good IDE/GUI builder for pure Gtk, I'd recommend a combo of gIDE and glade -- glade is really impressive, it supporsts multiple Gtk language bindings and can even generate XML widget layout files which can then be loaded dynamically, at runtime.
Actually, my current Java IDE of choice is NetBeans, which is written in Java -- it's one of the main reasons I chose it. It's available for JDK 1.1 or 1.2 with Swing 1.0 or 1.1. Translation: It'll probably work with whatever modern JRE you currently have installed:-)
And I suppose that when you want to configure windows, you edit the registry by hand with a hex editor? In the case of X alone, virtually all linux distributions come with programs to configure X for you...just tell them the hardware or let them auto-detect and off they go. Even Slackware has one.
First off, let me say that I agree with you, there are parts where GNOME is clunky. However, the most important thing we as users can do is to give helpful explanations of exaclty, and I mean exactly, of how it is clunky. There's no way the developers can read your mind. You've made a good start with your list, but it's not enough to let the developers know how they can fix it. If you gave the GNOME team a detailed of which behaviors should be changed in what ways, then I'm certain they'd be glad to consider it. Otherwise, all we're really doing is just whining.
Slashdot Mirror
You seem to be under the impression that Gtk+ lacks classes and inheritance. This is not the case. Gtk+ uses a run-time based object system. This is somewhat similar in concept to what Objective C and python do, and in fact it has been argued that such systems have certain advantages compared to statically typed systems such as C++.
Reminds me of Starship Titanic -- one of the main characters had to keep bothering the bomb so it would lose count and have to start over :-)
Actually, GNOME has a HAL applet already :-)
Sure, the interface sucks. But that's no reason to throw out a perfectly good HTML engine. Trust me, it's set up so that you could drop it into a standard GTK interface fairly easily.
This was back when Qt was still closed source -- it would have violated GPL to distribute it, which is why the gimp authors put their foot down. I think QPL may also be incompatible with GPL, soo...
GNOME (specifically, Havoc Pennington) is developing something similar to what you described, in which a single configuration API can output to different formats -- the default is XML, but in theory you could have such systems as LDAP used. In case you're interested, a prototype is available in cvs module gconf.
I don't see what this has to do with the main point of the previous poster, which is that gnome had CORBA from the very beginning. No matter the fact KDE may have had CORBA before GNOME, it did not have CORBA at its beginning.
Does that include PyKDE? What about KScript? :-)
libGlade is pretty cool -- it generates a gtk interface on the fly based on glade XML files. Add the fact that gnome-perl has bindings for it, and you've got a pretty nice deal.
Forking a project counts as "NIH", doesn't it?
Ettrich does not seem to stoop to the level of critiquing Gnome on SlashDot, but rather spends his time coding...
---
I suppose he wouldn't bother to defend himself when people resort to name-calling, either.
If you like VCL, I'd suggest VDK, a C++ wrapper around Gtk which is similar to VCL/OWL. It also has an IDE, VDKBuilder, which is designed to feel like C++Builder from Borland. As for a good IDE/GUI builder for pure Gtk, I'd recommend a combo of gIDE and glade -- glade is really impressive, it supporsts multiple Gtk language bindings and can even generate XML widget layout files which can then be loaded dynamically, at runtime.
Actually, my current Java IDE of choice is NetBeans, which is written in Java -- it's one of the main reasons I chose it. It's available for JDK 1.1 or 1.2 with Swing 1.0 or 1.1. Translation: It'll probably work with whatever modern JRE you currently have installed :-)
And I suppose that when you want to configure windows, you edit the registry by hand with a hex editor? In the case of X alone, virtually all linux distributions come with programs to configure X for you...just tell them the hardware or let them auto-detect and off they go. Even Slackware has one.
First off, let me say that I agree with you, there are parts where GNOME is clunky. However, the most important thing we as users can do is to give helpful explanations of exaclty, and I mean exactly, of how it is clunky. There's no way the developers can read your mind. You've made a good start with your list, but it's not enough to let the developers know how they can fix it. If you gave the GNOME team a detailed of which behaviors should be changed in what ways, then I'm certain they'd be glad to consider it. Otherwise, all we're really doing is just whining.
Not quite yet....remember, the real guide spoke out loud...(and transmitted a mental translation matrix for the babelfish) :-)
Star Office is available on windows, you knob. As well as OS/2 and Mac. And I believe Applix is available on windows too.
Gtk 1.2 is out.
And I assume you're basing this on your own developmental experience?