AppKit

From GNUstepWiki

(Difference between revisions)
Revision as of 09:54, 26 October 2006
Cbv (Talk | contribs)
Update link
← Previous diff
Revision as of 19:12, 22 October 2007
Geroldr (Talk | contribs)

Next diff →
Line 1: Line 1:
The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: [[NSWindow|windows]], [[NSMenu|menus]], [[NSButton|buttons]], [[NSSlider|sliders]], [[NSTextField|text fields]], and [[NSEvent|events]]. There are also many classes that offer operating-system-independent interfaces to [[NSImage|images]], [[NSCursor|cursors]], [[NSColor|colors]], [[NSFont|fonts]], [[NSPasteboard|pasteboards]], printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking. The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: [[NSWindow|windows]], [[NSMenu|menus]], [[NSButton|buttons]], [[NSSlider|sliders]], [[NSTextField|text fields]], and [[NSEvent|events]]. There are also many classes that offer operating-system-independent interfaces to [[NSImage|images]], [[NSCursor|cursors]], [[NSColor|colors]], [[NSFont|fonts]], [[NSPasteboard|pasteboards]], printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.
-It provides functionality that aims to implement the `AppKit' portion of the [[OpenStep]] standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.+It provides functionality that aims to implement the `AppKit' portion of the [[OpenStep]] standard however the implementation has been written to take advantage of GNUstep enhancements wherever possible.
-The GNUstep GUI Library is divided into a front and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. Different back-ends will make GNUstep available on various platforms. The default GNU back-end currently runs on top of the X Window System and uses only Xlib calls for graphics. Another backend uses a Display Postscript Server for graphics. Much work will be saved by this clean separation between front and back-end, because it allows different platforms to share the large amount of front-end code. Documentation for how the individual backends work is coverered in a separate document.+The GNUstep GUI Library is divided into a front and back-end. The front-end contains the majority of the implementation, but leaves out the low-level drawing and event code. Different back-ends will make GNUstep available on various platforms. The default GNU back-end currently runs on top of the X Window System and uses only Xlib calls for graphics. Another backend uses a Display Postscript Server for graphics. Much work will be saved by this clean separation between front and back-end, because it allows different platforms to share the large amount of front-end code. Documentation for how the individual backends work is covered in a separate document.
You can find the automatically generated API documentation [http://www.gnustep.org/resources/documentation/Developer/Gui/Reference/index.html here]. You can find the automatically generated API documentation [http://www.gnustep.org/resources/documentation/Developer/Gui/Reference/index.html here].
Line 10: Line 10:
* User interface elements: table views, browsers, matrices, scroll views, ... * User interface elements: table views, browsers, matrices, scroll views, ...
-* Graphics: WYSIWYG, Postscript-like graphics, Bezier paths, image handling with multiple representations, graphical contextes+* Graphics: WYSIWYG, Postscript-like graphics, Bezier paths, image handling with multiple representations, graphical contexts
* [[Colors|Color management]]: calibrated vs. device colors, CMYK, RGB, HSB, gray and named color representations, alpha transparency * [[Colors|Color management]]: calibrated vs. device colors, CMYK, RGB, HSB, gray and named color representations, alpha transparency
-* [[Text]] system features: rich text format, text attachements, layout manager, typesetter, rules, paragraph styles, font management, [[Spell checking|spell checking]]+* [[Text]] system features: rich text format, text attachments, layout manager, typesetter, rules, paragraph styles, font management, [[Spell checking|spell checking]]
* [[Document architecture|Document management]] * [[Document architecture|Document management]]
* [[Printing|Printing features]]: print operations, print panel and page layout * [[Printing|Printing features]]: print operations, print panel and page layout

Revision as of 19:12, 22 October 2007

The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.

It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard however the implementation has been written to take advantage of GNUstep enhancements wherever possible.

The GNUstep GUI Library is divided into a front and back-end. The front-end contains the majority of the implementation, but leaves out the low-level drawing and event code. Different back-ends will make GNUstep available on various platforms. The default GNU back-end currently runs on top of the X Window System and uses only Xlib calls for graphics. Another backend uses a Display Postscript Server for graphics. Much work will be saved by this clean separation between front and back-end, because it allows different platforms to share the large amount of front-end code. Documentation for how the individual backends work is covered in a separate document.

You can find the automatically generated API documentation here.

Features

  • User interface elements: table views, browsers, matrices, scroll views, ...
  • Graphics: WYSIWYG, Postscript-like graphics, Bezier paths, image handling with multiple representations, graphical contexts
  • Color management: calibrated vs. device colors, CMYK, RGB, HSB, gray and named color representations, alpha transparency
  • Text system features: rich text format, text attachments, layout manager, typesetter, rules, paragraph styles, font management, spell checking
  • Document management
  • Printing features: print operations, print panel and page layout
  • Help manager
  • Pasteboard (a.k.a. clip board) services
  • Spell checker
  • Workspace bindings for applications
  • Drag and drop operations
  • Services shared among applications

Notes and Snippets

Class Reference Protocol Reference