|Revision as of 10:26, 2 November 2009
Pingi (Talk | contribs)
[http://www.roard.com/docs/lmf2.article/en.html (GUI) Programming under GNUstep]
← Previous diff
|Revision as of 12:37, 7 February 2012
Rfm (Talk | contribs)
Next diff →
|Line 45:||Line 45:|
|Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.||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. Here's how.|
|== Graphical Applications ==||== Graphical Applications ==|
Revision as of 12:37, 7 February 2012
This page is intended as a collection of guides for developers.
Introductory Articles on GNUstep Development
| This article or section is a stub (i.e., in need of additional material).|
You can help us by
A general overview of GNUstep.
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.
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.
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.
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.
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.
This article will tell you how to deploy GNUstep applications on Windows.
Translation of GNUstep applications involves a number of steps, including translation of GNUstep Base and GNUstep GUI.
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. Here's how.
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 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 tutorial by Pierre-Yves Rivaille is a classic demonstrating the process used to create the ubiquitous currency converter application. A second tutorial by Yen-Ju Chen is somewhat more in-depth and extensive.
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.