![gtk vs qt gtk vs qt](https://i.stack.imgur.com/KY7ph.png)
An example is Hugelist which implements a list box that can handle more than 1,000,000 items without CPU or memory penalties.įor how this is possible, see: Mass-widget. It is possible -and easy- to write some megawidgets entirely with Tcl and Tk.
![gtk vs qt gtk vs qt](https://i.stack.imgur.com/xE886.png)
#Gtk vs qt code
Tk, on the other hand, will usually require you to code in C to create an entirely novel widget' (but, it is actually quite rare that this is needed, and this is possibly why Tk is so much easier to use - many, many so-called 'new widgets' can be implemented simply as mega-widgets, without any C).
![gtk vs qt gtk vs qt](https://celettu.files.wordpress.com/2009/05/arora.jpeg)
This means Java is very, very complicated, but allows you to create new widgets without needing to code in C. The real question here is why no other toolkit has adopted tags to such good effect.Ī big difference between Tk and Java's AWT/ Swing is that Java provides not just a set of widgets, but also the entire infrastructure for creating new widgets, drawing graphics (manipulating individual pixels), etc. At a higher level, it seems increasingly likely that Tk is better off for being object-based, but not object-oriented. Why has Tk aged so gracefully? It enjoys several specific technical advantages, discussed below. Beginners also find it easier to start with Tk than any other system, with the possible exceptions of rather hermetic and platform-specific technologies, as well as members of the *Card family. Well into its second decade of successful application, Tk remains the most reliable cross-platform GUI toolkit, besting even Java's AWT in its effective coverage. While fans of wxWidgets, Qt, GTK+, and other GUI toolkits often deride Tk as "old-fashioned", a good case can be made that it's merely mature.