“List of widget toolkits”的意思、由来-开放百科全书

This article provides a list of widget toolkits (also known as GUI frameworks), used to construct the graphical user interface (GUI) of programs, organized by their relationships with various operating systems.

Low-level widget toolkits

Integrated in the operating system

As a separate layer on top of the operating system

High-level widget toolkits

OS dependent

On Amiga

On Macintosh

On Microsoft Windows

On Unix, under the X Window System

Note that the X Window System was originally primarily for Unix-like operating systems, but it now runs on Microsoft Windows as well using, for example, Cygwin, so some or all of these toolkits can also be used under Windows.

Cross-platform

Based on C (including bindings to other languages)

Based on C++ (including bindings to other languages)

Based on OpenGL

Based on Flash

Based on XML

Based on JavaScript

Based on SVG

Based on .NET

Based on Java

Based on Object Pascal

Based on Objective-C

Based on Ruby

Not yet categorised

Comparison of widget toolkits

See also

References

1. ^[https://technet.microsoft.com/en-us/library/cc750820.aspx Microsoft: MS Windows NT Kernel-mode User]
2. ^Techworld: Microsoft to move graphics outside OS kernel
3. ^This version provides the core API of the .NET Framework 2.0, but its implementation of this API is still incomplete.
4. ^Web Development with TIBCO General Interface: Understanding General Interface Architecture | Model View Controller Architecture | InformIT
5. ^Qt Software to discontinue Qt Jambi after 4.5 release {{webarchive|url=https://web.archive.org/web/20090726080926/http://www.qtsoftware.com/about/news/preview-of-final-qt-jambi-release-available |date=26 July 2009 }}
6. ^http://cegui.org.uk/wiki/PyCEGUI
7. ^http://cegui.org.uk/wiki/Extending_your_Lua_Interface
8. ^http://cegui.org.uk/wiki/CEED
9. ^Migrating to client-side windows {{webarchive|url=https://web.archive.org/web/20110427131911/http://developer.gnome.org/gtk/2.24/gtk-migrating-ClientSideWindows.html |date=27 April 2011 }}: "GDK looks for the GDK_NATIVE_WINDOWS environment variable and makes all windows native if it is set. It also tries to be more compatible with the way prior versions worked in some other ways."
10. ^Coding Horror: Non-Native UI Sucks: "[…] has a cross-platform UI based on GTK, which produces predictably bland, least-common-denominator results:"
11. ^http://sourceforge.net/projects/iup/files/3.21/
12. ^http://www.tecgraf.puc-rio.br/iup/
13. ^Comparing IUP with Other Interface Toolkits: "[…] it does not have support for Unicode characters."
14. ^http://www.nanapro.org/en-us/
15. ^{{cite web |url = http://blog.qt.digia.com/blog/2009/01/14/nokia-to-license-qt-under-lgpl/ |title = Nokia to license Qt under LGPL |first = Sebastian |last = Nyström |date = 14 January 2009 |accessdate = 5 December 2013 }}
16. ^WxWidgets Compared To Other Toolkits: "Qt doesn't have true native ports like wxWidgets does. Qt does not use system provided widgets, but emulates it with themes. What we mean by this is that even though Qt draws them quite realistically, Qt draws its own widgets on each platform."
17. ^{{cite web|url=http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/ |title=Qt Modular Class Library |quote=Qt uses the native graphics APIs of each platform it supports, taking full advantage of system resources and ensuring that applications have native look and feel. |publisher=Digia |archiveurl=https://web.archive.org/web/20131101011752/http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/ |archivedate=1 November 2013 |deadurl=yes |df= }}
18. ^{{cite web |url = http://doc.qt.io/qt-4.8/qt4-styles.html |title = The Qt 4 Style API |quote = Qt's built-in widgets use [QStyle] to perform nearly all of their drawing, ensuring that they look exactly like the equivalent native widgets. |publisher = The Qt Company }}