You are not logged in.
Pages: 1
I'm trying to decide which toolkit to stick to and become proficient in. Though I'm sure it would be good to learn multiple toolkits, I rather to stick to just one. I'm debating between gtk and tk. No qt because I've yet to get a qt application working in windows, and right now I'm stuck mainly developing in windows with linux in mind. I'm programming in Ruby, so if you want to suggest an alternative to the 2 listed above please link me to the Ruby bindings for that toolkit .
I don't really care about skinability, I'd rather focus on functionality and performance rather than aesthetics.
Any insights into gtk or tk would be appreciated aswell.
Writing stories for a machine.
Offline
Ruby distribution usually comes with Tk bindings built in. Its why I considered it. The tk examples I've been playing with load faster than their equivilant in GTK. Maybe its just that I was loading them in windows, either way, it just seems fast. I like lean aswell .
Writing stories for a machine.
Offline
More applications out there are GTK, I dont frequently, or even at all use any TK apps. I programmed utilising TK before, so I dont know how it handles as a toolkit, but i do know it's butt ugly.
Take a look at AMSN, the number one requests for change there are for anti-aliased fonts, proper unicode support, and something less ugly.
iphitus
Offline
Have you tried wxWindows?
Offline
wxWindows just uses gtk bindings doesn't it?
Writing stories for a machine.
Offline
wxWindows has support for any GUI toolkit, provided you have the software and configuration set up for it.
I personally just use plain ol' GTK. I like the way it's organized and I don't have to do a lot of thinking when I use it, I just plop some widgets down, set up some signals, and then look at my pretty interface that I constructed in less than an hour. Not many machines that run X don't have GTK installed either, so you don't have to worry about people downloading dependencies. It makes me happy
Offline
If you're already running a program that uses gtk (or an other toolkit), most of the libraries are already loaded in the memory. So if you want (startup/load) speed, it's better to use 1 toolkit.
GTK is also a well maintained and tested toolkit, probably better than tk (but i don't know anything about tk).
Offline
I thought this sounded familiar:
http://bbs.archlinux.org/viewtopic.php? … ui+toolkit
Offline
Pages: 1