GNUstepWiki - User contributions [en]

NSWindow

2013-08-24T02:45:03Z

Awiebe:

The NSWindow class creates a drawing surface and fills the background based on its style mask.
==XIB Fields==
'''N.B.''' Unarchiver class = NSWindowTemplate

{|
! align="left"| Name
! Type
! Description
|-
!NSWindowStyleMask
|int
|A bitmask that is interpreted by the window to select it's style. [https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSWindow_Class/Reference/Reference.html#//apple_ref/doc/constant_group/Window_Style_Masks Values]
|-
!NSWindowBacking
|enum NSBackingStoreType : int
|Retained,Non-Retained,Buffered
|-
!NSWindowRect
|NSRect
|The initial window size.
|-
!NSWTFFlags
|int
|A bitmask, don't know what it does.
|-
!NSWindowTitle
|NSString
|What is the shown in the window titlebar.
|-
!NSWindowClass
|NSString
|The type of window the template represents.
|-
!NSViewClass
|NSString
|The name of the class backing the window's content area
|-
!NSWindowContentMaxSize
|NSSize
|Self explanitory.
|-
!NSWindowContentMinSize
|NSSize
|Self explanitory.
|-
!NSMinSize
|NSSize
|Seems to apply to the content view rather than the window.
|-
!NSMaxSize
|NSSize
|Seems to apply to the content view rather than the window.

|-
!NSScreenRect
|NSRect
|The screen size on which the view was encoded(used for scaling), should probably be an NSSize, but don't argue with Apple, or compatability issues will arise.

|}

==See Also==

NSAlert

2013-04-15T08:13:22Z

Awiebe:

{{stub}}
NSAlert is a modal dialog or [[sheet]].

<syntaxhighlight lang="c_max">

<code>

/**
NS Alert Example*/

NSAlert* a = [ NSAlert alertWithMessageText:@"title" defaultButton:@"ok" alternateButton:@"cancel" otherButton:nil informativeTextWithFormat:@"more information ];

//Run as a dialog
NSInteger returnCode = [a runModal];
switch(returnCode)
{
case 1:

//ok
break;

case 2:

//cancel
break;
}

//Attach to window
[a beginSheetModalForWindow:windowP modalDelegate:self didEndSelector:@selector(alertDidEnd:) contextInfo:nil];

- (void) alertDidEnd:(NSAlert *)alert returnCode:(NSInteger)returnCode contextInfo:(void *)contextInfo
{
switch(returnCode)
{
case 1:
//ok
break;
case 2:
//cancel
break;
}
}
</p>

</syntaxhighlight>
==See also==
* [https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSAlert_Class/Reference/Reference.html Apple on NSAlert]

User FAQ

2013-04-15T07:56:41Z

Awiebe: /* Why not use framework bundles? */ changed dynamic link to symbolic link

== GNUstep General Information ==

=== What is GNUstep? ===

GNUstep is the Free Software Foundation's effort to implement Apple, Inc's (formerly NeXT Software, Inc.'s) [[Cocoa]] APIs (formerly the [[OpenStep]] Standard). Also we are building developer and user applications based on this standard which may be used to form a complete desktop experience. For more details, take a look at the [[Introduction to GNUstep|introduction]].

=== What is Cocoa? ===

Cocoa is an Application Programming Interface (API) for creating applications using the Objective-C language. It was published by Apple, Inc.(Formerly NeXT Software, Inc.).

Cocoa consists of three parts: the `Foundation Kit', a library of non-graphical objects; the `Application Kit', a library of objects useful in creating graphical applications; and the Quartz display system.

=== What platforms does GNUstep run on? ===

See the list of [[Platform compatibility|supported platforms]] for information on what machines GNUstep builds on and what the status of the ports is. Probably a few days porting to any other UNIX system where current gcc compilers and gdb debugger work.

=== Does GNUstep run on Windows? ===

The primary targets for GNUstep are free UNIX system-based platforms such as GNU/Linux and FreeBSD.

That being said, the whole environment has been ported to [http://www.mingw.org MinGW environment]
and the non-gui libraries are reported to work well.

The GUI library uses the win32 backend library to work under Windows. The backend library is a thin layer that converts the GNUstep methods to handle drawing of GUI elements to calls to the Windows API. This project is currently in beta.

=== What is GNUstep's position towards KDE and the GNOME project? ===

You can use GNUstep with GNOME and/or KDE (See [[IconManager.app]]). GNUstep displays on top of X11. You can still do programming in C (since Objective-C is just a super-set of C), and if you're using gcc 4.1 or later, you can mix C++ and Objective-C code in the same file.

GNUstep, is much more than a window manager or desktop environment. It frees you to develop cross-platform applications without the work of developing an OS independent framework from scratch. It gives you lots of basic functionality, from font panels to Unicode strings to distributed objects.

=== How can I get GNUstep? ===

Many distributions include packaged versions of GNUstep (Debian, etc.). To compile from scratch, download the GNUstep Startup package or take a look at the [[Platform compatibility]] list. Get the latest releases from [ftp://ftp.gnustep.org/pub/gnustep/core FTP].

=== How do you run GNUstep? ===

You are presumably under the misapprehension that GNUstep is some sort of program or window manager. It isn't! GNUstep is a whole load of things -- primarily a set of libraries for developing software. At present, it's those libraries, plus various command-line based support tools and service providing daemons, plus various GUI development tools, a GUI desktop/workspace application, etc. At no stage will you ever 'run' GNUstep -- you will run applications and tools and will use it's services. At some point you may well find packages distributed as 'GNUstep' systems in the way that you get 'GNU/Linux' systems packaged today. For instance, look at the [http://io.debian.net/~tar/gnustep/ GNUstep Live CD].

If you want to see a sample GUI application running you need to build GNUstep and look at the example applications in the gnustep-examples package. Build 'Finger' or 'Ink' and start it with 'openapp Finger.app' or 'openapp Ink.app'

For the best look, use WindowMaker (preferred GNUstep window manager) as your window manager. In others desktops (that have its how window manager) you can use [[IconManager.app]]

=== Is there a web site? ===

See [http://www.gnustep.org/ GNUstep Website] and [[Main_Page | GNUstep Wiki]].

=== When is GNUstep intended to be available? ===

It's usable now. Major releases are made about every six months. However, if you are a serious developer, it's probably best to use the latest snapshots.

=== What is usable? ===

Most of GNUstep is quite usable and there are many complex applications that work well. However, GNUstep does not completely track the latest changes that Apple makes to their interface and there are still some parts that need some work). This means many applications will run quite well. Applications that require very complex text handling and some unusual features and/or some of the latest additions to Cocoa may not work as well. See the Compatibility and layout section for more information.

== Compiling and Installing ==

=== How do I compile GNUstep on my machine? ===

Read the file 'GNUstep-HOWTO', which comes with the GNUstep distribution (gnustep-make), and also is available separately on the GNUstep web site. To check beforehand, take a look at the [[Platform compatibility]] list.
NB. gnustep-base-1.23.0 is the last release which supports pre gcc-4.0.0 compilers. For later releases you will want to ensure you have a more recent Objective-C compiler.

=== Are there any precompiled packages available? ===

Check the [http://www.gnustep.org/resources/sources.html Download Section] for links to RPMs, Debian packages, and BSD ports. There are also Windows installers, Mac OS X binaries and others.

=== How do I start the applications I just installed? ===

First, read http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto_4.html#SEC7 to make sure you have set up your environment correctly. Then from a terminal enter:

openapp Application.app

=== What are these type and size warnings? ===

These warnings:
/usr/bin/ld: warning: type and size of dynamic symbol
`__objc_class_name_NSConstantString' are not defined
are a common occurence and are due to a mismatch between the gcc compiler and the ld linker. They don't do any harm so they can be safely ignored. They have been fixed in the 3.1 version of the GCC compiler.

=== What are these import warnings? ===

Do you get this obnoxious warning whenever you compile an application, tool, or Objective-C program:
warning: using `#import' is not recommended
[...]
Up until version 3.4 of the GCC compiler, the #import directive was improperly implemented. As a result, the compiler automatically emitted a warning whenever the #import directive was used. As of gcc 3.4, this problem has been fixed, so presumably, this warning is no longer emitted when code is compiled. If you are using an earlier compiler, you can suppress these warnings by adding -Wno-import to your include (cpp) flags.

== Compatibility and Layout ==

=== Can I run NeXT OPENSTEP or Mac OS X programs on GNUstep? ===

You can't run these programs on GNUstep, but if you have the source code for the programs, you should be able to port them to GNUstep and compile them. Whether or not you will be able to run them depends on how complete GNUstep is at the time.

=== Is GNUstep following changes to OpenStep and Mac OS X? ===

Yes, gnustep-base already contains the documented changes in the Foundation library. GNUstep aims to be compatible with both the OpenStep specification and with Mac OS X. It should be easy to write an application that compiles cleanly under both GNUstep and Cocoa. GNUstep can be expected to support the OSX 10.4 version of the Cocoa APIs (we consider it a bug if it does not), but also actually supports many APIs from OSX 10.5 and later (contributions of methods from these later versions are very welcome).

=== Do we have to have the NEXTSTEP look and feel? ===

GNUstep is aiming for something like the NEXTSTEP 3.3 look and feel. Although we don't want to force anyone into this, a lot of the power and ease of use comes from this feel. The look of GNUstep is something different -- buttons and other widgets can look different but still act the same way. We hope to implement themes which will allow this.

For a different desktop feel please see [[Themability]].

=== What's up with the directory structure? ===

First of all, GNUstep uses a slightly different directory structure than NEXTSTEP or Mac OS X. Part of this is historical, part is because we can't do things the same way (see the section [[User FAQ#Why not use framework bundles?]]). Although currently the structure is very similar to the one used in Mac OS X.

It's also possible to configure GNUstep run using the standard FHS directory structured used under GNU/Linux
and other unices so that it blends better in the host environment.

=== Why not use framework bundles? ===

Framework bundles are much more difficult to port and to use, and are very unnatural on a UNIX system; extremely unnatural on Windows. In a framework bundle, the shared dynamic library is inside a framework wrapper directory. Because of this, the dynamic linker can't find it.

We have frameworks, so how do we work around that? Well, we create symbolic links from a directory inside the dynamic linker path into the framework, which work, but then you can't move the framework anywhere else on the system, otherwise you break the link, such that nothing will find the framework any longer! On systems without symbolic links, like Windows, we can't even do this! We have to copy the library from the framework into the dynamic linker path, but that is simply a shared library then! Absolutely no difference. You put the dynamic library in a system directory in the dynamic linker path, and associate with that library a resource directory. OpenStep for Windows did that, and still called them frameworks. So we can do the same, and call our libraries frameworks.

Shared libraries are all in a flat directory where the dynamic linker can easily find them. This is how it works on Unixoids, Windows and probably most other systems. The OpenStep API requires us to provide some stuff for frameworks, like creating and registering a framework object automatically each time a framework is used (linked at runtime, or linked into the app), and attaching to it the list of classes inside the framework, which are not particularly trivial to implement and might make trouble when porting, as they depend on playing with the linker and the object file format. However, shared libraries are handled by the operating system for us, so we never have to use these facilities.

It's easier for Apple's Mac OS X. They can modify the system linker, compiler, the system dynamical linker as they please, because they have full control over the platform these run on. They can modify the system to support frameworks natively. GNUstep, however, is meant to run on many different platforms, platforms which we don't control (Windows, Sun Solaris, Darwin, GNU/Linux, UNIX system variants) and which have different linkers and do not support frameworks natively. On some systems it's difficult to just load a bundle or compile a shared library!

So building the core libraries as 'libraries' means that it's much easier to port them, and it's much more difficult to break them. Sure, frameworks have a bundle of resources associated with it -- but we can very easily associate a bundle of resource with a shared library, no reason why not. We are doing it. So please note that GNUstep libraries are meant to be much similar to Mac OS X frameworks. They are composed of a shared library and associated with a bundle of resources. There is a difference in terminology, in where the resources are installed, and possibly a slight difference in the NSBundle API to get to the resource bundle (anyway, it's a one line difference between Mac OS X and GNUstep, so it looks like very easy to <tt>#ifdef</tt>).

In other words, GNUstep libraries are meant to basically do the same as frameworks do on Mac OS X, but to be portable to very different platforms (such as Windows).

=== Why not use native widgets? ===

The GNUstep GUI code is divided into two libraries ... the gui proper (gnustep-gui), which handles most of the work of implementing the AppKit API, and the backend (gnustep-back) which handles the interface to the native operating system. The display server (GSDisplayServer) is one of the two classes which provide the main interface between the two parts. The other class is the graphics context (NSGraphicsContext). The later does the actual drawing whereas the former manages windows and events. This separation is just great to have multiple graphics backends like art, xlib and cairo share the same x11 display server.
So code in gnustep-gui calls methods of the display server, and code in gnustep-back translates those calls to native calls of the system you are running on.

This means that application developers use the OpenStep/GNUstep/MacOS-X AppKit API to write their applications, and the gnustep-back library uses the native functionality to do the job where possible.
For instance, you do cut and paste or DnD using the OpenStep API for that, and on an ms-windows system, the actual calls to perform the operations are the native win32 ones. ie we leave the job to the operating system, so cut and paste from gnustep applications can interact with cut and paste from native win32 applications.
Of course, where the two APIs (OpenStep and win32) operate in very different ways, the conversion between the two is hard, but often the layer between the two is quite thin.

One area where there is not much scope for overlap is drawing within a window ... the way that the OpenStep API operates is so different from ms-widnows or X-windows that high level code for drawing things inside a windows using the native operating system generally cannot fit with OpenStep, so the gui library does all the drawing inside the window with quite low level code rather than trying to map OpenStep 'controls' to native 'widgets'.

Since the basic design of the two (frontend and backend) libraries is, to draw OpenStep controls rather than try to map to native controls (because that's generally easier and makes the code very portable), we generally make no use of native widgets.
However, the gui frontend can dynamically load a theme engine to draw it's controls, and a theme engine is free to try to draw parts of a window using its own code ... so it can use the native controls where that's a practical solution.

== Troubleshooting ==

=== Problems compiling (loading shared libs) ===

If you get something like

plmerge: error while loading shared libraries:
libgnustep-base.so.1: cannot open shared object file: No such file or directory

or this:

Making all for service example...
make[2]: *** [example.service/Resources/Info-gnustep.plist] Error 1
make[1]: *** [example.all.service.variables] Error 2
make[1]: Leaving directory `/home/multix/gnustep-gui-0.8.6/Tools'
make: *** [internal-all] Error 2

This means your GNU make is being overly protective. When you try to become root (e.g. to install something), certain environment variables like LD_LIBRARY_PATH are unset in order to reduce the possibility of a security breach. If you are becoming root to install something, you need to exec the GNUstep.sh file as root, just as you do when you login. Although for simplicity, you can also try this:

make LD_LIBRARY_PATH=$LD_LIBRARY_PATH

You could also be having problems with gcc. gcc 2.96 does not work (Mandrake 8.1, perhaps others). Use a different compiler, like gcc 3.x.

=== Problems compiling (GNUstep Internal Error) ===

If you get

GNUSTEP Internal Error:
The private GNUstep function to establish the argv and environment
variables was not called.
Please report the error to bug-gnustep@gnu.org.

when compiling the gui library, there could be several things wrong. One is that you installed the gnustep-objc library, but the compiler found another Objecive-C library (like the one that came with gcc). If you are using gcc 3.x, DO NOT use the gnustep-objc library.

There could also be a mismatch between the base and gui library versions. Make sure you have the latest release of each library installed.

=== Problems with Alt key ===

It's possible the Alt key is not where you think it is or is defined incorrectly. Try running the GSTest application, KeyboardInput test (located in the examples package at [ftp://ftp.gnustep.org/pub/gnustep/core FTP]) to test it. See [http://www.gnustep.org/resources/documentation/User/Gui/KeyboardSetup.html keyboard setup] for information on how to change the settings.

If you are using WindowMaker, it's possible it is grabing this key and using it for itself. To check, open Window Maker's WPrefs and go to the Mouse Preferences. Then use another value for the "Mouse grab modifier" (bottom right). That will allow you to alt-drag things.

=== Problems with gcc3 ===

Don't forget you need to update binutils and libc also.

=== Problems with fonts ===

Why do the characters get changed to asterisks ('*')?

The problem you are getting come from the fact that the xlib backend (when not using Xft) will only use one fixed X font for a given font name. If the font "helvetica" is used inside of GNUstep the one selected X font, in your case "-*-helvetica-medium-r-normal--12-*-*-*-p-*-iso8859-1" is used. So only characters (or glyphs) that are available in that font can be displayed. The selection of which font name to use happens inside the font_cacher and is more or less at random (the order fonts are listed by the X system).

You can influence the fonts that are available by setting:

defaults write NSGlobalDomain GSFontMask "*iso8859-13"
font_cacher

(or using a different character set, like iso8859-2). This is really a bug in GNUstep, but it hasn't been fixed yet.

The other option is the use the art backend, which handles fonts much better. When compiling gnustep-back, start with

./configure --enable-graphics=art

=== No characters displayed ===

When using the xlib backend, no characters are displayed in any GNUstep applications.

The xlib backend has font anti-aliasing turned on by default. It's possible that GNUstep can't find any fonts on your system that can be properly anti- aliased. Try

defaults write NSGlobalDomain GSFontAntiAlias NO

to turn off font anti-aliasing.

=== No Makefile ===

I tried to compile something and I get:

GNUmakefile:27: /Makefiles/common.make: No such file or directory
GNUmakefile:39: /Makefiles/aggregate.make: No such file or directory
gmake: *** No rule to make target `/Makefiles/aggregate.make'. Stop.

Make sure you have installed the gnustep-make package and also type something like

source /usr/GNUstep/System/Library/Makefiles/GNUstep.sh

depending on your GNUstep's installation path.

You can put this line in your `.profile' or `.bash_profile' file so that it is done automatically when you log in.

== Misc ==

=== Why don't you just have Gorm output Renaissance files? ===

Philosophical and architectural incompatibilities.

=== Is there a way to install GNUstep on Mac OS X? ===

Yes! Please see [[Platform:BSD#Mac_OS_X | MacOS X installation notes]].

=== Is there any way to use gnustep-make and gnustep-base without using openapp/opentool? ===

opentool is obsolete and you should be able to run command-line programs directly from your
shell prompt like any other command-line program.

openapp is useful to run applications but in standard situations you can also run directly
the program from within the .app folder.

=== Can GNUstep help with porting applications from MacOS-X? Is there any HOWTO on that? ===

See for example Tamsys.

=== How difficult it should be to port it to Linux and GNUstep? ===

Somehow relevant may be discussion on How to port to GNUstep Answered. Unfortunately this link is broken now. Dredge around in the google discussion group, I guess. I couldn't find anything helpful.

=== Can I deploy my GNUstep application without requiring people to install GNUstep? ===

No. Compare it to running Java applications without people requiring to install Java runtime environment.

=== How can I get more information on Objective-C ? ===

Take a look at the [[Objective-C]] page.

[[Category:FAQ]]

XIB

2012-12-27T08:41:18Z

Awiebe:

As of MacOS 10.3 Apple moved away from the binary encoded nib files, and towards the xml encoded XIB files, for their interface definitions.

The xib file format is actually quite easy to understand, it is the responsability of the object encodeing and decoding, it to insure that it's attributes are read correctly.

Here is a [http://www.multiupload.nl/B2A8HXDBI0 commented example] of a XIB file. For easy reading open it in a syntax highliting editor using XML highlighting.

To provide cross platform compatability, review the "XIB fields" section of the gnustep wiki article on the interface you intend to provide a codec for. Also be sure to read the apple article on [[#See Also|KVC]].

==See Also==
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueCoding/Articles/Overview.html Apple on KVC] - Encoded objects must be KVC complient
*[http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/KeyValueObserving/KeyValueObserving.html#//apple_ref/doc/uid/10000177i Apple on KVO] -KVO explains how to decode KVC objects.
*[http://www.monobjc.net/index.php?page=xib-file-format XIB File Format Definition as understod by MonoObjc]

3DKit

2012-11-23T03:13:26Z

Awiebe:

{{Unmaintained}}
{{Framework|
shortdescription = The GNU 3DKit provides an object oriented graphics API for writing 3D graphics applications using GNUstep or Cocoa. |
currentversion = 0.4 |
releasedate = |
license = [http://www.gnu.org/copyleft/lesser.html GNU Lesser General Public License] |
overview = The GNU 3DKit is officially part of the GNU project! It is an extension to GNUstep, which provides an object oriented application development framework and tool set for use on a wide variety of computer platforms. GNUstep is based on the original OpenStep specification provided by NeXT, Inc. (now Apple). Additionally the GNU 3DKit may also be used on Mac OS X using the Cocoa API. |
features = Instead of developing yet another OpenGL based scene graph API the new GNU 3DKit will become an object oriented graphics framework based on global illumination concepts which will use OpenGL only for preview capabilities. More information will be reveiled as soon as the time is ready for it.|
maintainer = [http://www.nice.ch/~phip/ Philippe C.D. Robert] |
relatedlinks = * [http://www.gnu.org/software/gnu3dkit/ GNU 3DKit]
* [http://savannah.gnu.org/projects/gnu3dkit/ Savannah] |
category = [[Category:Graphics_Frameworks]]
}}

TextEdit.app

2012-11-23T03:03:02Z

Awiebe:

{{Unmaintained}}
{{stub}}

{{Application|

shortdescription = TextEdit is a relatively basic text editor. It handles plain text or RTF, has a nice "Wrap to Page" mode, has search/replace functionality, and can display any file as text. |

currentversion = [http://www.gtlib.cc.gatech.edu/pub/debian/pool/main/t/textedit.app/textedit.app_4.0.orig.tar.gz 4.0] |

releasedate = Nov 29, 2004 |

license = freely copy, distribute, and reuse the code |

overview = < ... > |

features = < ... > |

maintainer = < ... > |

relatedlinks = http://www.nongnu.org/backbone/apps.html |

category = [[Category:Editor Applications]]
}}

NeXTGo.app

2012-11-23T02:52:27Z

Awiebe:

{{Unmaintained}}
{{stub}}

{{Application|
shortdescription = '''NeXTGo''' is the classic Go game |

currentversion = [http://savannah.nongnu.org/download/gap/NeXTGo-3.0.tar.gz 3.0] |

releasedate = Nov 5, 2005 |

license = GPL 2 |

overview = < ... > |

features = < ... > |

maintainer = Gregory John Casamento |

relatedlinks =
* [http://www.nongnu.org/gap/nextgo/index.html Official NeXTGo Page]
* [http://www.nongnu.org/gap/index.html GNUstep Application Project]|

category = [[Category:Games Applications]]
}}

Ladder.app

2012-11-23T02:51:53Z

Awiebe:

{{Unmaintained}}
{{stub}}
{{Application|
shortdescription=Ladder is a graphically pleasing implementation of Go. It uses [http://www.gnu.org/software/gnugo/gnugo.html GNU Go] as it's engine and you must have a recent version of GNU Go installed in order to run it.|

currentversion=[http://savannah.nongnu.org/download/gap/Ladder-1.0.tar.gz 1.0]|

releasedate=Unknown|

license=GPL 2.0|

overview=|

features=|

maintainer=
* [mailto:object@gmail.com Banlu Kemiyatorn]|

relatedlinks=http://www.nongnu.org/gap/ladder/index.html|

category=[[Category:Games_Applications]]
}}

Gridlock.app

2012-11-23T02:46:00Z

Awiebe:

{{Unmaintained}}
{{Application|
shortdescription = Gridlock is a collection of over 30 grid-based strategy games, including Ataxx, Reversi, Checkers, Gomoku, Connect Four, and more. |

currentversion = [http://www.dozingcatsoftware.com/Gridlock/Gridlock-gnustep-1.10.tar.gz 1.10] |

releasedate = Nov 26 2005 |

license = MIT |

overview = See the [http://www.dozingcatsoftware.com/Gridlock/readme.html Readme] for a detailed description. |

features = * 31 different games
* network play|

maintainer =
* [mailto:brian@dozingcatsoftware.com Brian Nenninger] |

relatedlinks =
* [http://www.dozingcatsoftware.com/Gridlock/readme.html Official Page] |

category = [[Category:Games Applications]]
}}

GRubik.app

2012-11-22T05:53:52Z

Awiebe:

{{Unmaintained}}
{{stub}}

{{Application|

shortdescription = GRubik is a virtual 3D Rubik's cube for you to solve. |

currentversion = [http://debian.uni-essen.de/misc/GNUstep/Apps/Recreational/GRubik.tgz 0.1] |

releasedate = July 2002 |

license = GPL2 |

overview = |

features =
* simple but functional and fast 3D
* a smart scramble that ensures you get a solvable cube
* interesting code that you might enjoy reading and which uses a variety of programming techniques.|

maintainer = Marko Riedel |

relatedlinks = |

category = [[Category:Games Applications]]
}}

GPuzzle.app

2012-11-22T05:44:09Z

Awiebe:

{{Unmaintained}}
{{stub}}
{{Application|
shortdescription = Simulates a jigsaw puzzle and illustrates the use of clipping paths. |

currentversion = [http://www.gnustep.it/marko/GPuzzle2/GPuzzle2.tgz 0.2] |

releasedate = July 16, 2006 (?) |

license = GPL2 |

overview =

'''NOTE: GPuzzle was renamed to Jigsaw, latest version can be found when looking for [[Jigsaw.app]]'''

You need a medium-sized TIFF file to play this game.
Left-click and drag to move a piece or cluster.
Ctrl-left-click and drag to connect knobs to slots.
Right-click to disassemble a cluster.
Ctrl-right-click to extract a piece from a cluster. |

features = |

maintainer =
* [mailto:markoriedelde@yahoo.de Marko Riedel] |

relatedlinks =
* [http://www.gnustep.it/marko/GPuzzle2/ Official Page] |

category = [[Category:Games Applications]]
}}

GFractal.app

2012-11-22T05:42:04Z

Awiebe:

{{Unmaintained}}
{{stub}}

{{Application|

shortdescription = Computes five different fractals including the Mandelbrot set. |

currentversion = [http://www.gnustep.it/marko/GFractal/GFractal.tgz 0.1]|

releasedate = May 2002 |

license = GPL2 |

overview = |

features = |

maintainer = Marko Riedel |

relatedlinks =
* [http://www.gnustep.it/marko/GFractal/index.html Official Page] |

category = [[Category:Science Applications]]
}}

Emacs.app

2012-11-22T04:45:55Z

Awiebe:

{{dated}}
{{Application|

shortdescription = [[Image:EmacsApp.png|thumb|Emacs.app browsing the manual]]
'''Emacs.app''' is a port of GNU Emacs, the ''"extensible, customizable, self-documenting, real-time display editor"'' to OS X and GNUstep. |

currentversion = [http://downloads.sourceforge.net/emacs-app/emacs-23.0.0_NS-9.0rc1.tar.bz2 9.0-rc1]|

releasedate = Dec 24, 2006 |

license = [[GPL]] 2 |

overview = Emacs for GNUstep and MacOS X is a version of
GNU Emacs CVS unicode-2 branch (currently planned to be released as
Emacs 23) which adds support for the GNUstep and MacOS X systems via
the OpenStep APIs (referred to as "Cocoa" under OS X).
<font color="#808080">– From the manual.</font> |

features = This port leaves most of the core functions of Emacs unchanged and is
fully-compatible with all Emacs Lisp packages, however it has a number
of step-ish features which do not have any equivalent in Emacs's X11
interface. The design aim was to make it look as similar as possible
to an X application to Emacs Lisp programs and to make it look like a
normal GNUstep or MacOS X application to users.
<font color="#808080">– From the manual.</font> |

maintainer = Adrian Robert |

relatedlinks = *[http://emacs-app.sourceforge.net Emacs.app website]
*[http://www.gnu.org/software/emacs GNU Emacs website]
*[http://en.wikipedia.org/wiki/Emacs Emacs wikipedia entry]|

category = [[Category:Editor Applications]]
}}

Template:Dated

2012-11-22T04:39:35Z

Awiebe:

<div style="text-align:center; border-style:solid;border-width:2px;">
This article is out of date, it requires the attention of an editor or its original author.
</div>

CodeEditor.app

2012-11-22T04:33:55Z

Awiebe:

{{Unmaintained}}
{{Application|

shortdescription = This application is unmantained and show problems with the current GNUstep. You can use [[Gemas.app]] instead.

CodeEditor is a text and code editor. |

currentversion = [http://savannah.nongnu.org/projects/codeeditor/ 0.4.4] |

releasedate = April 08, 2004 |

license = GPL2 |

overview = The goal of CodeEditor is to be a good non-rich text code editor. CodeEditorView offers a subclass of NSTextView and supports syntax highlight, mark delimiters, etc. It can be used in other projects. |

features =
* Faster than ever
* Tab View: Don't need to open so many terminals again.
* Toolbar: Use "Alt (left) - t" to open/close a simple toolbar on the fly.
* Find (Regular Express support) and replace.
* File Inspector.
* Change font attributes and preference instantly without restart.
* Periodically or manually Highlight keyword with difference attributes according to the language.
* Automatically or manually find delimiter pair.
* Automatically indentation according to the preference.
* Support scripting (need StepTalk). |

maintainer = Yen-Ju Chen |

relatedlinks =
* [http://www.nongnu.org/codeeditor CodeEditor website]|

category = [[Category:Development Applications]] [[Category:Editor Applications]]
}}

FreeTar.app

2012-11-22T04:32:56Z

Awiebe:

{{Unmaintained}}
{{stub}}

{{Application|

shortdescription = TAR archiver |

currentversion = 1.1.1 |

releasedate = September 2002 |

license = GPL |

overview = |

features = |

maintainer = Fabien Vallon |

relatedlinks =
* https://gna.org/projects/freetar/ |

category = [[Category:Archiver Applications]]
}}

Template:Unmaintained

2012-11-22T04:32:33Z

Awiebe:

<div style="border-style:solid;
border-width:2px;border-color:red; background-color:beige; margin:2px;">
<h1>Unmaintained</h1>
This project is either unmaintained, or its status is unknown.
Please do not remove this until the status of this project has been determined.
</div>

Template:Unmaintained

2012-11-22T04:31:41Z

Awiebe:

<div style="border-style:solid;
border-width:2px;border-color:red; background-color:beige">
<h1>Unmaintained</h1>
This project is either unmaintained, or its status is unknown.
Please do not remove this until the status of this project has been determined.
</div>

Template:Unmaintained

2012-11-22T04:29:59Z

Awiebe:

<div style="border-style:solid;
border-width:2px;border-color:red">
<h1>Unmaintained</h1>
This project is either unmaintained, or its status is unknown.
Please do not remove this until the status of this project has been determined.
</div>

NSControl

2012-11-04T00:34:53Z

Awiebe:

NSControl ithe the a very important framework in [[AppKit]], it is the superclass for items that recieve user input messages from the window(see [http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Responder Object ]
==XIBFields==
{{:NSControlXIB}}
==See also==
*[http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Apple on responder chains]
*[http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Apple on event handeling]

NSComboBox

2012-11-04T00:34:00Z

Awiebe:

Comperable to an [[NSPopUpButton]] a combobox also allows for textual input.
==XIB Fileds==
{{:NSControlXIB}}

NSComboBox

2012-11-04T00:15:06Z

Awiebe:

Comperable to an [[NSPopUpButton]] a combobox also allows for textual input.

Foundation

2012-11-04T00:02:34Z

Awiebe:

{{Dynamic List}}
The GNUstep base library (aka gnustep-base) contains a powerful set of non-graphical [[Objective-C]] classes that can readily be used in your programs. At present there are approximately 70 different classes available, including classes to handle [[NSString|strings]] and [[NSArray|arrays]], [[NSDate|dates]] and times, [[NSConnection|distributed objects]], [[NSURL|URLs]] and [[NSFileManager|file systems]] to name but a few.

You can find the automatically generated API documentation [http://www.gnustep.org/resources/documentation/Developer/Base/Reference/index.html here].

== Features ==

* [[Strings]]
* [[Collections]] (arrays, sets, and dictionaries) and [[NSEnumerator|enumerators]]
* [[File management]]
* [[Archiving|Object Archiving]]
* Advanced calendar [[Date|date]] manipulation
* [[Distributed Objects]] and inter-process communication
* [[URL]] handling
* [[Notifications]] (and distributed notifications)
* Easy [[Threading|multi-threading]]
* [[Timer]]s
* [[Lock]]s
* [[Exception handling]]

== Notes and Snippets ==

{| border="0" cellpadding="2"
! Class Reference !! Protocol Reference
|-
|

* [[NSAffineTransform]]
* [[NSArchiver]]
* [[NSArray]]
* [[NSAssertionHandler]]
* [[NSAttributedString]]
* [[NSAutoreleasePool]]
* [[NSBundle]]
* [[NSCachedURLResponse]]
* [[NSCalendarDate]]
* [[NSCharacterSet]]
* [[NSClassDescription]]
* [[NSCoder]]
* [[NSComparisonPredicate]]
* [[NSCompoundPredicate]]
* [[NSConditionLock]]
* [[NSConnection]]
* [[NSCountedSet]]
* [[NSData]]
* [[NSDate]]
* [[NSDateFormatter]]
* [[NSDecimalNumber]]
* [[NSDecimalNumberHandler]]
* [[NSDeserializer]]
* [[NSDictionary]]
* [[NSDirectoryEnumerator]]
* [[NSDistantObject]]
* [[NSDistributedLock]]
* [[NSDistributedNotificationCenter]]
* [[NSEnumerator]]
* [[NSError]]
* [[NSException]]
* [[NSExpression]]
* [[NSFileHandle]]
* [[NSFileManager]]
* [[NSFormatter]]
* [[NSHTTPCookie]]
* [[NSHTTPCookieStorage]]
* [[NSHTTPURLResponse]]
* [[NSHost]]
* [[NSIndexPath]]
* [[NSIndexSet]]
* [[NSInputStream]]
* [[NSInvocation]]
* [[NSKeyedArchiver]]
* [[NSKeyedUnarchiver]]
* [[NSLocale]]
* [[NSLock]]
* [[NSMessagePort]]
* [[NSMessagePortNameServer]]
* [[NSMethodSignature]]
* [[NSMutableArray]]
* [[NSMutableAttributedString]]
* [[NSMutableCharacterSet]]
* [[NSMutableData]]
* [[NSMutableDictionary]]
* [[NSMutableIndexSet]]
* [[NSMutableSet]]
* [[NSMutableString]]
* [[NSMutableURLRequest]]
* [[NSNetService]]
* [[NSNetServiceBrowser]]
* [[NSNotification]]
* [[NSNotificationCenter]]
* [[NSNotificationQueue]]
* [[NSNull]]
* [[NSNumber]]
* [[NSNumberFormatter]]
* [[NSObject]]
* [[NSOutputStream]]
* [[NSPipe]]
* [[NSPort]]
* [[NSPortCoder]]
* [[NSPortMessage]]
* [[NSPortNameServer]]
* [[NSPredicate]]
* [[NSProcessInfo]]
* [[NSPropertyListSerialization]]
* [[NSProtocolChecker]]
* [[NSProxy]]
* [[NSRecursiveLock]]
* [[NSRunLoop]]
* [[NSScanner]]
* [[NSSerializer]]
* [[NSSet]]
* [[NSSocketPort]]
* [[NSSocketPortNameServer]]
* [[NSSortDescriptor]]
* [[NSStream]]
* [[NSString]]
* [[NSTask]]
* [[NSThread]]
* [[NSTimeZone]]
* [[NSTimeZoneDetail]]
* [[NSTimer]]
* [[NSURL]]
* [[NSURLAuthenticationChallenge]]
* [[NSURLCache]]
* [[NSURLConnection]]
* [[NSURLCredential]]
* [[NSURLCredentialStorage]]
* [[NSURLDownload]]
* [[NSURLHandle]]
* [[NSURLProtectionSpace]]
* [[NSURLProtocol]]
* [[NSURLRequest]]
* [[NSURLResponse]]
* [[NSUnarchiver]]
* [[NSUndoManager]]
* [[NSUserDefaults]]
* [[NSValue]]
* [[NSValueTransformer]]
* [[NSXMLParser]]
* [[NSConstantString]]

| valign="top" |

* [[NSCoding]]
* [[NSCopying]]
* [[NSDecimalNumberBehaviors]]
* [[NSLocking]]
* [[NSMutableCopying]]
* [[NSObjCTypeSerializationCallBack]]
* [[NSObject]]
* [[NSURLAuthenticationChallengeSender]]
* [[NSURLHandleClient]]
* [[NSURLProtocolClient]]

|}

[[Category:Frameworks]]

Template:Dynamic List

2012-11-04T00:01:24Z

Awiebe:

<div style="border-style:solid;
border-width:3px; text-align:center;">
'''Dynamic List''' <br />
This is a list which is constantly changing and may never be considered complete.
</div>

Template:Dynamic List

2012-11-04T00:00:37Z

Awiebe:

<div style="border-style:solid;
border-width:3px; text-align:center;">
This is a list which is constantly changing and may never be considered complete.
</div>

NSControl

2012-11-03T23:55:47Z

Awiebe:

NSControl ithe the a very important framework in [[AppKit]], it is the superclass for items that recieve user input messages from the window(see [http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Responder Object ]

==See also==
*[http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Apple on responder chains]
*[http://developer.apple.com/library/ios/#documentation/general/conceptual/Devpedia-CocoaApp/Responder.html Apple on event handeling]

User:Awiebe

2012-09-24T22:52:23Z

Awiebe:

[http://stackoverflow.com/users/888715/awiebe http://stackexchange.com/users/flair/795711.png]

Currently a Computer Science student, long time macintosh user (as of 1995, so don't give me that mac fanboy crap)– but became interested in GNUStep after apple started making some questionable design decisions. Always been interested in having a system to (at least partially) call his own.

==Languages==
*English,French
*C
*C++
*Objc/C++
*C#(kind of)
*Java
*Javascript
*Bash
*Php
*SQL
*X/HTML
*XML
*VB(Only because I used some in a course)

==Comp Sci Interests==
*DSP
*BSP
*Graphics (3D & 2D)
*Audio Processing
*Video Processing
*Games
===Likes using, but has others write===
*Databases
*Compression
*Physics Engines
*Drawing Libraries
*Web rendering Agents

==Turn Ons==
*Clean, crisp code.
*Descriptive varible names.
==Turn Offs==
*Endianness Issues.
*Indentation and Bracketing issues
*People who think ( C ) int == int32_t
*People who take the above headers literally.
==How to Contact==

Put "GNUStep" in the subject line.
awiebe ;a-t; Burningthumb com

User Guides

2012-09-19T20:59:37Z

Awiebe: /* Installing GNUstep */

This page is intended as a collection of guides for users.

== Installing GNUstep ==

Installation can be easy or complex, depending on the system you use. If you encounter problems that aren't discussed here, please [[Get Help|ask for help on the mailing lists]].

* [http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto_toc.html GNUstep Installation] instructions or [[Installation | Simple Installation]] ([http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto.pdf PDF], [http://www.gnustep.org/resources/documentation/GNUstep-HOWTO-Italian.text Italian])
* Make sure you also check the [[Platform_compatibility|platform-specific]] instructions as well.
* Comprehensive [http://gnustep.made-it.com/BuildGuide/ build guide] for GNUstep on GNU/Linux.
* [http://www.gnustep.org/resources/documentation/User/Gui/KeyboardSetup.html User Keyboard Setup]
* [http://www.gnustep.org/resources/documentation/User/Gui/LanguageSetup.html Setup for East Asian Languages]
* User Defaults ([http://www.gnustep.org/resources/documentation/User/Gui/DefaultsSummary.html GUI]) ([http://www.gnustep.org/resources/documentation/Developer/Back/General/DefaultsSummary.html Back])
* [[GNUstep SVN Installation Guide]]

* [http://svn.gna.org/svn/etoile/trunk/Etoile/INSTALL.Ubuntu GNUstep and Étoilé dependency list]
* [[Building GNUstep with Clang]]

== Using GNUstep ==

* [[:Category:Applications|User Applications]]
* [http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem_toc.html Filesystem Layout] ([http://www.gnustep.org/resources/documentation/User/GNUstep/filesystem.pdf PDF])
* [[User_FAQ|GNUstep Users' FAQ]] ([http://www.gnustep.org/resources/documentation/User/GNUstep/userfaq.pdf PDF])
* [[Get Help|Mailing Lists, IRC and Newsgroups]]
* [[Cross Compiling]]
* [http://gnustep.files.wordpress.com/2010/11/objective-c_gnustep.pdf Manual de Objective-C y GNUstep (PDF en español)]
* [[Changing GNUStep Theme]]

== Other Info ==

* News and info:
** [http://freshmeat.net/browse/806/?topic_id=806 Freshmeat]
** [http://www.gnustep.wordpress.com/ GNUstep en español] - Noticias e información
* Projects:
** [[:Category:Desktop Environments|Desktop Environments]]
*** [http://www.nongnu.org/backbone/ Backbone] - GNUstep Desktop project
*** [http://www.etoile-project.org/ Étoilé] - GNUstep based user environment
*** [http://www.nongnu.org/gap/ GAP] - GNUstep Application Project
** Live CDs
*** [http://io.debian.net/~tar/gnustep/ GNUstep Live CD Project] - based on Debian
* Developer sites:
** [[For_Developers | Developers]] - List of developers
** [http://www.gnustep.it/ GNUstep.it] - Italian developer site
** [http://www.advogato.org/proj/GNUstep/ Advogato] - basic GNUstep project info and links to some developer diaries
** [http://www.collaboration-world.com/ Collaboration World] - home to GNUMail, Affiche and more
** [http://www.roard.com/docs/ GNUstep HelpCenter]
** [http://freshmeat.net/projects/gnustep-icons/ GNUstep Icons project]
* [[Success_Stories | GNUstep Success Stories]]

== Stores ==

* [http://www.cafepress.com/openlogic "Openlogic" GNUstep store] - A portion of these proceeds go to the FSF and GNUstep.
* The GNUstep project does not sponsor or benefit from these items:
** [http://www.cafepress.com/gnustep "GNUstep" store]
** [http://www.cafepress.com/opengnustep "OPENGNUstep" store]

Developer FAQ

2012-09-19T20:56:46Z

Awiebe:

[[Category:FAQ]]

Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.

==Getting started==
===[[Installation]]===
How to install GNUStep
===Installation [[Troubleshooting]]===
What to do when installation screws up.
=== [[Configuration]]===
What to do once GNUStep is installed.

== Compatibility ==

=== Is it easy to port OPENSTEP programs to GNUstep? ===

It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.

=== How about porting between Cocoa and GNUstep? ===

It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.

=== Tools for porting ===

While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.

* '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).
* '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.
* '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.
* '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.
* '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.

=== Can I transfer archived data from GNUstep to Cocoa? ===

Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.

The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.

=== Does distributed objects work between GNUstep and Cocoa? ===

See the answer to the previous question (on archive compatibility) for why this won't work either.

=== Is there an Interface Builder for GNUstep? ===

There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].

=== Can I use my original NIB files? ===
It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later.

Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.

=== Can one use the hybrid "Objective-C++" ? ===

Yes. As of release 4.1 the GNU C Compiler (GCC) supports "Objective-C++".

=== Is there a plan to support the Java/YellowBox Bindings? ===

Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects.

=== What if I compile GNUstep under OPENSTEP/MacOS X? ===

GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.

You can, however, use a GNUstep program with an X11 server running on MacOSX.

=== Is the Objective C API for GTK related? ===

No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.

The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks.

=== How about implementing parts of the Application Kit with GTK? ===

Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.

That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome.

== Compiling and Developing ==

=== How can I get started programming? ===
Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)

=== Why doesn't GDB support Objective-C? ===
As of GDB 6.0, gdb supports debugging of Objective-C code.

== How can I help with GNUstep? ==

The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.

Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep.

Here are the next steps:
* Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]
* Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.
* For a bigger challenge, finish off part of the [[Roadmap]]

=== How do I start writing applications? ===

You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.

Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.

=== Helping develop GNUstep ===

There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.

Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].

Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.

Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.

Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation.

Specific tasks are noted in the developers section on the GNUstep website.

=== Helping document GNUstep ===

All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.

Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.

More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!

Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.

GNUstep documentation should have copyright assigned to the Free Software Foundation.

=== How do I assign my contribution? ===

Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).

=== How do I update the task list? ===

The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).

One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.

Send any changes or additions to bug-gnustep@gnu.org.

A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.

If a class or method is

* in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.
* in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP
* in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X

There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.

=== How do I start writing tests? ===

You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.

To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.

=== How can I help with the GNUstep website? ===

'''Please consider contributing to this Wiki as opposed to the website.'''
Contact Adam Fedor fedor@gnu.org, the maintainer.

The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.

If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.

If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.

The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.

=== How can I take part with a GNUstep autobuilder for the testfarm? ===
* General Procedure
** Make sure your build system have a gcc compiler with objc support.
*** run "gcc -v" to see if obc is on the list of --enable-language option
** (Preferred Option): Get the source code via SVN:
*** svn co http://svn.gna.org/svn/gnustep/autotest gnustep-testfarm
** (Alternate Option): ...Or download the source code and test files
*** mkdir gnustep-testfarm && cd gnustep-testfarm
*** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2
*** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2
*** wget http://ftp.gnustep.org/pub/daily-snapshots/tests.current.tar.bz2
*** tar xjf startup.current.tar.bz2 ; tar xjf core.current.tar.bz2; tar xjf tests.current.tar.bz2
** cd startup/scripts
** ./test-gnustep

If you want to test this on a remote machine with X, make sure you don't forget the -X or -Y parameter
for ssh.

The results get posted to http://www.gnustep.org/developers/testfarm.html
The test script will automatically update using SVN if possible. See more documentation
in the test-gnustep script

== GNU Objective C Compiler and Runtime ==

=== What is the Objective C Runtime? ===

The [[Objective-C runtime]] Library provides C functions and data structures required to execute an Objective C program.

The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @""-style string objects).

It also has several differences over NeXT's implementation:

* GNU's runtime provides "selector-types" along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).

* Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.

Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.

=== Where can I get a gcc compiler with Objective C support? ===
*TBA.
=== How I can compile my own gcc compiler with objective-C support ? ===
* TBA.
=== How I check if my gcc compiler has good objective C environment ? ===
* TBA.

== GNUstep Base Library ==

=== What is the GNUstep Base Library? ===

The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops etc.

It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).

=== What is its current state of development? ===

GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.

=== What are the features of GNU Distributed Objects? ===

GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.

NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.
Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU "typed selector" mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like.

== GNUstep GUI Library ==

=== What is the GUI Library? ===

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 peripheral 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.

=== Explain the organization of the front- and back-ends ===

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. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X-Window. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. 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.

=== What is the current state of development of the front-end? ===
Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.

=== What is the current state of development of the back-ends? ===

There are several backends currently available:

* '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing.
* '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality.
* '''w32:''' This backend works on Windows and uses basic Windows drawing
* '''cairo:''' A backend based on the cairo graphics library. It is the standard backend (as long as the required libraries are installed).

== GNUstep DisplayGhostScript Server ==

=== What is the Display Ghostscript Server? ===

It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.

At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.

=== What is its current state of development? ===

GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.

Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.

=== What is the relationship between the Display Ghostscript Server and X-Window? ===

Display Ghostscript runs on top of X-Window.

Developer Guides

2012-09-19T20:53:44Z

Awiebe:

This page is intended as a collection of guides for developers.

== Introductory Articles on GNUstep Development ==

{{Stub}}

=== [[Installation]] ===
How to get started using GNUStep, because it is not immediately obvious, and we appologize for that.

=== [[GNUstep Suite|GNUstep Libraries and Tools]] ===

A general overview of GNUstep.

=== [http://www.gnustep.org/resources/documentation/Developer/Base/ProgrammingManual/manual_toc.html GNUstep Base Programming Manual] ===

The aim of this manual is to introduce you to the Objective-C language and the GNUstep development environment, in particular the Base library. The manual is organised to give you a tutorial introduction to the language and APIs, by using examples whenever possible, rather than providing a lengthy abstract description.

While Objective-C is not a difficult language to learn or use, some of the terms may be unfamiliar, especially to those that have not programmed using an object-oriented programming language before. Whenever possible, concepts will be explained in simple terms rather than in more advanced programming terms, and comparisons to other languages will be used to aid in illustration.

===[[GNUStep Macros]]===
See a define, but don't know what it's for, you are not alone. See this article for a reference to various macros, or otherwise unusual language extensions that you may see when reading the GNUStep Code.

=== [http://www.roard.com/docs/lmf2.article/en.html (GUI) Programming under GNUstep] ===

This tutorial will introduce you to the [[AppKit]] classes and how to use [[Gorm]] to create graphical interfaces.

=== [[Writing Makefiles]] ===

The Makefile package is a system of make commands that is designed to encapsulate all the complex details of building and installing various types of projects from libraries to applications to documentation. This frees the developer to focus on the details of their particular project. Only a fairly simple main makefile need to be written which specifies the type of project and files involved in the project.

=== [ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-examples-1.1.0.tar.gz Sample GNUstep Programs] ===

This isn't really an article but rather a collection of small "codified guides" for the pragmatic programmer who wants to explore GNUstep by looking at and messing around with example code. This is best done while reading about basic concepts of OpenStep or Cocoa with the API documentation ([[Foundation]], [[AppKit]]) open in the background.

== General ==

=== [[Writing portable code|Coding for Portability]] ===

Writing code that will compile and then run on different platforms can be surprisingly easy. This guide describes
some straight-forward steps to take to make your program easy to port to new platforms.

=== [[Property Lists|Using Property Lists]] ===

A regular issue that programmers face is storing structured configuration information, and reading it back. GNUstep has a standard mechanism that can be used for this task, amongst others: Property Lists.

=== [[Deployment on Windows]] ===

This article will tell you how to deploy GNUstep applications on Windows.

=== [[Adding a new Natural Language to GNUstep|Translating GNUstep]] ===

Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.

=== [[Contributing to GNUstep core libraries]] ===

Contributing to the core libraries is what everyone loves you for the most ... but it's quite a step to go from simple bug fixes/patches to major new code contributions. Follow the link above to see how.

When you read the information on [[Contributing to GNUstep core libraries]], please keep in mind that while it was written primarily form the point of view of contributing code to the gnustep-base library, the principles all apply to the gnustep-gui library (and other library code too). Also, a lot of the information is also relevant to contributions to application/tool code, not just library code.

== Graphical Applications ==

=== Simple Graphical Application Design ===
GNUstep includes several sophisticated development tools. GNUstep GUI interfaces are designed using [[Gorm]] (Graphical Object Relationship Modeler), an elegant application developed by Gregory Casamento. (See his [http://heronsperch.blogspot.com/ blog] for the latest news on GORM.) There are two proto-IDEs, [[ProjectCenter]] and [[ProjectManager]].

There are several introductory tutorials for using these development tools. The first [http://www.gnustep.it/pierre-yves/index.html tutorial] by Pierre-Yves Rivaille is a classic demonstrating the process used to create the ubiquitous currency converter application. A second [http://www.nongnu.org/gstutorial/ tutorial] by Yen-Ju Chen is somewhat more in-depth and extensive.

Nicolas Roard created a [http://gnustep.org/experience/DevelopmentDemonstration.html video] demonstrating the process of developing a simple calculator, and another [http://home.gna.org/pmanager/videos.html video] here by Sašo Kiselkov if you feel the need to create another currency converter.

=== [[Document based applications|Document-based Application Design]] ===

One of the most common use-patterns of applications on modern platforms is that of document-based applications --- applications which can have several active user-controlled contexts. Some familar examples might be a word processor where the user may have multiple document windows concurrently, or a web browser which allows a user to have a number of different browser windows open at the same time. This guide provides information and tips on how to code this style of application.

== Web Applications ==

Please have a look at [[Creating A Simple GSWeb Application]] to learn how to create a [[GNUstepWeb|GNUstep Web]] application.

== Other Information ==

=== Developer sites ===

* [http://www.roard.com/docs/ GNUstep HelpCenter]

[[Category:Development]]

NSMenu

2012-09-19T20:50:43Z

Awiebe:

GNUStep provides 3 menus. The system menu, the contextual menu, and the window menu. Their behaviours are not specifically defined, however the observed behaviour is.

== Under linux ==
*If a context menu is available when right clicking provide it, if not provide the application menu, otherwise provide the system menu.

==Under MacOS X==
*If a context menu is available provide it, applications menus appear in the menubar at the top of the screen according to the application in the foreground.

==Under Windows==
Untested.

Pasteboard

2012-09-19T20:44:57Z

Awiebe:

The GNUStep clipboard is a generic wrapper for information to be shared between applications.

==Notes==
The GNUStep clipboard is not bridged to the gnome clipboard, and may or may not be bridged to the windows clipboard. They are one and the same on MacOS as a native system call is used.

==Usage==
*[https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/PasteboardGuide106/Introduction/Introduction.html Apple on Copy and Paste]

*[https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/DragandDrop/DragandDrop.html Apple on Drag and Drop]

*[https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/SysServices/introduction.html Apple on "Services"]

AppKit

2012-09-19T20:20:31Z

Awiebe:

{{Dynamic List}}

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 [[Cocoa]] API (formerly [[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 [http://www.gnustep.org/resources/documentation/Developer/Gui/Reference/index.html 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|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|spell checking]]
* [[Document architecture|Document management]]
* [[Printing|Printing features]]: print operations, print panel and page layout
* Help manager
* [[Pasteboard|Pasteboard]] (a.k.a. clip board) services
* [[Spelling|Spell checker]]
* [[Workspace|Workspace]] bindings for applications
* [[Drag and drop]] operations
* [[Service|Services]] shared among applications
* [[XIB]] WYSIWIG GUI definition language – To be implemented

== Notes and Snippets ==

{| border="0" cellpadding="2"
! Class Reference !! Protocol Reference
|-
|

* [[NSActionCell]]
* [[NSAffineTransform]]
* [[NSAlert]]
* [[NSApplication]]
* [[NSBezierPath]]
* [[NSBitmapImageRep]]
* [[NSBox]]
* [[NSBrowser]]
* [[NSBrowserCell]]
* [[NSButton]]
* [[NSButtonCell]]
* [[NSCachedImageRep]]
* [[NSCell]]
* [[NSClipView]]
* [[NSColor]]
* [[NSColorList]]
* [[NSColorPanel]]
* [[NSColorPicker]]
* [[NSColorWell]]
* [[NSComboBox]]
* [[NSComboBoxCell]]
* [[NSControl]]
* [[NSCursor]]
* [[NSCustomImageRep]]
* [[NSDataLink]]
* [[NSDataLinkManager]]
* [[NSDataLinkPanel]]
* [[NSDocument]]
* [[NSDocumentController]]
* [[NSDrawer]]
* [[NSDrawerDelegate]]
* [[NSEPSImageRep]]
* [[NSEvent]]
* [[NSFileWrapper]]
* [[NSFont]]
* [[NSFontManager]]
* [[NSFontPanel]]
* [[NSForm]]
* [[NSFormCell]]
* [[NSGraphicsContext]]
* [[NSHelpManager]]
* [[NSHelpPanel]]
* [[NSImage]]
* [[NSImageCell]]
* [[NSImageRep]]
* [[NSImageView]]
* [[NSInputManager]]
* [[NSInputServer]]
* [[NSLayoutManager]]
* [[NSMatrix]]
* [[NSMenu]]
* [[NSMenuItem]]
* [[NSMenuItemCell]]
* [[NSMenuView]]
* [[NSMovie]]
* [[NSMovieView]]
* [[NSMutableParagraphStyle]]
* [[NSNib]]
* [[NSNibConnector]]
* [[NSNibControlConnector]]
* [[NSNibOutletConnector]]
* [[NSOpenGLContext]]
* [[NSOpenGLPixelFormat]]
* [[NSOpenGLView]]
* [[NSOpenPanel]]
* [[NSOutlineView]]
* [[NSPageLayout]]
* [[NSPanel]]
* [[NSParagraphStyle]]
* [[NSPasteboard]]
* [[NSPopUpButton]]
* [[NSPopUpButtonCell]]
* [[NSPrintInfo]]
* [[NSPrintOperation]]
* [[NSPrintPanel]]
* [[NSPrinter]]
* [[NSProgressIndicator]]
* [[NSResponder]]
* [[NSRulerMarker]]
* [[NSRulerView]]
* [[NSSavePanel]]
* [[NSScreen]]
* [[NSScrollView]]
* [[NSScroller]]
* [[NSSearchField]]
* [[NSSearchFieldCell]]
* [[NSSecureTextField]]
* [[NSSecureTextFieldCell]]
* [[NSSelection]]
* [[NSSlider]]
* [[NSSliderCell]]
* [[NSSound]]
* [[NSSpellChecker]]
* [[NSSpellServer]]
* [[NSSplitView]]
* [[NSStepper]]
* [[NSStepperCell]]
* [[NSTabView]]
* [[NSTabViewItem]]
* [[NSTableColumn]]
* [[NSTableHeaderCell]]
* [[NSTableHeaderView]]
* [[NSTableView]]
* [[NSText]]
* [[NSTextAttachment]]
* [[NSTextAttachmentCell]]
* [[NSTextContainer]]
* [[NSTextField]]
* [[NSTextFieldCell]]
* [[NSTextStorage]]
* [[NSTextTab]]
* [[NSTextView]]
* [[NSToolbar]]
* [[NSToolbarItem]]
* [[NSView]]
* [[NSWindow]]
* [[NSWindowController]]
* [[NSWorkspace]]

| valign="top" |

* [[NSChangeSpelling]]
* [[NSColorPickingCustom]]
* [[NSColorPickingDefault]]
* [[NSDraggingInfo]]
* [[NSIgnoreMisspelledWords]]
* [[NSInputServerMouseTracker]]
* [[NSInputServiceProvider]]
* [[NSMenuItem]]
* [[NSMenuValidation]]
* [[NSMenuView]]
* [[NSTextAttachmentCell]]
* [[NSTextInput]]
* [[NSUserInterfaceValidations]]
* [[NSValidatedUserInterfaceItem]]

|}

[[Category:Frameworks]]

Template:Dynamic List

2012-09-19T20:20:23Z

Awiebe:

This is a list which is constantly changing and may never be considered complete.

NSClipView

2012-09-19T20:17:58Z

Awiebe:

NSClipView is an abstract superclass for objects that draw subviews that overflow a rect masking them. For example an [[NSScrollView]] uses an NSClipView to obsucre the portion of the scrollview that is not currently rendered.

URL

2012-07-21T20:36:45Z

Awiebe:

All APIs that used "paths"(file) are now moving towards using URLs for obvious reasons:
*No confusion between windows and *NIX paths
*URLs can declare a protocol for transport when accessing remote paths.
*URLs provide a standard, unambiguous reference to any resource.

==URL Related Classes==
* [[NSURL]]
* [[NSFileHandle]]
* [[NSOpenPanel]]
* [[NSSavePanel]]

Reference counting

2012-07-21T20:21:16Z

Awiebe:

Reference counting is used to automatically deallocate objects when they are no longer needed.

==Using reference counting==
By convention when using an autorelased object you must "retain" before using it, and release it when you are done with it. For consistency you may "retain the object you want at the beginign of your method, and release it at the end, though in a tight loop you may wish to only retain once.

===Example===
<source lang="objc">

-(void)myMethod:(NSObject*)myObject
{

[myObject retain]
//my code
[myObject release]

}
</source>
===Tight Loop===
<code>

-(void)myMethod:(NSObject*)myObject
{

[myObject retain]
for(int64_t i = 0; i<LONG_LONG_MAX; i++)

{

[self mySubMethod:myObject]

}

[myObject release]

}

-(void)mySubMethod:(NSObject*)myObject
{

//Remove retain/relase overhead

//[myObject* retain]

//my code

//[myObject* release]

}
</code>

==See also==
[http://en.wikipedia.org/wiki/Reference_counting Wikipedia on reference counting]

NSAutoreleasePool

2012-07-21T20:13:49Z

Awiebe:

The autorelease pool is responsible for freeing objects with a [[reference counting|reference count]] of zero.

Reference counting

2012-07-21T20:13:35Z

Awiebe:

Reference counting is used to automatically deallocate objects when they are no longer needed.

==Using reference counting==
By convention when using an autorelased object you must "retain" before using it, and release it when you are done with it. For consistency you may "retain the object you want at the beginign of your method, and release it at the end, though in a tight loop you may wish to only retain once.

===Example===
<code>

-(void)myMethod:(NSObject*)myObject
{

[myObject retain]
//my code
[myObject release]

}
</code>
===Tight Loop===
<code>

-(void)myMethod:(NSObject*)myObject
{

[myObject retain]
for(int64_t i = 0; i<LONG_LONG_MAX; i++)

{

[self mySubMethod:myObject]

}

[myObject release]

}

-(void)mySubMethod:(NSObject*)myObject
{

//Remove retain/relase overhead

//[myObject* retain]

//my code

//[myObject* release]

}
</code>

==See also==
[http://en.wikipedia.org/wiki/Reference_counting Wikipedia on reference counting]

NSNumber

2012-07-21T19:54:44Z

Awiebe:

A container fromat for numeric interchange.

NSNumber is used in GNUStep frameworks to provide an abstraction for numbers until they must be used to call native APIs, at the expense of a minor performance hit. Operations requiring values to be computed in a tight loop should consider using primitive datatypes to avoid overhead.

NSBitmapImageRep

2012-07-21T19:49:46Z

Awiebe:

An internal representation of an [[NSImage]] that is stored as a bitmap.

NSGraphicsContext

2012-07-21T19:37:05Z

Awiebe:

A graphics context is and ADT that allows for a the [[Appkit]] drawing protocols to be used for drawing to a view(the most common), or an image, file, printer, ect. In essence it provides a canvas on which to draw.

NSEvent

2012-07-21T19:32:47Z

Awiebe:

A container for user input information. When an event such as a key or mousedown occurs, an event will be dispatched by the NSInputServer.
==See Also==
[https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/nsevent_Class/Reference/Reference.html Apple On NSEvent]

Plist

2012-07-21T07:44:10Z

Awiebe:

Plists allow certain types to be archived and later restored, they are usually used for storing prefernces.

==Special Plists===
* [[Info Plist]] - Contains bundle information for MacOS Applications.

Archiving

2012-07-21T07:41:10Z

Awiebe:

== Allowing objects to be archived ==

To permit an object to be archived (also known as serialisation) its class needs to implement the NSCoding protocol. This protocol exposes two methods: -encoderWithCoder and -initWithCoder:. By implementing these methods, your object can be serialised/deserialised (for [[plist]]s or RPC) as well as sent over GNUstep's Distributed objects mechanism.

See the reference manual for more details.

NSSound

2012-07-21T02:11:55Z

Awiebe:

A representation of an audio object, may be initialized with serveral differenet kinds of files, as well as with serveral system defined audio files.

===System sounds===
System sounds are located under
$GNUSTEP_ROOT/System/Lbrary/Sounds/name.wav

*Basso
*Blow
*Frog
*Glass
*Hero
*Ping
*Pop
*Sosumi
*Submarine
*Tink

AppKit

2012-07-21T01:50:30Z

Awiebe: /* Features */

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 [[Cocoa]] API (formerly [[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 [http://www.gnustep.org/resources/documentation/Developer/Gui/Reference/index.html 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|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|spell checking]]
* [[Document architecture|Document management]]
* [[Printing|Printing features]]: print operations, print panel and page layout
* Help manager
* [[Pasteboard|Pasteboard]] (a.k.a. clip board) services
* [[Spelling|Spell checker]]
* [[Workspace|Workspace]] bindings for applications
* [[Drag and drop]] operations
* [[Service|Services]] shared among applications
* [[XIB]] WYSIWIG GUI definition language – To be implemented

== Notes and Snippets ==

{| border="0" cellpadding="2"
! Class Reference !! Protocol Reference
|-
|

* [[NSActionCell]]
* [[NSAffineTransform]]
* [[NSAlert]]
* [[NSApplication]]
* [[NSBezierPath]]
* [[NSBitmapImageRep]]
* [[NSBox]]
* [[NSBrowser]]
* [[NSBrowserCell]]
* [[NSButton]]
* [[NSButtonCell]]
* [[NSCachedImageRep]]
* [[NSCell]]
* [[NSClipView]]
* [[NSColor]]
* [[NSColorList]]
* [[NSColorPanel]]
* [[NSColorPicker]]
* [[NSColorWell]]
* [[NSComboBox]]
* [[NSComboBoxCell]]
* [[NSControl]]
* [[NSCursor]]
* [[NSCustomImageRep]]
* [[NSDataLink]]
* [[NSDataLinkManager]]
* [[NSDataLinkPanel]]
* [[NSDocument]]
* [[NSDocumentController]]
* [[NSDrawer]]
* [[NSDrawerDelegate]]
* [[NSEPSImageRep]]
* [[NSEvent]]
* [[NSFileWrapper]]
* [[NSFont]]
* [[NSFontManager]]
* [[NSFontPanel]]
* [[NSForm]]
* [[NSFormCell]]
* [[NSGraphicsContext]]
* [[NSHelpManager]]
* [[NSHelpPanel]]
* [[NSImage]]
* [[NSImageCell]]
* [[NSImageRep]]
* [[NSImageView]]
* [[NSInputManager]]
* [[NSInputServer]]
* [[NSLayoutManager]]
* [[NSMatrix]]
* [[NSMenu]]
* [[NSMenuItem]]
* [[NSMenuItemCell]]
* [[NSMenuView]]
* [[NSMovie]]
* [[NSMovieView]]
* [[NSMutableParagraphStyle]]
* [[NSNib]]
* [[NSNibConnector]]
* [[NSNibControlConnector]]
* [[NSNibOutletConnector]]
* [[NSOpenGLContext]]
* [[NSOpenGLPixelFormat]]
* [[NSOpenGLView]]
* [[NSOpenPanel]]
* [[NSOutlineView]]
* [[NSPageLayout]]
* [[NSPanel]]
* [[NSParagraphStyle]]
* [[NSPasteboard]]
* [[NSPopUpButton]]
* [[NSPopUpButtonCell]]
* [[NSPrintInfo]]
* [[NSPrintOperation]]
* [[NSPrintPanel]]
* [[NSPrinter]]
* [[NSProgressIndicator]]
* [[NSResponder]]
* [[NSRulerMarker]]
* [[NSRulerView]]
* [[NSSavePanel]]
* [[NSScreen]]
* [[NSScrollView]]
* [[NSScroller]]
* [[NSSearchField]]
* [[NSSearchFieldCell]]
* [[NSSecureTextField]]
* [[NSSecureTextFieldCell]]
* [[NSSelection]]
* [[NSSlider]]
* [[NSSliderCell]]
* [[NSSound]]
* [[NSSpellChecker]]
* [[NSSpellServer]]
* [[NSSplitView]]
* [[NSStepper]]
* [[NSStepperCell]]
* [[NSTabView]]
* [[NSTabViewItem]]
* [[NSTableColumn]]
* [[NSTableHeaderCell]]
* [[NSTableHeaderView]]
* [[NSTableView]]
* [[NSText]]
* [[NSTextAttachment]]
* [[NSTextAttachmentCell]]
* [[NSTextContainer]]
* [[NSTextField]]
* [[NSTextFieldCell]]
* [[NSTextStorage]]
* [[NSTextTab]]
* [[NSTextView]]
* [[NSToolbar]]
* [[NSToolbarItem]]
* [[NSView]]
* [[NSWindow]]
* [[NSWindowController]]
* [[NSWorkspace]]

| valign="top" |

* [[NSChangeSpelling]]
* [[NSColorPickingCustom]]
* [[NSColorPickingDefault]]
* [[NSDraggingInfo]]
* [[NSIgnoreMisspelledWords]]
* [[NSInputServerMouseTracker]]
* [[NSInputServiceProvider]]
* [[NSMenuItem]]
* [[NSMenuValidation]]
* [[NSMenuView]]
* [[NSTextAttachmentCell]]
* [[NSTextInput]]
* [[NSUserInterfaceValidations]]
* [[NSValidatedUserInterfaceItem]]

|}

[[Category:Frameworks]]

Color

2012-07-21T01:49:50Z

Awiebe:

[https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSColorSpace_Class/Reference/Reference.html Apple on NSColorSpace]]

Foundation

2012-07-21T01:45:23Z

Awiebe: /* Notes and Snippets */

The GNUstep base library (aka gnustep-base) contains a powerful set of non-graphical [[Objective-C]] classes that can readily be used in your programs. At present there are approximately 70 different classes available, including classes to handle [[NSString|strings]] and [[NSArray|arrays]], [[NSDate|dates]] and times, [[NSConnection|distributed objects]], [[NSURL|URLs]] and [[NSFileManager|file systems]] to name but a few.

You can find the automatically generated API documentation [http://www.gnustep.org/resources/documentation/Developer/Base/Reference/index.html here].

== Features ==

* [[Strings]]
* [[Collections]] (arrays, sets, and dictionaries) and [[NSEnumerator|enumerators]]
* [[File management]]
* [[Archiving|Object Archiving]]
* Advanced calendar [[Date|date]] manipulation
* [[Distributed Objects]] and inter-process communication
* [[URL]] handling
* [[Notifications]] (and distributed notifications)
* Easy [[Threading|multi-threading]]
* [[Timer]]s
* [[Lock]]s
* [[Exception handling]]

== Notes and Snippets ==

{| border="0" cellpadding="2"
! Class Reference !! Protocol Reference
|-
|

* [[NSAffineTransform]]
* [[NSArchiver]]
* [[NSArray]]
* [[NSAssertionHandler]]
* [[NSAttributedString]]
* [[NSAutoreleasePool]]
* [[NSBundle]]
* [[NSCachedURLResponse]]
* [[NSCalendarDate]]
* [[NSCharacterSet]]
* [[NSClassDescription]]
* [[NSCoder]]
* [[NSComparisonPredicate]]
* [[NSCompoundPredicate]]
* [[NSConditionLock]]
* [[NSConnection]]
* [[NSCountedSet]]
* [[NSData]]
* [[NSDate]]
* [[NSDateFormatter]]
* [[NSDecimalNumber]]
* [[NSDecimalNumberHandler]]
* [[NSDeserializer]]
* [[NSDictionary]]
* [[NSDirectoryEnumerator]]
* [[NSDistantObject]]
* [[NSDistributedLock]]
* [[NSDistributedNotificationCenter]]
* [[NSEnumerator]]
* [[NSError]]
* [[NSException]]
* [[NSExpression]]
* [[NSFileHandle]]
* [[NSFileManager]]
* [[NSFormatter]]
* [[NSHTTPCookie]]
* [[NSHTTPCookieStorage]]
* [[NSHTTPURLResponse]]
* [[NSHost]]
* [[NSIndexPath]]
* [[NSIndexSet]]
* [[NSInputStream]]
* [[NSInvocation]]
* [[NSKeyedArchiver]]
* [[NSKeyedUnarchiver]]
* [[NSLocale]]
* [[NSLock]]
* [[NSMessagePort]]
* [[NSMessagePortNameServer]]
* [[NSMethodSignature]]
* [[NSMutableArray]]
* [[NSMutableAttributedString]]
* [[NSMutableCharacterSet]]
* [[NSMutableData]]
* [[NSMutableDictionary]]
* [[NSMutableIndexSet]]
* [[NSMutableSet]]
* [[NSMutableString]]
* [[NSMutableURLRequest]]
* [[NSNetService]]
* [[NSNetServiceBrowser]]
* [[NSNotification]]
* [[NSNotificationCenter]]
* [[NSNotificationQueue]]
* [[NSNull]]
* [[NSNumber]]
* [[NSNumberFormatter]]
* [[NSObject]]
* [[NSOutputStream]]
* [[NSPipe]]
* [[NSPort]]
* [[NSPortCoder]]
* [[NSPortMessage]]
* [[NSPortNameServer]]
* [[NSPredicate]]
* [[NSProcessInfo]]
* [[NSPropertyListSerialization]]
* [[NSProtocolChecker]]
* [[NSProxy]]
* [[NSRecursiveLock]]
* [[NSRunLoop]]
* [[NSScanner]]
* [[NSSerializer]]
* [[NSSet]]
* [[NSSocketPort]]
* [[NSSocketPortNameServer]]
* [[NSSortDescriptor]]
* [[NSStream]]
* [[NSString]]
* [[NSTask]]
* [[NSThread]]
* [[NSTimeZone]]
* [[NSTimeZoneDetail]]
* [[NSTimer]]
* [[NSURL]]
* [[NSURLAuthenticationChallenge]]
* [[NSURLCache]]
* [[NSURLConnection]]
* [[NSURLCredential]]
* [[NSURLCredentialStorage]]
* [[NSURLDownload]]
* [[NSURLHandle]]
* [[NSURLProtectionSpace]]
* [[NSURLProtocol]]
* [[NSURLRequest]]
* [[NSURLResponse]]
* [[NSUnarchiver]]
* [[NSUndoManager]]
* [[NSUserDefaults]]
* [[NSValue]]
* [[NSValueTransformer]]
* [[NSXMLParser]]
* [[NSConstantString]]

| valign="top" |

* [[NSCoding]]
* [[NSCopying]]
* [[NSDecimalNumberBehaviors]]
* [[NSLocking]]
* [[NSMutableCopying]]
* [[NSObjCTypeSerializationCallBack]]
* [[NSObject]]
* [[NSURLAuthenticationChallengeSender]]
* [[NSURLHandleClient]]
* [[NSURLProtocolClient]]

|}

[[Category:Frameworks]]

NSSlider

2012-07-21T01:42:51Z

Awiebe:

The NSSlider performs a linear interpolation between '''min''' and '''max''' based on its position from left to right, where right is '''max'''.