|WikiProject Software / Computing||(Rated Start-class, Mid-importance)|
This page should have a "history" section, possibly with a timeline of all existing entries.
Should XUL be on here somewhere? http://www.mozilla.org/projects/xul/
Perhaps there could be a comparison chart/table like other things? 184.108.40.206 20:36, 14 September 2006 (UTC)
For the table header, license, price, developer, still in developement, current version, windows, linux, mac, rad......
Wrong Link on See Also
There is a link here to "Comparison of widget engines" but that is completely unrelated. "Widget engines" are applet encapsulation programs as can be seen on its page. We should probably have a separate "Comparison of widget toolkits" for this page to link to. 220.127.116.11 21:48, 27 September 2006 (UTC)
What do you call the little boxes appearing on the corners and edges of a "selected control" that let you change the size and shape of the control? --Uncle Ed 20:04, 15 November 2006 (UTC)
I've heard them called "anchors" before, if you're asking about specific terminology. Otherwise I think "resizing handle" or something would be sufficiently descriptive. Ham Pastrami (talk) 10:14, 28 January 2008 (UTC)
In need of major attention **widget toolkit, widget engine**
There seems to be some inconsistency on how people define "widget toolkit" and "widget engine" (for example, what distinguishes a "high level widget toolkit" from a "widget engine")? dr.ef.tymac 17:23, 8 December 2006 (UTC)
- The List of widget toolkits splits in two sections, one for "high-level widget toolkits", the other for low-level ones. Is this a reality, and if so, should it be documented here? --Jerome Potts (talk) 07:57, 25 January 2008 (UTC)
- This is a rough explanation. A widget toolkit is essentially a code library for GUI developers, often in the form of source code or DLL. A widget engine, on the other hand, is a binary program, designed to be lightweight and providing some scripting functionality -- essentially a customizable mini-desktop. The difference between a low-level and high-level toolkit: A low-level kit is one that does not have a central model of interaction -- the programmer must poll the OS for input messages and decide what to do with them. For example a typical input message will tell you "user clicked the mouse at coordinates (x,y)". The programmer then has to figure out which widget is at coordinates (x,y), and if there is more than one possibility, he then has to determine the z-order as well. A high-level kit takes care of this automatically, by creating a generic widget superclass and deriving or wrapping each widget using that class. The uniform interface can then be exploited to treat all widgets in the same manner using a layout manager. The manager, which has access to all the relevant details of each widget, handles all the OS messages and abstracts them into events ("user clicked ok button"), making it much simpler to write the GUI logic. Ham Pastrami (talk) 09:54, 25 January 2008 (UTC)
list with usage of widget toolkits
I would like to create a list with widget toolkits + examples (applications which use them). This page or better a new one?