https://mediawiki.gnustep.org/api.php?action=feedcontributions&feedformat=atom&user=MguesdonGNUstepWiki - User contributions [en]2026-04-21T05:03:45ZUser contributionsMediaWiki 1.35.7https://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=6435User:Mguesdon2012-07-31T11:23:39Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=6434User:Mguesdon2012-07-31T11:10:05Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2<br />
<br />
<source lang="php"><br />
<?php<br />
$v = "string"; // sample initialization<br />
?><br />
html text<br />
<?<br />
echo $v; // end of php code<br />
?><br />
</source></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=6433User:Mguesdon2012-07-31T11:03:26Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2<br />
<br />
<syntaxhighlight lang="php"><br />
<?php<br />
$v = "string"; // sample initialization<br />
?><br />
html text<br />
<?<br />
echo $v; // end of php code<br />
?><br />
</syntaxhighlight></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=6432User:Mguesdon2012-07-31T11:00:30Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2<br />
<br />
<syntaxhighlight><br />
[a b:c];<br />
</syntaxhighlight></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=6431User:Mguesdon2012-07-31T10:54:11Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2<br />
<br />
<syntaxhighlight lang="php"><br />
<?php<br />
$v = "string"; // sample initialization<br />
?><br />
html text<br />
<?<br />
echo $v; // end of php code<br />
?><br />
</syntaxhighlight></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=5630GNUstep in production2009-04-30T13:31:37Z<p>Mguesdon: /* Companies which use and/or support GNUstep */</p>
<hr />
<div>''Note: Please leave a short note about how is the company related to GNUstep. Please sort the list alphabetically.''<br />
<br />
== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.brainstorm.co.uk/ Brainstorm Mobile Solutions Ltd] has one the most advanced SMS/MMS mobile marketing platforms on the market, and it's all running on GNUstep.<br />
* [http://www.orange-concept.com/ Orange Concept] is working mainly on [http://www.gnustepweb.org GNUstepWeb] and [[GDL|GDL2]] for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
* [http://www.goldelico.com/ Golden Delicious Computers] is working on [http://www.quantum-step.com QuantumSTEP] for Embedded Devices<br />
<br />
== Companies which use and/or support GNUstep ==<br />
<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
* [http://www.intars.at/ Ayers Application Design & Development]<br />
* [http://www.ivt.baug.ethz.ch/oev/RailMLEditor_d.html Institut für Verkehrsplanung und Transportsysteme]<br />
* Microcom ([http://www.cyberpokershop.com CyberPokerShop], [http://www.cyberdvdfilms.com CyberDVDFilms]) <br>uses [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and [[GDL2]] to run its shops since may 2003.<br />
* [http://www.lmet.fr Le Monde en Tique] the famous french Computer Science library uses [http://www.eCommStep.com eCommStep] for it's B2C and B2B e-Commerce web site.<br />
* Orillion<br />
* [http://www.seat-1.com seat-1 Software GmbH ], business software for small to medium-sized production, trading and service companies. The software product IntarS is powered by [[GNUstepWeb]] on GNU based operating systems.<br />
<br />
* [[Smartsoft]] develops highly customized business applications for MacOSX and Solaris.<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=File:Theming.odp&diff=5527File:Theming.odp2009-02-17T17:26:39Z<p>Mguesdon: </p>
<hr />
<div></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Success_Stories&diff=5408Success Stories2009-01-08T18:54:44Z<p>Mguesdon: added link to "GNUstep in production"</p>
<hr />
<div>= Cenon =<br />
[http://www.cenon.info/ Cenon] is a vector graphics tool with a wide range of applications. It is built upon a modular graphical core, and offers a variety of applications beyond desktop publishing. Cenon can convert, import, and export many graphics formats. The modular concept allows the extension of Cenon for specialized applications.<br />
<br />
= RailML Editor =<br />
The [http://www.ivt.baug.ethz.ch/oev/railmleditor_d.html RailML Editor] was ported to GNUstep from OPENSTEP. The RailML.org Initiative attempts to facilitate communication between railway applications. RailML Editor is one of the many applications that follow the railML standard.<br />
<br />
= NetMage =<br />
NetMage is a client-server system developed completely in GNUstep and<br />
Objective-C and running on GNU/Linux and other flavors of *nix. It is<br />
used internally by the companies NETLAB and GTS Nextra for collective<br />
monitoring and administering of long-range synchronous radio<br />
telecommunications links.<br />
<br />
Some screenshots:<br />
<br />
1. NetMage with the login screen visible and a list of available<br />
synchronous networks to connect to:<br />
http://netdev.netlab.sk/netmage1.png<br />
<br />
2. NetMage showing a network of radio links in a synchronous network:<br />
http://netdev.netlab.sk/netmage2.png<br />
<br />
3. NetMage showing the settings of a modular link multiplexer along with<br />
a list of available interface cards:<br />
http://netdev.netlab.sk/netmage3.png<br />
<br />
Please consider the above screenshots licensed under the FDL - I provide<br />
them in good faith for the endorsement of GNUstep, not for any profit<br />
(we don't sell the above mentioned software anyways...).<br />
<br />
= See also =<br />
[[GNUstep in production]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=5407GNUstep in production2009-01-08T18:52:10Z<p>Mguesdon: </p>
<hr />
<div>''Note: Please leave a short note about how is the company related to GNUstep. Please sort the list alphabetically.''<br />
<br />
== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.brainstorm.co.uk/ Brainstorm Mobile Solutions Ltd] has one the most advanced SMS/MMS mobile marketing platforms on the market, and it's all running on GNUstep.<br />
* [http://www.orange-concept.com/ Orange Concept] is working mainly on [http://www.gnustepweb.org GNUstepWeb] and [[GDL|GDL2]] for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
* [http://www.goldelico.com/ Golden Delicious Computers] is working on [http://www.quantum-step.com QuantumSTEP] for Embedded Devices<br />
<br />
== Companies which use and/or support GNUstep ==<br />
<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
* [http://www.intars.at/ Ayers Application Design & Development]<br />
* [http://www.ivt.baug.ethz.ch/oev/RailMLEditor_d.html Institut für Verkehrsplanung und Transportsysteme]<br />
* Microcom ([http://www.cyberpokershop.com CyberPokerShop], [http://www.cyberdvdfilms.com CyberDVDFilms]) <br>uses [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and [[GDL2]] to run its shops since may 2003.<br />
* Orillion<br />
* [http://www.seat-1.com seat-1 Software GmbH ], business software for small to medium-sized production, trading and service companies. The software product IntarS is powered by [[GNUstepWeb]] on GNU based operating systems.<br />
<br />
* [[Smartsoft]] develops highly customized business applications for MacOSX and Solaris.<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepWeb&diff=4929GNUstepWeb2007-11-23T19:16:15Z<p>Mguesdon: </p>
<hr />
<div>{{Framework|<br />
shortdescription = GNUstepWeb is a web application library |<br />
<br />
currentversion = [http://gnustep.org] |<br />
<br />
releasedate = use SVN |<br />
<br />
license = LGPL2|<br />
<br />
overview = GNUstepWeb is a development framework for web applications written in Objective-C which is designed to be source-code compatible with [http://www.apple.com/webobjects/ WebObjects] 4.5 - a product originally developed by NeXT Inc, whose newer versions have been released by Apple and are Java-based. |<br />
<br />
features = This library is a component of the [[GNUstep]] project in the dev-libs section and is available in the standard ways - such as the [ftp://ftp.gnustep.org/pub/daily-snapshots/dev-libs.current.tar.bz2 GNUstep ftp site].<br />
<br />
David Wetzel recommends using the current version that can be obtained by executing the following [[SVN]] check out in an empty directory<br />
svn co http://svn.gna.org/svn/gnustep/libs/gsweb/trunk <br />
<br />
|<br />
<br />
maintainer = David Wetzel |<br />
<br />
Installation tips =<br />
* Install GNUstep core and gdl2 components<br />
* Install Apache 2.x<br />
* Download svn current version (see above)<br />
* Install Apache2 / GNUstepWeb adaptor module (see GSWAdaptors/Apache/INSTAL in GNUstepWeb Tree)<br />
* Setup Adaptor configuration (see GSWAdaptors/Apache/INSTAL)<br />
* Build and install GNUstepWeb (see INSTALL) in GNUstepWeb Tree<br />
* Build and install Examples/hello (see Examples/hello/INSTALL)<br />
* Run hello<br />
* Point your browser to: http://localhost/GSWeb/hello.gswa.<br />
<br />
|<br />
<br />
relatedlinks = <br />
* Apple has [http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/webobjects.html legacy WebObjects 4.5 documentation] available. Please note that the official site [http://www.gnustepweb.org/ gnustepweb.org] is somewhat out of date. <br />
* David Wetzel runs a low-volume mailing list called [http://lists.turbocat.net/mailman/listinfo.cgi/gswhackers gswhackers].<br />
* [[Creating A Simple GSWeb Application]] is very easy. |<br />
<br />
category = [[Category:GNUstepWeb]] [[Category:Networking_Frameworks]]<br />
}}</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepWeb&diff=4928GNUstepWeb2007-11-23T19:15:22Z<p>Mguesdon: </p>
<hr />
<div>{{Framework|<br />
shortdescription = GNUstepWeb is a web application library |<br />
<br />
currentversion = [http://gnustep.org] |<br />
<br />
releasedate = use SVN |<br />
<br />
license = LGPL2|<br />
<br />
overview = GNUstepWeb is a development framework for web applications written in Objective-C which is designed to be source-code compatible with [http://www.apple.com/webobjects/ WebObjects] 4.5 - a product originally developed by NeXT Inc, whose newer versions have been released by Apple and are Java-based. |<br />
<br />
features = This library is a component of the [[GNUstep]] project in the dev-libs section and is available in the standard ways - such as the [ftp://ftp.gnustep.org/pub/daily-snapshots/dev-libs.current.tar.bz2 GNUstep ftp site].<br />
<br />
David Wetzel recommends using the current version that can be obtained by executing the following [[SVN]] check out in an empty directory<br />
svn co http://svn.gna.org/svn/gnustep/libs/gsweb/trunk <br />
<br />
|<br />
<br />
maintainer = David Wetzel |<br />
<br />
Installation tips =<br />
* Install GNUstep core and gdl2 components<br />
* Install Apache 2.x<br />
* Download svn current version (see above)<br />
* Install Apache 2 <-> GNUstepWeb adaptor module (see GSWAdaptors/Apache/INSTAL in GNUstepWeb Tree)<br />
* Setup Adaptor configuration (see GSWAdaptors/Apache/INSTAL)<br />
* Build and install GNUstepWeb (see INSTALL) in GNUstepWeb Tree<br />
* Build and install Examples/hello (see Examples/hello/INSTALL)<br />
* Run hello<br />
* Point your browser to: http://localhost/GSWeb/hello.gswa.<br />
<br />
|<br />
<br />
relatedlinks = <br />
* Apple has [http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/webobjects.html legacy WebObjects 4.5 documentation] available. Please note that the official site [http://www.gnustepweb.org/ gnustepweb.org] is somewhat out of date. <br />
* David Wetzel runs a low-volume mailing list called [http://lists.turbocat.net/mailman/listinfo.cgi/gswhackers gswhackers].<br />
* [[Creating A Simple GSWeb Application]] is very easy. |<br />
<br />
category = [[Category:GNUstepWeb]] [[Category:Networking_Frameworks]]<br />
}}</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Stefanbidi&diff=3613User:Stefanbidi2006-09-27T08:45:33Z<p>Mguesdon: </p>
<hr />
<div>== Custom Skins ==<br />
In order to test some skins, and maybe learn some CSS in the process, the administrator needs to enable User Style codes. According to wikimedia.org the default is to ignor User Style code, in order to enable it, the following lines need to be added to '''LocalSettings.php'''<br />
$wgAllowUserJs = true;<br />
$wgAllowUserCss = true;<br />
It would be nice if we had this option! [[User:Stefanbidi|Stefanbidi]]<br />
<br />
Done<br />
[[User:Mguesdon|Mguesdon]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=1114GNUstep in production2005-08-29T15:05:59Z<p>Mguesdon: /* Companies which use and/or support GNUstep */</p>
<hr />
<div>''Note: Please leave a short note about how is the company related to GNUstep.''<br />
<br />
== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept] is working mainly on [http://www.gnustepweb.org GNUstepWeb] and [[GDL|GDL2]] for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and/or support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom]<br>uses [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and [[GDL2]] to run its shop since may 2003.<br />
* [http://www.seat-1.com seat-1 Software GmbH ], business software for small to medium-sized production, trading and service companies. The software product IntarS is powered by [[GNUstepWeb]] on GNU based operating systems.<br />
* Orillion<br />
* [http://www.theinternetco.net/ The Internet Company]<br />
* [http://www.ivt.baug.ethz.ch/oev/RailMLEditor_d.html Institut für Verkehrsplanung und Transportsysteme]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GDL2&diff=2056GDL22005-08-29T14:47:53Z<p>Mguesdon: </p>
<hr />
<div>#REDIRECT [[GDL]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Glossary&diff=945Glossary2005-08-29T14:44:11Z<p>Mguesdon: /* G */</p>
<hr />
<div>''Please add mainly GNUstep related terms here.''<br />
<br />
== A ==<br />
* [[AppKit]]<br />
* [[Application]]<br />
<br />
== B ==<br />
* [[Back]]<br />
* [[Bundle]]<br />
* [[Bundle|Bundle, main]]<br />
<br />
== C ==<br />
* [[Category]]<br />
* [[Class]]<br />
* [[Controller]]<br />
<br />
== D ==<br />
* [[Delegate]]<br />
* [[DPS]]<br />
* [[Drag and Drop]]<br />
<br />
== E ==<br />
<br />
== F ==<br />
* First responder - see [[Responder]]<br />
* [[Foundation]]<br />
* [[Framework]]<br />
<br />
== G ==<br />
* [[GUI]]<br />
* [[GNUstep]]<br />
* [[GDL]]<br />
* [[GDL2]]<br />
<br />
== H ==<br />
<br />
== I ==<br />
* [[Instance variable]]<br />
* [[Invocation]]<br />
<br />
== J ==<br />
<br />
== K ==<br />
* [[Key Value Coding]]<br />
* [[Key Value Observing]]<br />
* Key window - see [[Window]]<br />
* KVC - see [[Key Value Coding]]<br />
<br />
== L ==<br />
<br />
== M ==<br />
* Main window - see [[Window]]<br />
* [[Makefile]]<br />
* [[MVC]]<br />
<br />
== N ==<br />
* NeXTSTEP<br />
<br />
== O ==<br />
* [[Objective-C]]<br />
* [[OpenStep]] - API standard<br />
* [[OPENSTEP]] - operating system<br />
* Outlet - see FIXME<br />
<br />
== P ==<br />
* [[Protocol]]<br />
<br />
== Q ==<br />
<br />
== R ==<br />
* [[Responder]]<br />
* Responder, first - see [[Responder]]<br />
* Responder chain - see [[Responder]]<br />
<br />
== S ==<br />
* [[Scripting]]<br />
* [[Service]]<br />
* [[Application Services|Services, application]]<br />
<br />
== T ==<br />
* [[Target-Action]]<br />
* [[Tool]]<br />
<br />
== U ==<br />
<br />
== V ==<br />
* [[View]]<br />
<br />
== W ==<br />
* [[Window]], ~ key, ~ main<br />
<br />
== X ==<br />
<br />
== Y ==<br />
<br />
== Z ==</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GDL&diff=2048GDL2005-08-29T14:42:37Z<p>Mguesdon: </p>
<hr />
<div>GNUstep Database Library<br />
<br />
[[EOF]] Compatible library</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Glossary&diff=936Glossary2005-08-29T14:42:25Z<p>Mguesdon: /* G */</p>
<hr />
<div>''Please add mainly GNUstep related terms here.''<br />
<br />
== A ==<br />
* [[AppKit]]<br />
* [[Application]]<br />
<br />
== B ==<br />
* [[Back]]<br />
* [[Bundle]]<br />
* [[Bundle|Bundle, main]]<br />
<br />
== C ==<br />
* [[Category]]<br />
* [[Class]]<br />
* [[Controller]]<br />
<br />
== D ==<br />
* [[Delegate]]<br />
* [[DPS]]<br />
* [[Drag and Drop]]<br />
<br />
== E ==<br />
<br />
== F ==<br />
* First responder - see [[Responder]]<br />
* [[Foundation]]<br />
* [[Framework]]<br />
<br />
== G ==<br />
* [[GUI]]<br />
* [[GNUstep]]<br />
* [[GDL2]]<br />
<br />
== H ==<br />
<br />
== I ==<br />
* [[Instance variable]]<br />
* [[Invocation]]<br />
<br />
== J ==<br />
<br />
== K ==<br />
* [[Key Value Coding]]<br />
* [[Key Value Observing]]<br />
* Key window - see [[Window]]<br />
* KVC - see [[Key Value Coding]]<br />
<br />
== L ==<br />
<br />
== M ==<br />
* Main window - see [[Window]]<br />
* [[Makefile]]<br />
* [[MVC]]<br />
<br />
== N ==<br />
* NeXTSTEP<br />
<br />
== O ==<br />
* [[Objective-C]]<br />
* [[OpenStep]] - API standard<br />
* [[OPENSTEP]] - operating system<br />
* Outlet - see FIXME<br />
<br />
== P ==<br />
* [[Protocol]]<br />
<br />
== Q ==<br />
<br />
== R ==<br />
* [[Responder]]<br />
* Responder, first - see [[Responder]]<br />
* Responder chain - see [[Responder]]<br />
<br />
== S ==<br />
* [[Scripting]]<br />
* [[Service]]<br />
* [[Application Services|Services, application]]<br />
<br />
== T ==<br />
* [[Target-Action]]<br />
* [[Tool]]<br />
<br />
== U ==<br />
<br />
== V ==<br />
* [[View]]<br />
<br />
== W ==<br />
* [[Window]], ~ key, ~ main<br />
<br />
== X ==<br />
<br />
== Y ==<br />
<br />
== Z ==</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Creating_document_based_applications&diff=2025Creating document based applications2005-08-29T14:38:40Z<p>Mguesdon: /* Introduction */</p>
<hr />
<div>Note: First version; subject to further revisions and changes.<br />
--[[User:Quineska|ChrisArmstrong]] 07:09, 7 Jul 2005 (CEST)<br />
<br />
== Introduction ==<br />
<br />
[[OpenStep]] can provide your application a document-based model. It helps to simplify the process of creating such applications. [[GNUstep]] implements this as well; this document aims to provide an overview of what is required in the creation and design of such an application.<br />
<br />
It is assumed you are familiar with GNUstep, and have some understanding as how to create [[Gorm]]'s interface files (often referred to as nib's), as well as some understanding of how they work.<br />
<br />
Importantly, such applications have certain components that are required, and should be considered as part of their design. When programming, classes that will be used as part of the [[AppKit]] are:<br />
<br />
==== NSDocument ====<br />
<br />
This class is central to the OpenStep document based model. These application's declare a new instance of a subclass of NSDocument for each “document” that is opened. You will subclass NSDocument to implement this.<br />
<br />
Each instance of your NSDocument subclass may have one or more windows associated with it. These are used as an interface for loading and saving a representation of your document type. Each window will have an “NSWindowController” instance associated with it, where NSDocument maintains a list of these.<br />
<br />
==== NSDocumentController ====<br />
<br />
This class acts a controller. It maintains a list of documents (instances of your NSDocument subclass) and is responsible for loading and instantiating new documents. It is usually not necessary to implement a subclass of this, but often it may be useful to implement special functionality (especially related to opening and creating documents at an application level).<br />
<br />
==== NSWindowController ====<br />
<br />
As mentioned above, NSWindowController instances are individually associated with one NSWindow instance, in such a way that a document maintains a list of window controllers that are reponsible for rendering the views associated with a document.<br />
<br />
You will most likely not have to subclass NSWindowController. Instead, you associate a nib file (the Gorm output) with the subclass of NSDocument, and NSDocumentController will load this nib file for each document that is created or loaded.<br />
<br />
For example, a text based application that is used for the editing of plain text files, may subclass NSDocument with a TextDocument class. Each instance of this class would have an NSWindowController instance associated with it, which in turn manages a window instance that is instantiated from a nib file. The NSDocumentController instance, as managed and instantiated by GNUstep, would be responsible for loading and saving documents in your application. It even prompts the user to save their documents when they try to quit the application.<br />
<br />
== File Components ==<br />
<br />
In building your application you will need to create a number of special files. From scratch, the following should be a rough guide to getting it working. These include the Makefile, your application's property list and the interface files.<br />
<br />
=== The Makefile ===<br />
<br />
For this type of application, no special makefile is needed: it just has to be a normal application. Project Builder should be able to spit out the required makefile and Gorm files that are needed for a generic application. I believe it is also capable of providing support for document-based applications. Otherwise use the following as a template:<br />
<br />
<br />
'''GNUmakefile'''<br />
<br />
include $(GNUSTEP_MAKEFILES)/common.make<br><br><br />
APP_NAME = DocumentApp<br><br />
DocumentApp_OBJC_FILES =<br><br />
MyDocument.m <br><br />
main.m<br><br><br />
DocumentApp_RESOURCES = \ <br><br />
Resources/Info-gnustep.plist \<br><br />
Resources/DocumentApp.gorm \<br><br />
Resources/MyDocument.gorm<br><br><br />
-include GNUmakefile.preamble<br><br />
include $(GNUSTEP_MAKEFILES)/application.make<br><br />
-include GNUmakefile.postamble<br><br />
<br />
For more information as to customising this file, as well as setting up compiler options for third party libraries and includes, see the GNUstep makefile manual.<br />
<br />
===The application dictionary===<br />
<br />
For those that have edited this file in their project before, it is a dictionary with various values entered. For our purposes, we need an array within the main dictionary, called "NSTypes". This is a array of unnamed dictionaries, with one dictionary for each type. <br />
<br />
I have provided an example for this file below. ProjectBuilder creates one as well. Please note that "TextEdit" does exist as an example application from NEXT I think, and again on MacOS X but I have constructed a much simpler version, used only for plain text files.<br />
<br />
Taking a look at the single dictionary entry in the NSTypes array, the following key-value pairs are needed:<br />
* '''NSDocumentClass:''' This is (string) the subclass name you use in your code, the "objective-c name" of your document subclass. This is used by NSDocumentController's default implementation to create instances of your document type.<br />
* '''NSName:''' The generic file type (string). This is completely arbitrary, and can be anything you like. For the purpose of conventions, it may be more appropriate not to use the "NS" or "GS" prefix (the latter of which I not sure), and instead use either your own, or no prefix at all.<br />
* '''NSHumanReadableName:''' The human readable name of your document type (string)? TODO: explain where this is used.<br />
* '''NSUnixExtensions:''' An array of strings, each containing a file extension connected to this document type on "unix" platforms. TODO: explain how "unix" is interpreted by GNUstep.<br />
* '''NSDOSExtensions:''' An array of strings, each containing a file extenstion connected to this document type on "DOS" platforms (could be loosely interpreted as any MS platforms GNUstep runs on, i.e. Windows 2000/XP).<br />
* '''NSRole:''' A string, either "Viewer" or "Editor", depending on how your document operates on this file type.<br />
* '''NSIcon:''' A icon name associated with this document type. TODO: Investigate how this works.<br />
<br />
<br />
'''Info-gnustep.plist'''<br />
{<br />
ApplicationDescription = "A simple text editor for GNUstep.";<br />
ApplicationName = TextEdit;<br />
ApplicationRelease = 0.10;<br />
Authors = ( "Christopher Armstrong" );<br />
Copyright = "Copyright (C) 2005 Christopher Armstrong";<br />
CopyrightDescription = "Released under GPL.";<br />
FullVersionID = 0.10;<br />
NSExecutable = TextEdit;<br />
NSMainNibFile = TextEdit.gorm;<br />
NSPrincipalClass = NSApplication;<br />
NSRole = Application;<br />
NSTypes = (<br />
{<br />
NSDocumentClass = "TextDocument";<br />
NSName = "GSTextDocumentType";<br />
NSHumanReadableName = "Text Document";<br />
NSUnixExtensions = ( "txt", "" );<br />
NSDOSExtensions = ( "txt" );<br />
NSRole = Editor;<br />
}<br />
);<br />
}<br />
<br />
<br />
For more information on property list files, consult [[Property Lists]].<br />
<br />
=== Interface files ===<br />
<br />
Two interface files are needed: one for your main application, and another that will be instantiated with each instance of your document subclass. These both should be listed as resources in your makefile, (as shown the GNUmakefile example above). It may be helpful to name the document nib file after your class.<br />
<br />
==== Application Interface File ====<br />
<br />
The application one should just be a menu (though it could be more if necessary). When constructing it, take the following into account:<br />
<br />
* Use a standard Gorm template for an Application.<br />
* Delete the window instance in the "Objects" pane (unless you need a main window, which is beyond the scope of this document).<br />
* Set NSOwner's class to "NSDocumentController". This is the custom class option of NSOwner in the property inspector. This ensures that the openDocument:, newDocument: messages, as sent to NSFirst, get picked up by NSDocumentController. Do not instantiate it (I believe you can't anyway).<br />
* If you intend to subclass NSDocumentController, subclass it in the Classes pane. To make sure that this class is instantiated and used, make sure you instantiate it in Gorm or in your main.m file, and set NSOwner to be your subclass.<br />
* Drag a Document menu from the palette onto your main menu. This already has the proper outlet and action linkage for each relevant message to be directed to NSFirst. Generic messages (such as openDocument:, not associated with any document instance) are forwarded to the shared instance of NSDocumentController (see it's reference documentation). When a document is active, more specific messages (such as close: or saveDocument:) are forwarded to the relevant document instance of your NSDocument subclass.<br />
* Add any appropriate menus such as "Info" and "Format" which may be relevant to your application.<br />
<br />
==== Document Interface File(s) ====<br />
<br />
The document interface file is a window containing the view(s) required for the implementation of one instance of your document type. For example, in the case of a TextDocument type, a window instance with a NSTextView drawn on it is used for each document window. This interface file is instantiated every time a person creates a new document (the newDocument: message is sent to NSDocumentController) or opens an existing document (openDocument:).<br />
<br />
You will need to:<br />
* '''Subclass NSDocument''' with your document type in Gorm. This is done in a couple of ways, see [[Gorm_Manual#Custom_classes|custom classes]]. It is up to you whether or not you let Gorm generate the class files, but make sure you add the appropriate outlets to your class in the source files (otherwise, I think your your program may segfault).<br />
* '''Set NSOwner:''' Set your subclass as NSOwner's Custom class using the Property Inspector. ''DO NOT INSTANTIATE IT.''<br />
<br />
Another thing that you may want to consider is custom outlets. If you place certain views or controls on your window (including the window itself), you may want to refer to them directly in your code, e.g. the NSTextView in our TextEdit example is accessed directly, so that we can save it's contents to a file. To enable this, we add outlets to our class (see [[Gorm_Manual#Custom_classes|custom classes]]). We then connect NSOwner to the appropriate controls/views, and select the outlets in the Connections Property Inspector (see [[Gorm_Manual#Editing_the_interface|editing the interface]]).<br />
<br />
== Code ==<br />
<br />
Various things need to be done at a code level, to ensure that your NSDocument subclass is properly instantiated. This section aims to tell you what is necessary.<br />
<br />
=== NSDocument subclass ===<br />
<br />
When creating your subclass, you may have chosen to have Gorm create the class files. If not, you should create two files for your subclass: a header (.h) file and an implementation file (.m). The header file should take the following layout (we're using the TextEdit example again):<br />
<br />
#ifndef TEXTDOCUMENT_H<br />
#define TEXTDOCUMENT_H <br><br />
#include <AppKit/AppKit.h> <br><br />
@class NSDocument; <br><br />
/* The document type string, as specified in the property list [[#The_application_dictionary|NSTypes array]] */ <br><br />
NSString * GSTextDocumentType = "GSTextDocumentType";<br />
@interface TextDocument : NSDocument<br />
{<br />
@protected<br />
/* Outlets we added in our Gorm nib file */<br />
id * textView;<br />
}<br />
/* Basic methods used for loading and saving document data (respectively). */<br />
- (BOOL) loadDataRepresentation:(NSData*)representation ofType:(NSString*)type;<br />
- (NSData*) dataRepresentationOfType: (NSString*)type; <br><br />
/* Information and events handling of GUI related changes */<br />
- (NSString*) windowNibName;<br />
- (void) windowControllerDidLoadNib:(NSWindowController*)windowController; <br><br />
@end<br><br />
<br />
Firstly, take note that we inherit from NSDocument. As a result, we need to override some methods for a basic (but working) implementation. <br />
<br />
==== loadDataRepresentation:ofType: and dataRepresentationOfType: ====<br />
<br />
The methods, loadDataRepresent:ofType: and dataRepresentationOfType: are used by NSDocumentController to load and save our files. The first method is called when the user trys to open a document (NSDocumentController gets the file name and copies it's data using an open panel). The method is passed the raw data in this file, as well as a string representing its type. It is important to note that this type string is the same one used in your property list. It is used by NSDocumentController to tell you what type it thinks you should open the data with. If this is not possible, or if there is an error trying to parse the data, your method returns FALSE/NO. Otherwise, you should store a local, meaningful representation of the data, which you can insert into your document window a little later (and return TRUE/YES).<br />
<br />
For example, in terms of the TextEdit example:<br />
- (BOOL) loadDataRepresentation:(NSData*) representation ofType:(NSString*)type<br />
{<br />
/*Check type information */<br />
if ([representation equalTo:GSTextDocumentType]==NO)<br />
return NO;<br />
/* Clean out our old representation if it still exists */<br />
if (fileContents) RELEASE(fileContents); <br><br />
/* Allocate room for the new data, and try to initialise a string with it. */<br />
self->fileContents = [NSString alloc];<br />
fileContents = [fileContents initWithBytes: [representation bytes]<br />
length: [representation length]<br />
encoding: NSASCIIStringEncoding]; <br><br />
/* If this can't be done, return NO */<br />
if (!fileContents)<br />
return NO; <br><br />
/* Otherwise, set our TextView to the string data. */<br />
[self->textView setString: fileContents];<br />
return YES;<br />
}<br />
<br />
If this is not sufficient, or if your program can open the data in a more efficient manner, it may be worth looking into overriding -initWithContentsOfFile:ofType: and -initWithContentsOfURL:ofType:. Again, see the GUI manual for more details.<br />
<br />
dataRepresentationOfType: is used to save the data. Your method is expected to return an instance of NSData that contains what should be saved to a file, for the type specified. Again, the ''type'' variable should be checked to ensure that you can write data of that type. Return nil if the file cannot be saved as that type.<br />
<br />
For example:<br />
<br />
- (NSData*) dataRepresentationOfType:(NSString*)type<br />
{<br />
if ([type equalTo:GSTextDocumentType]==NO)<br />
return nil; <br><br />
NSData stringData = [[textView string] dataUsingEncoding:NSASCIIStringEncoding]; <br />
return stringData; <br />
}<br />
<br />
If a more sophisticated save implementation is needed, consult the documentation for information on the writeTo* methods.<br />
<br />
==== windowNibName ====<br />
<br />
This method must be overriden to return the a string of the name of your nib file (without the file extension). More complex implementations will use other methods to load the interface files. TODO: information on what methods need to be overriden.<br />
<br />
==== windowControllerDidLoadNib: ====<br />
<br />
Use this method to add code that should be run as soon as ''windowController'' has been initialised. Your document may have many window controllers; each window controller taking possession of one window.<br />
<br />
In the TextEdit example, this method is used to copy the ''fileContents'' variable to the text view. It otherwise initialises the document window. <br />
<br />
Also note that you can override windowControllerWillLoadNib: to perform pre-interface loading initialisation.<br />
<br />
==== makeWindowControllers ====<br />
<br />
This is an optional method to override, which must be used if you have multiple window controllers per document. It is responsible for creating each window controller from it's interface file and then adding it to the document. Use the addWindowController: method.<br />
<br />
==== Other considerations ====<br />
<br />
* You need a way to notify NSDocument that your document has changed, so that NSDocumentController can enable the menu item to allow saving. This is done by a call to the updateChangeCount: method. For example, the TextDocument class adds itself as a delegate to the textView, for any notification of changes. It then calls updateChangeCount: in the delegate's method.<br />
<br />
* You may also wish to add a close: method (not the close method already in NSDocument, see below) to respond to the menu item permitting your document to close. This could perform cleanup operations before a call to [self close] is made e.g.<br />
<br />
- (void) close:(id)sender /* Note this is not the method found in NSDocument (they differ by a parameter) */<br />
{<br />
[self close];<br />
}<br />
<br />
=== NSDocumentController ===<br />
<br />
This class can optionally be subclassed, to implement some specific functionality. For example, programs handling multiple document types may override newDocument: to create a window so that the user can select which document type to create.<br />
<br />
You should use separate implementation files and add the .m file to GNUmakefile.<br />
<br />
=== NSWindowController ===<br />
<br />
This class can also be optionally subclassed, to implement functionality specific to a window controller for a document type. You may need to override makeWindowControllers: in the NSDocument subclass in order to make sure your specific window controller is instantiated.<br />
<br />
You should use separate implemenation files and add the .m file to GNUmakefile.<br />
<br />
== Optional Additions ==<br />
<br />
=== Custom NSDocumentController and NSWindowController implementations ===<br />
<br />
See [[#NSWindowController|NSWindowController]] and [[#NSDocumentController|NSDocumentController]].<br />
<br />
----<br />
<br />
[[Category:Development]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_As_a_Product&diff=1995GNUstep As a Product2005-08-29T14:37:16Z<p>Mguesdon: /* Marketing Objective-C */</p>
<hr />
<div>Ideas about how to market GNUstep<br />
<br />
== The GNUstep as a Product ==<br />
<br />
There are several definitions of GNUstep. One is [http://www.gnustep.org/ here] (Home), [http://www.gnustep.org/information/aboutGNUstep.html here] (Intro),[http://wiki.gnustep.org/index.php/Introduction%20to%20GNUstep here] (Wiki Intro) and [http://wiki.gnustep.org/index.php/GNUstepIsNotWM here] (GS vs WM).<br />
<br />
There are many uses for GNUstep, but we have to agree on single definition of a single product that will be provided at the beginning. Of course there are many flavours of GNUstep installations, but there should be only one or two introduced.<br />
<br />
The product definition should contain:<br />
* what it is<br />
* what it offers<br />
* references to something known and recognised (comparison is good for understanding)<br />
* strengths of gnustep<br />
* use few buzzwords, but very, very decently<br />
<br />
GNUstep by its nature IS some kind of environment, as it is not bunch of libraries, because it requires its own filesystem storage (for resources, for example) and running servers (daemons). We can call this more complex set of components an environment. As there are not many applications for GNUstep right now, the best product that can be done from GNUstep is "GNUstep Development Environment". Sugestion for general description of the environment:<br />
<br />
'''GNUstep''': ''GNUstep is a cross-platform, object oriented environment composed of frameworks, tools, and servers (daemons). It is very similar to the Cocoa frameworks from Apple, and tries to maintain compatibility with Cocoa wherever it is desired and possible. The frameworks provide classes for containers, distributed objects, object archiving, file management, text system, font management, image composition, WYSIWYG PostScript graphics, and more.''<br />
<br />
{| border=1<br />
! Product/Package<br />
! Description<br />
! Contents<br />
|+<br />
| '''Runtime Environment'''<br />
| Core that forms an environment in which GNUstep applications, tools and servers can be run.<br />
| GNUstep Core, Workspace application, Terminal application, example services<br />
|+<br />
| '''Development Environment'''<br />
| Collection of core applications for worskpace management, object relationship modelling, source code editing, terminal emulation and set of core development frameworks (Foundation and Application Kits) <br />
| Components from the Runtime Environment + Gorm, ProjectCenter, EasyDiff<br />
|+<br />
| '''Framework Collection''' [2] <br />
| Object oriented solutions for web application development, database (Oracle, MySQL, Postgresql,...) connectivity and object abstraction, language independent scripting<br />
| GSWeb, GDL2, StepTalk<br />
|}<br />
<br />
[1] No user applications are included, as it is an development environment.<br />
<br />
[2] feel free to replace the word Production with something better''.<br />
<br />
== Distribution and installation ==<br />
<br />
Any product has to be distributed. Current possible distribution channels are:<br />
<br />
* Direct distribution from GNUstep website through .tar.gz source or binaries<br />
* MS Windows executable<br />
* Debian based linux distributions with .deb packages<br />
* RPM packaging based distributions<br />
<br />
Installation should be as easy as:<br />
<br />
# Download<br />
# Launch installer (doubleclicking in hosting environment is prefered)<br />
# Configure<br />
# Run!<br />
<br />
For Linux distributions with native packaging systems, there should be meta package containing several gnustep packages according to the gnustep products/solutions.<br />
<br />
For other Linux distributions, installation should be either guarded by executable package or by providing instructions that can be moved by Copy & Paste into a terminal window.<br />
<br />
For MS Windows, the installer should create full binary installation of the gnustep environment that is ready to launch. It should place a GNUstep icon on the desktop or into the start menu. Launching ''GNUstep development session'' is same as launching GWorkspace.app or Terminal.app<br />
<br />
== Using GNUstep Development Environment ==<br />
<br />
User should be able to use GNUstep D.E. by clicking on an icon or picking a menu item. For the time being, the main entry to the environment should be GWorkspace or Terminal.app. No .cshrc or .bashrc fiddling should be required.<br />
<br />
Having GNUstep useable from user's preffered terminal is for advanced users. Instructions for required 'sourcing' and 'setting env variables' should be given at the end of the installation and should be explicitly marked as instructions for advanced users.<br />
<br />
Alternative for the development nevironment, there should be a very simple 'dock application' with preconfigured entries for GWorkspace, Terminal.app, Gorm.app and ProjectCenter.app. Nothing fancy, simple window with matrix of buttons with icons.<br />
<br />
GWorkspace should be preconfigured to contain icons for System/Applications, Local/Applications, System/Documentation and Local/Documentation on the shelf.<br />
<br />
== Goals and how to get there ==<br />
First a list of the primary goals:<br />
* Get more app developers<br />
* Get more app users<br />
<br />
Why do we want them:<br />
* More testing of the GNUstep-core<br />
* More bug fixes of GNUstep-core<br />
* More applications that use GNUstep-core<br />
<br />
How to attract developers:<br />
* Good documentation<br />
* Easy to use tools<br />
* Complete development set<br />
<br />
How to attract users:<br />
* Apps<br />
* Apps<br />
* Apps<br />
<br />
Where do we "hire" developers:<br />
* See the list below<br />
<br />
developers already know some kind of language, so we have to address them from their starting point. You want to be able to point e.g. a Java programmer to a document that targets the Java programmer to use [[Objective-C]].<br />
<br />
Where do we find users:<br />
* See the list below<br />
* Make sure GNUstep is incorporated in as many distro's as possible<br />
<br />
How are we gonna approach developers?<br />
How are we gonna approach users?<br />
<br />
== Marketing [[Objective-C]] ==<br />
Working with a language that is not familiar to most programmers requires a lot of marketing. The first idea was to create a list that shows the highlights of the language then create documents that tell e.g. a Java programmer how to do things in [[Objective-C]], and also for C programmes, C++ programmers etc. So an article per programming language.<br />
<br />
== Other notes ==<br />
<br />
[[Release procedure]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_As_a_Product&diff=933GNUstep As a Product2005-08-29T14:36:47Z<p>Mguesdon: /* Goals and how to get there */</p>
<hr />
<div>Ideas about how to market GNUstep<br />
<br />
== The GNUstep as a Product ==<br />
<br />
There are several definitions of GNUstep. One is [http://www.gnustep.org/ here] (Home), [http://www.gnustep.org/information/aboutGNUstep.html here] (Intro),[http://wiki.gnustep.org/index.php/Introduction%20to%20GNUstep here] (Wiki Intro) and [http://wiki.gnustep.org/index.php/GNUstepIsNotWM here] (GS vs WM).<br />
<br />
There are many uses for GNUstep, but we have to agree on single definition of a single product that will be provided at the beginning. Of course there are many flavours of GNUstep installations, but there should be only one or two introduced.<br />
<br />
The product definition should contain:<br />
* what it is<br />
* what it offers<br />
* references to something known and recognised (comparison is good for understanding)<br />
* strengths of gnustep<br />
* use few buzzwords, but very, very decently<br />
<br />
GNUstep by its nature IS some kind of environment, as it is not bunch of libraries, because it requires its own filesystem storage (for resources, for example) and running servers (daemons). We can call this more complex set of components an environment. As there are not many applications for GNUstep right now, the best product that can be done from GNUstep is "GNUstep Development Environment". Sugestion for general description of the environment:<br />
<br />
'''GNUstep''': ''GNUstep is a cross-platform, object oriented environment composed of frameworks, tools, and servers (daemons). It is very similar to the Cocoa frameworks from Apple, and tries to maintain compatibility with Cocoa wherever it is desired and possible. The frameworks provide classes for containers, distributed objects, object archiving, file management, text system, font management, image composition, WYSIWYG PostScript graphics, and more.''<br />
<br />
{| border=1<br />
! Product/Package<br />
! Description<br />
! Contents<br />
|+<br />
| '''Runtime Environment'''<br />
| Core that forms an environment in which GNUstep applications, tools and servers can be run.<br />
| GNUstep Core, Workspace application, Terminal application, example services<br />
|+<br />
| '''Development Environment'''<br />
| Collection of core applications for worskpace management, object relationship modelling, source code editing, terminal emulation and set of core development frameworks (Foundation and Application Kits) <br />
| Components from the Runtime Environment + Gorm, ProjectCenter, EasyDiff<br />
|+<br />
| '''Framework Collection''' [2] <br />
| Object oriented solutions for web application development, database (Oracle, MySQL, Postgresql,...) connectivity and object abstraction, language independent scripting<br />
| GSWeb, GDL2, StepTalk<br />
|}<br />
<br />
[1] No user applications are included, as it is an development environment.<br />
<br />
[2] feel free to replace the word Production with something better''.<br />
<br />
== Distribution and installation ==<br />
<br />
Any product has to be distributed. Current possible distribution channels are:<br />
<br />
* Direct distribution from GNUstep website through .tar.gz source or binaries<br />
* MS Windows executable<br />
* Debian based linux distributions with .deb packages<br />
* RPM packaging based distributions<br />
<br />
Installation should be as easy as:<br />
<br />
# Download<br />
# Launch installer (doubleclicking in hosting environment is prefered)<br />
# Configure<br />
# Run!<br />
<br />
For Linux distributions with native packaging systems, there should be meta package containing several gnustep packages according to the gnustep products/solutions.<br />
<br />
For other Linux distributions, installation should be either guarded by executable package or by providing instructions that can be moved by Copy & Paste into a terminal window.<br />
<br />
For MS Windows, the installer should create full binary installation of the gnustep environment that is ready to launch. It should place a GNUstep icon on the desktop or into the start menu. Launching ''GNUstep development session'' is same as launching GWorkspace.app or Terminal.app<br />
<br />
== Using GNUstep Development Environment ==<br />
<br />
User should be able to use GNUstep D.E. by clicking on an icon or picking a menu item. For the time being, the main entry to the environment should be GWorkspace or Terminal.app. No .cshrc or .bashrc fiddling should be required.<br />
<br />
Having GNUstep useable from user's preffered terminal is for advanced users. Instructions for required 'sourcing' and 'setting env variables' should be given at the end of the installation and should be explicitly marked as instructions for advanced users.<br />
<br />
Alternative for the development nevironment, there should be a very simple 'dock application' with preconfigured entries for GWorkspace, Terminal.app, Gorm.app and ProjectCenter.app. Nothing fancy, simple window with matrix of buttons with icons.<br />
<br />
GWorkspace should be preconfigured to contain icons for System/Applications, Local/Applications, System/Documentation and Local/Documentation on the shelf.<br />
<br />
== Goals and how to get there ==<br />
First a list of the primary goals:<br />
* Get more app developers<br />
* Get more app users<br />
<br />
Why do we want them:<br />
* More testing of the GNUstep-core<br />
* More bug fixes of GNUstep-core<br />
* More applications that use GNUstep-core<br />
<br />
How to attract developers:<br />
* Good documentation<br />
* Easy to use tools<br />
* Complete development set<br />
<br />
How to attract users:<br />
* Apps<br />
* Apps<br />
* Apps<br />
<br />
Where do we "hire" developers:<br />
* See the list below<br />
<br />
developers already know some kind of language, so we have to address them from their starting point. You want to be able to point e.g. a Java programmer to a document that targets the Java programmer to use [[Objective-C]].<br />
<br />
Where do we find users:<br />
* See the list below<br />
* Make sure GNUstep is incorporated in as many distro's as possible<br />
<br />
How are we gonna approach developers?<br />
How are we gonna approach users?<br />
<br />
== Marketing Objective-C ==<br />
Working with a language that is not familiar to most programmers requires a lot of marketing. The first idea was to create a list that shows the highlights of the language then create documents that tell e.g. a Java programmer how to do things in Objective-C, and also for C programmes, C++ programmers etc. So an article per programming language.<br />
<br />
== Other notes ==<br />
<br />
[[Release procedure]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Gorm_Manual&diff=1000Gorm Manual2005-08-29T14:35:40Z<p>Mguesdon: /* Overview */</p>
<hr />
<div>== Guide to the Gorm application ==<br />
<br />
{| style="border:1px solid black; background-color:lavender; padding:10pt;"<br />
|+<br />
| <br />
Documentation authors:<br />
* Gregory John Casamento <greg_casamento@yahoo.com><br />
* Richard Frith-Macdonald <richard@brainstorm.co.uk><br />
<br />
''Copyright 1999,2000,2004,2005 Free Software Foundation, Inc.''<br />
<br />
''License: FDL 1.2''<br />
|}<br />
<br />
<br />
=== Gorm Developers ===<br />
<br />
* Gregory John Casamento <greg_casamento@yahoo.com> Is the current maintaner of Gorm. Has implemented lots of new features and rewritten large portions of the existing code.<br />
* Richard Frith-Macdonald <richard@brainstorm.co.uk> wrote the original version of Gorm as part of the GNUstep project.<br />
* Pierre-Yves Rivaille <gnustep@rivaille.net> Is also a major contributor to the Gorm application.<br />
<br />
== Overview ==<br />
<br />
[[Image:GormFull.png|right|thumbnail|Gorm 0.10.2 running on Linux showing the main windows and the inspector.]]<br />
<br />
Gorm is an application for creating the user interface (and possibly entire<br />
applications) for a GNUstep application. Initially a close clone of the old<br />
NeXTstep 3.3 Interface Builder application, I expect that Gorm will mutate<br />
beyond the capabilities of that app.<br />
<br />
GNUstep is an object-oriented programming framework and a collection of tools<br />
developed for or using the GNUstep libraries.<br />
<br />
You can find out more about GNUstep at [http://www.gnustep.org]<br />
<br />
The basic idea behind Gorm is simple - it provides a graphical user interface<br />
with which to connect together objects from the GNUstep libraries (as well as<br />
custom-written objects) and set their attributes in an easy to use manner.<br />
<br />
The collection of objects is then saved as a document which can either be<br />
re-loaded into Gorm for further editing, or can be loaded into a running<br />
GNUstep application in order to provide that application with a user<br />
interface or some subsystem.<br />
<br />
This manual assumes a working knowledge of [[Objective-C]] and C. These are <br />
necessary prerequisites to understanding some of the technical details and <br />
examples given here.<br />
<br />
This manual is ment to cover basic operation of the Gorm application. More about the GNUstep development and programming, please refer to the links at the end of this document.<br />
<br />
=== Major features ===<br />
<br />
* Drag-and-drop creation of GUI elements from palettes.<br />
* Direct on-screen manipulation of GUI elements<br />
* Manipulation and examination of objects via inspectors.<br />
* Drag-and-drop creation of connections between objects.<br />
* Interactive test mode for interfaces/object-networks under development.<br />
* Saving data in a format loadable by GNUstep applications.<br />
* Run-time loading of additional palettes that may be written using an API<br />
<br />
== First contact ==<br />
<br />
To launch the Gorm application, select it in the workspace's file viewer or from the dock. If you are using terminal, then type following on the command line:<br />
<br />
gopen Gorm.app<br />
<br />
=== Menu ===<br />
<br />
[[Image:GormMenu.png|right|thumbnail|Gorm's menu in detail.]]<br />
<br />
Here is a description of the menu structure and what each menu does -<br />
<br />
* Info: The info menu produces a submenu ...<br />
** Info Panel: A panel giving very limited information about Gorm<br />
** Preferences: A panel allowing you to set preferences<br />
** Help (not implemented)<br />
** A panel providing general help on using Gorm<br />
<br />
* Document: The Document menu item produces a submenu ...<br />
** Open: This produces an open panel that lets you open a Gorm document.<br />
You use this if you want to use Gorm to edit an exisiting document.<br />
** New Application: This creates a new application document within Gorm, you may then use the Palettes panel to drag new objects into the document.<br />
** New Module: Contains a submenu, which also contains:<br />
*** New Empty: produces an empty document with only NSFirst and NSOwner.<br />
*** New Inspector: produces a document with NSOwner, NSFirst and a window which is the correct size for an Inspector.<br />
*** New Palette: produces a document which is like the one by New Inspector, but it's window is the right size for a Palette. <br />
** Save: This saves the current document<br />
** Save As: This saves the current document to a new file and changes the document name to match the new name on disk.<br />
** Save All: This saves all documents currently being edited by Gorm.<br />
** Revert To Saved: This removes all changes made to the document sunce the last save, or since the document was opened.<br />
** Test Interface: This provides interactive testing of the active document. To end testing, you need to select the quit menu item.<br />
** Miniaturize: This miniaturises the active document (or whatever panel is currently key).<br />
** Close: This closes the currenly active document.<br />
** Debug: Prints some useful internal information.<br />
** Load Sound: Loads a sound into the .gorm file.<br />
** Load Image: Loads an image into the .gorm file.<br />
<br />
* Edit: In addition to the usual Cut, Copy, Paste, Delete Select All, this menu also contains:<br />
<br />
** Group: Which produces a submenu<br />
*** In Splitview: Groups views into an NSSplitView. Gorm does this based on the relative positions of the views being grouped. It determines the orientation and the order of th views and then groups them either vertically or horizontally in the order they appear on the screen.<br />
*** In Box: Simply groups all of the views into one NSBox.<br />
*** In ScrollView: Simply groups all of the views into one NSScrollView.<br />
*** Ungroup: Ungroups the contained views.<br />
<br />
** Set Name: This allows the user to set a name for a given object in the Objects view in the main document window.<br />
<br />
** Disable Guideline: This item toggles between Enable Guideline and Disable Guideline. This allows the user to turn on or off the guides which appear when placing views in a window or view in Gorm.<br />
<br />
* Classes: Contains menus for working with classes.<br />
** Create Subclass: Creates a subclass of the currently selected class in the current document classes view.<br />
** Load Class: Loads a class from a .h file into the current document.<br />
** Create Class Files: Generates a .h and .m file from the currently selected class in the current document classes view.<br />
** Instantiate: Creates an instance of the selected class in the current document classes view.<br />
** Add Outlet/Action: Adds an outlet or an action depending on what is selected in the document classes view. If the outlet icon is selected, it will add an outlet, if it the action icon is selected it will add an action.<br />
** Remove: Removes the currently selected outlet, action or class.<br />
<br />
* Tools: Contains the inspector and the palette menus<br />
** Inspector: Shows the inspector<br />
** Palette: Shows the palette<br />
** Load Palette: Opens a file panel and allows the user to load a palette into Gorm.<br />
<br />
* Windows: Shows currently open windows.<br />
<br />
* Services: Shows currently available services.<br />
<br />
* Hide: Hides the application.<br />
<br />
* Quit: Quits the application.<br />
<br />
=== Preferences ===<br />
<br />
The preferences panel contains a number of useful customizable options which can be used to modify the behavior of Gorm.<br />
<br />
Some of these defaults can be safely modified from the command line by the user.<br />
* PreloadHeaders:<br />
The user can define a set of headers to load when Gorm starts creation of a new .gorm file. This is useful when the user is building a framework or a set of interfaces for a large application.<br />
<br />
* ShowInspectors:<br />
Controls whether the inspector shows when Gorm is started.<br />
<br />
* ShowPalettes:<br />
Controls whether the palettes window shows when Gorm is started.<br />
<br />
* BackupFile:<br />
Determines if the old .gorm is moved to .gorm~ when the modified version is saved.<br />
<br />
<br />
== Basic Concepts ==<br />
<br />
This chapter will explain some of the basic things you need to understand before starting work on a new application.<br />
<br />
First you need to understand a few basic concepts. Gorm's main window includes a few standard entries which must be explained before we can proceed. The basic objects are abstract and they are being concretised on the runtime. They are:<br />
<br />
* an owner of the object model or the user interface - NSOwner<br />
* first responder - an object or a view that will receive actions as first - NSFirst<br />
* a font manager representation - NSFont<br />
<br />
[[Image:GormDocument.png|thumb|The document window of Gorm showing NSOwner and NSFirst.]]<br />
<br />
'''NSOwner''' is the class which "owns" the interface. This is, by default, [[NSApplication]], but it can be any class you like. You can change it by selecting NSOwner in the document window and going to the "Custom Class" inspector in the inspectors window. From there, you should see all of the classes which the NSOwner can assume. We'll discuss more about this later when we go over how to create a new application<br />
<br />
'''NSFirst''' is your interface to the responder chain. NSFirst is representative of the current "first responder" in the application. When you want a message, such as a changeFont: message, to go to the current first responder from, say, a menu, you connect the menu item to the NSFirst object in the document window. By doing this, it means that whichever object has first responder status at that time in the application will become the reciever of the "changeFont:" message. <br />
<br />
'''NSFont''' represents the NSFontManager object for the application. This object is a shared singleton. This means that, for any given app, there should be only one instance of the object. This object is generally added to the document window when another objec, such as a Font menu item, is added to the interface, which, in turn, requires that this object be added to the document.<br />
<br />
=== Responder and responder chain ===<br />
<br />
A responder is any subclass of NSResponder. This includes NSWindow, NSView and all of the NSControl subclasses.<br />
<br />
The '''responder chain''' is a sequence of objects which are called to determine where a message sent to the first responder will go. A message invoked on the first responder will be invoked on the first object in the responder chain which responds to that message.<br />
<br />
The object which this message will be called on is determined in the method [NSApplication targetForAction:]. The call sequence is as follows, it will only proceed to the next step in each case if the current step fails to respond to the message which was invoked:<br />
<br />
* The firstResponder of the keyWindow, if one exists. <br />
* Iterates through all responders by pulling each in the linked list of responders for the key window. <br />
* It then tries the keyWindow.<br />
* Then the keyWindow's delegate<br />
* if the application is document based it tries the document controller object for the key window.<br />
* then it tries the mainWindow's list of responders (as above)<br />
* the mainWindow's delegate<br />
* if the app is document based, it tries the document controller for the main window<br />
* and finally, it tries the NSApplication delegate.<br />
<br />
If all of the options in this list are exhausted, it then gives up and returns nil for the object which is to respond.<br />
<br />
== Creating an Application Interface ==<br />
<br />
Gorm provides you with prebuilt interface template for an application. Note that to create whole application you would need to use the [[ProjectCenter]] or other development tools. <br />
<br />
If you have ProjectCenter create an "Application" project. Create it with the name "FirstApp". From there you can open the MainMenu.gorm by clicking on interfaces and selecting MainMenu.gorm. If Gorm.app is properly installed, you Gorm should start up.<br />
<br />
If you don't have ProjectCenter, you can create the Gorm file by hand. First you need to start Gorm. You can either do this by doing: <br />
<br />
<br />
You then need to select the Document menu, and then New Application. This should produce a new document window, with a menu and an empty window. This should be the same as with the ProjectCenter gorm file since this is the basic starting point for an application.<br />
<br />
For the sections below... only do one or the other, not both. <br />
<br />
<br />
== Editing the interface ==<br />
<br />
=== Adding Controls from the Palette ===<br />
<br />
Go to the Gorm menu and select Tools, then Palettes. This will bring the palette window to the front. The second palette from the left is the "ControlsPalette". Select that one and find the button object (it should have the word "Button" in it). Drag that to the window and drop it anywhere you like.<br />
<br />
Repeat this operation with the text field. It's the control with "Text" in it. We are now ready to start making connections between different objects in the document.<br />
<br />
=== Making Connections ===<br />
<br />
The type of application we are creating is known as a "NSApplication delegate" this means that the MyController object will be set as the delegate of NSApplication.<br />
<br />
To make this connection click on NSOwner and hold down the Control button, keep it pressed as you drag from the NSOwner object to the MyController object. The inspectors window should change to the Connections inspector and should show two outlets "delegate" and "menu". Select the "delegate", at this point you should see a green S and a purple T on the NSOwner and MyController objects respectively, and press the "Connect" button in the inspector. In the "Connections" section of the inspector you should see an entry which looks similar to "delegate (MyController)" this indicates that the connection has been made.<br />
<br />
Now we need to make connections from the controller to the textfield and from the controller to the button. Select the MyController object and Control-Drag (as before) from the object to the text field, this will make an outlet connection. You should see the connections inspector again, this time select the "value" outlet and hit Connect. <br />
<br />
Next, control-drag from the button to the controller, this will make an action connection. The connections inspector should again appear. This time you need to select the "target" outlet, to get the list of actions. The list should have only one entry, which is "buttonPressed:" since this is the one we added earlier. Press Connect. You should see an entry like "buttonPressed: (MyController" in the Connections section of the inspector.<br />
<br />
It is also possible to make this connection to NSFirst, but to keep things simple, make it directly to the object. If you make the connection to buttonPressed: on NSFirst the functionality of the application will be unchanged, but the invocation will take the path described above in the section which describes "The Responder Chain".<br />
<br />
=== Saving the gorm file ===<br />
<br />
At this point you must save the .gorm file. Go to the Gorm menu and click Documents and then select "Save". If the document was opened from a pre-existing .gorm, it will save to that same file name. If it is an UNTITLED .gorm file a file dialog will appear and you will need to select the directory where you want to store the .gorm file and type the name of the .gorm file. <br />
<br />
== Custom classes ==<br />
<br />
There are two ways to do create a custom class in Gorm. I will take you through each step by step. First click on the classes icon in the toolbar on the top of the Gorm document window. You should see the view below change to an outline view containing a list of class names. Once this happens we're ready to create a class.<br />
<br />
Select the class you wish to subclass in the outline view. For our example we will use the simplest: NSObject. Select it by clicking on the class name once. Then go to the Classes menu in the main menu and select Create Subclass (you can also type Alt-Shift-c, which will do this as well. The new class will be created in the list with the name "NewClass".<br />
<br />
=== Using The Outline View ===<br />
<br />
Double click on the subclass name to make it editable. Type the name of the class and hit enter. For our example, please use the class name MyController. When you hit enter an alert panel will appear and warn you about breaking connections, simply select OK and continue.<br />
<br />
This method of inputting the classes was inspired by IB in OPENSTEP 4.2/Mach which had functionality very similar to this. For users of that the transition to Gorm will be seamless.<br />
<br />
=== Object awakening ===<br />
<br />
The method ''awakeFromNib'' is called on any custom object which is unarchived from a nib/gorm file. This method is called on all objects after the entire archive has been loaded into memory and all connections have been made. Given all of this, you should not make any assumptions at all about which objects have been called and which have not. You should not release any objects in this method.<br />
<br />
=== Outlets and Actions ===<br />
<br />
Too add an outlet, select the round icon with the two horizontal lines in it (it sort of looks like a wall outlet. This should become depressed. Here you need to go to the Gorm Menu, under Classes select "Add Outlet/Action". Each time you press this menu item another outlet will be added with a name similar to newOutlet, as you add more the number at the end will increase. For now add only one outlet.<br />
<br />
To rename the outlet simply double click it and change it's name like you did the class above to "value" for the sake of our example.<br />
<br />
The steps to add on action are precisely the same as adding an outlet, except you must click on the button which looks like a target (a circle with a + inside). Add an action and name it "buttonPressed:" for the sake of our example.<br />
<br />
=== Using The Class Edit Inspector ===<br />
<br />
This way is much more inline with the "OPENSTEP/GNUstep" philosophy. For each object there is an inspector, even for Class objects.<br />
<br />
Once you have created the class as described in the previous section "Creating a Class In Gorm", you must skip to this section to use the inspector. In the Gorm main menu select Tools and then select "Inspectors". This will make certain that the inspectors window is being displayed. Once the inspectors window is up move the pulldown on the top to "Attributes" and select the class you created which should, at this point, have the name "NewClass". You'll notice that the "Class" field at the top which shows the name's background color has turned white, instead of grey. This indicates that this class name is editable. Erase "NewClass" from the text field and type "MyController".<br />
<br />
Adding outlets is very intuitive in the inspector. Simply select the "Outlets" tab in the tab view and click "Add" to add more outlets, and "Remove" to remove them. For the sake of our example, add one outlet and name it "value".<br />
<br />
Very much like above only with the "Actions" tab, add an action called button pressed.<br />
<br />
=== Instantiating The Class ===<br />
<br />
In the Classes outline view select the new class you've created, now called MyController and then go to the Gorm menu and select Classes, and then Instantiate. The document window should shift from the classes view to the objects view. Amoung the set of objects should be a new object called MyController.<br />
<br />
=== Generating .h and .m files from the class. ===<br />
<br />
This is different than saving, some people have gotten this confused with the idea of Gorm generating the code for the gui. Gorm does nothing of the sort (grin). <br />
<br />
Go to the Classes section in the Document window and select the MyController class yet again. Now go to the Gorm menu and select Classes and the select "Create Class Files". This will bring up a file panel and it allow you to select the directory in which to put the files. It will first create the MyController.m file and then the MyController.h file. Simply select the directory in which your app will reside and hit okay for both. You can change the names, but the default ones, which are based on the class name, should be sufficient. When you look at the .m for this class, you should see the buttonPressed: method with the comment /* insert your code here */ in it. Delete this comment and add:<br />
<br />
[value setStringValue: @"Hello"]; <br />
<br />
The class should look like this after you're done:<br />
<br />
#include <AppKit/AppKit.h><br />
#include "MyController.h"<br />
@implementation MyController<br />
- (void) buttonPressed: (id)sender<br />
{<br />
[value setStringValue: @"Hello"];<br />
}<br />
@end<br />
<br />
You recall, we connected the textfield to the "value" variable. The call above causes the method setStringValue to be invoked on the textfield you added to the window. <br />
<br />
Also, note that the name of the method is "buttonPressed:". This is the action which is bound to the button. When it is pressed the text in the textfield should change to "Hello".<br />
<br />
You now need to build the application either by copying in a GNUmakefile and making the appropriate changes or by using ProjectCenter's build capability, depending on if you use it or not.<br />
<br />
This app is available as "SimpleApp" in the Examples directory under the Documentation directory distributed with Gorm. Hopefully this has helped to demonstrate, albeit on a small scale, the capabilities of Gorm. In later chapters we will cover more advanced application architectures and topics.<br />
<br />
== A Simple Application ==<br />
<br />
This chapter will describe an application, very much like the previous one, but using a slightly different structure. This application builds on the previous application and uses WinController as the NSOwner of the app instead of making it the delegate of NSApplication.<br />
<br />
=== Adding Menu Items ===<br />
<br />
Select the first palette in the palette window, this should be the MenusPalette. The palette will have a bunch of pre-made menu items on it that you can add. We want to keep this simple, so grab the one called "Item" and drag it over to the menu in main menu nib (the menu on the screen, not the one in the objects view). As you have this object over the menu, the copy/paste mouse cursor should appear (it looks something like one box over another box at a 45 degree angle). Where you drop the menu determines it's position in the menu. You can always drag it to a new position after you've placed it by simply selecting and dragging up or down. Once you've placed the menu item, double click on the title and change it to "Open"<br />
<br />
You can also change the name in the NSMenuItem attributes inspector. Now you must add openWindow: to MyController and make the connection from the "Open" menu item to NSFirst. In the connections inspector, find the "openWindow:" action. You could simply make the connection directly, but this is an exaple to show you that this connection will work as well. Whichever object has First Responder status will be tested to see if it responds to this method.<br />
<br />
The implementation for openWindow: in MyController should simply be:<br />
<br />
- (void) openWindow: (id) sender<br />
{<br />
winController = [[WinController alloc] init];<br />
}<br />
<br />
Also add the winController attribute and an include to allow WinController to be referenced in the MyController.m file.<br />
<br />
=== Making a Controller-based .gorm file ===<br />
<br />
Create a new .gorm file as described in the previous section using the "New Module" menu item. Under "New Module" select "New Empty". This should produce a .gorm file with only NSOwner and NSFirst. From the WindowsPalette (which should be the second palette in the palette window) drag a window to the location where you want it to appear on the screen. In the window add a button called "Close".<br />
<br />
Go through the same steps you went through previously to create MyController, except for adding the outlets/actions, but this time with the name WinController. Add an outlet called window and an action called "closeWindow:". <br />
<br />
Now, instead of instantiating the class go back to the objects view and select the NSOwner object. After that select the "Custom Class" inspector. Look for the entry for WinController and select it. You now must connect the "window" outlet to the Window you added previously.<br />
<br />
Switch back to the objects view, then Control-Drag not to the window on the screen, but to the window's representation in the objects view. In the connection inspector select the window outlet and click Ok.<br />
<br />
Save the .gorm as using the name Controller.gorm in the project directory. <br />
<br />
Generate the Controller.h and Controller.h files as described in the previous section.<br />
<br />
=== Add the init method to WinController ===<br />
<br />
Add an implementation of the action "closeWindow:" to WinController and also an init which loads the gorm/nib file and declares itself as the owner. Here's how:<br />
<br />
/* All Rights reserved */<br />
#include <AppKit/AppKit.h><br />
#include "WinController.h"<br />
@implementation WinController<br />
- (id) init<br />
{<br />
if((self = [super init]) != nil)<br />
{<br />
if([NSBundle loadNibNamed: @"Controller" owner: self] == NO)<br />
{<br />
NSLog(@"Problem loading interface");<br />
return nil;<br />
}<br />
[window makeKeyAndOrderFront: self];<br />
}<br />
return self;<br />
}<br />
// close<br />
- (void) closeWindow: (id) sender<br />
{<br />
[window close];<br />
}<br />
// dealloc<br />
- (void) dealloc<br />
{<br />
[super dealloc];<br />
RELEASE(window);<br />
}<br />
@end <br />
<br />
The Controller gorm will be loaded and the connections will be made to the current instance, i.e. window will point to the window object instantianted in the .gorm file and all actions declared in the .gorm file which are attached to the object NSOwner will be resolved on self.<br />
<br />
=== Running the App ===<br />
<br />
Type the command: <br />
<br />
gopen Controller.app<br />
<br />
on the command line in the project directory. Once the application has started it should look very much like the first application. Select the "Open" button from the Menu and you should see the second window pop up, now choose close, this will call the method "closeWindow:" which should cause the window to disappear.<br />
<br />
<br />
== Advanced Topics ==<br />
<br />
=== Restrictions On Your Custom Subclasses ===<br />
<br />
The restrictions here are the same as those in Apple's InterfaceBuilder. In general, you cannot have additional information which is expected to be decoded in an initWithCoder: method from a custom class which uses one of the methods in the previous section. This is because, by definition, Gorm doesn't know anything about these classes and allowing you to use them in Gorm in this way is a convenience to make it simpler for the developer. Gorm therefore, must use one of the proxies to encode the class since it cannot encode the class directly.<br />
<br />
How can you get your classes into Gorm, you say? I'm pleased that you asked me that question. The best way to make your class known to Gorm so that you don't need to worry about the above restriction is to add a palette which contains your class. In this way, because you're literally linking the class into Gorm, you're making the class and it's structure known to Gorm so that it can encode the class directly. With the new palette loaded you can load and save classes containing real instances, not proxies, of your class encoded directly in the .gorm file. How to create a palette is discussed at length in the following section.<br />
<br />
=== Graphical Objects In A Palette ===<br />
<br />
You are, by now, familiar with the built in palettes which are provided with Gorm. Palettes are a powerful feature which allows the developer to add his/her own objects to Gorm. It is possible for a developer to write custom inspectors, editors and palettes for use with Gorm. A good example of a custom palette is palettetest in the dev-apps/test in the GNUstep distribution. Assuming you don't have that, however, I will explain precisely what you need to do in order to create a simple palette. The entire process is very short and suprisingly simple. First open Gorm and select Gorm->Document->New Module->New Palette. This will create a palette sized window. Once that's done go to the classes view in the main document window and find "IBPalette" in the class list. Create a subclass of that, the name can be whatever you want. For the purposes of our example we'll call it MyPalette. Drag a custom view to the window and choose the class you would like to add to the palette from one of your custom classes.<br />
<br />
Once you've done this, generate the code for the classes (discussed in previous chapters). In the code, you'll add a method called "-(void) finishInstantiate" leave it empty for now. In the makefile for the palette make sure that the library or framework the view comes from is linked with the palette. Now build the palette.<br />
<br />
After the palette is built you're ready to load it into Gorm. Go to the preferences panel and go to "Palettes". This should bring up a table view. Click on add. You should see a open dialog open. Select the palette bundle with this. If the palette is successfully loaded, you should see the name appear in the list. One thing to note here. Once a palette is loaded, it can't be unloaded until you close and restart Gorm. This is because by loading the palette bundle, the code in the bundle is being linked into Gorm. This can't be undone, once it's done.<br />
<br />
Now, you should see the palette in the set of palettes in the palette window. Simply scroll over to it and select it's icon. When you do this, you should see the view that you set up using the custom view displayed as an actual instance. Note that we used one of the techniques listed above, it is possible to use any of the three for any object you add to your palette. You can now drag the view from the palette to a new window.<br />
<br />
=== Non-Graphical Objects In A Palette ===<br />
You may recall the creation of a method called "-(void) finishInstantiate" in the previous section. This section will make full use of that method. Re-open the palette you created before, but this time add an image view to the window. Then add to the image view, the icon you want to represent the non-graphical object. Here you'll need to add an ivar to the MyPalette class in both Gorm and in your source code called, imageView. Once you've done this make the connection between the image view and it's ivar.<br />
<br />
Assuming that the class is called "NonUIObject", in finishInstantiate, you'll need to add the following line of code:<br />
<br />
-(void) finishInstantiate<br />
{<br />
id obj = [NonUIObject new];<br />
[self associateObject: obj type: IBObjectPboardType with: imageView];<br />
}<br />
<br />
This code has the effect of associating the non-ui object with the ui object you just added to represent it. When you drag and drop the element which prepresents the object to something, it will copy the object, not the ui element, to the destination.<br />
<br />
Congratulations, you now know how Palettes work.<br />
<br />
== Frequently Asked Questions ==<br />
<br />
See: [[Gorm FAQ]]<br />
<br />
== Implementation details ==<br />
<br />
This chapter describes some details about implementation of various features of Gorm. You should read it if you are a developer that would like to add custom objects, inspectors or would like to do other Gorm development.<br />
<br />
The IB documentation on how object selection is managed and how editors and<br />
inspectors are used is unclear ... so the author of Gorm gone his own way.<br />
<br />
When a document is loaded, the document object creates an editor attached<br />
to each top-level object in the user interface (NSMenu and NSWindow objects).<br />
These editors must be aware of their edited objects being clicked upon, and<br />
clicking on one of these should cause the corresponding editor to become the<br />
active editor.<br />
<br />
The ''active editor'' is responsible for handling selection of the edited object<br />
(and any objects below it in the object hierarchy). Upon change of selection,<br />
the editor is responsible for sending an IBSelectionChangedNotification with<br />
the selection owner (normally the editor itsself) as the notification owner.<br />
<br />
The main application watches for these notifications in order to keep track<br />
of who has the selection.<br />
<br />
=== Connections ===<br />
<br />
The connection API is the same as that for [[Interface Builder|IB]], but with the extension that the<br />
document object must implement [-windowAndRect:forObject:] to return the<br />
window in which the object is being displayed, and the rectangle enclosing<br />
the object (in window base coordinates).<br />
<br />
This information is needed by Gorm so that it can mark the connection.<br />
<br />
The editors mananging the drag-and-drop operation for a connection must call:<br />
<br />
[NSApp -displayConnectionBetween:and:]<br />
<br />
to tell Gorm to update its display. This method sets the values currently returned by:<br />
<br />
[NSApp -connectSource] and <br />
[NSApp -connectDestination]<br />
<br />
This section will cover some topics which won't be of general interest to most users. The details in this section pertain to the internal workings of Gorm.<br />
<br />
== Gorm file format ==<br />
<br />
The current Gorm file format is basically just a set of objects, encoded one after another in a continuous stream with some markers indicating when a new class starts or which class is encoded. <br />
<br />
=== The Name Table ===<br />
<br />
Each object in the .gorm file has a name assigned to it by the application. This allows Gorm to refer to the objects by a name once they are loaded rather than an address. Each name is associated with it's object in a dictionary which preserves the overall structure of the GUI which has been created. <br />
<br />
'''The Custom Class Table''' - This is only used when the user has associated a custom class with an existing instance in the gorm file. If the user has, for instance, added an NSWindow to the gorm, he/she can use the custom class inspector to select a subclass of NSWindow to change to. <br />
<br />
'''Connections Array''' - This array is used to form the connections after the .gorm file is loaded. The method [... establishConnection] is never called on either NSNibControlConnector or NSNibOutletConnector objects while in Gorm. This prevents the connections from having any effect while they are being edited in Gorm itself. Once they are loaded, the establishConnection method is called and the connections are made.<br />
<br />
=== Custom Class Encoding ===<br />
<br />
Custom objects are an interesting challenge in Gorm. By definition, custom classes are not known to Gorm, unless they are in a palette (covered elsewhere). For classes which are not in a palette instances of these classes in Gorm are encoding in one of three ways:<br />
<br />
* '''Proxy''' - This is a standin object which takes the place of the custom object. This is usually used when the superclass of the object is a non-graphical object, such as a controller. The init message is called on this object when it's unarchived.<br />
* '''Custom View''' - This is a standin view object similar to the one descrribed above, but it is a subclass of NSView. When this is used the initWithFrame: message is called on the view instance which is created (based on what view subclass the user selects)<br />
* '''Template''' - Probably the most interesting of the three. This is a standin class which uses an existing instance created in Gorm to build a custom subclass from. For instance when a window subclass is created, call it MyWindow, a template class called GSWindowTemplate is used to hold the NSWindow created in Gorm as well as the name of the subclass to be created when the class is unarchived outside of Gorm as well as some additional information. When the classes are unarchived in the running app, the designated initializer for that class will be invoked, except in the case of [[NSControl]] subclasses. See the Apple documentation for more information.<br />
<br />
All custom instances have awakeFromNib invoked on them when they are unarchived from the .gorm file. This allows the user to do whatever additional setup that needs to be done, such as setting attribute. Classes which are "known" are, of course, directly encoded into the .gorm file.<br />
<br />
== References ==<br />
<br />
[[ProjectCenter]] - GNUstep integrated development environment<br />
<br />
[[Category:Development]]<br />
<br />
== Links ==</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Writing_portable_code&diff=1079Writing portable code2005-08-29T14:35:09Z<p>Mguesdon: /* Porting from Cocoa to GNUstep */</p>
<hr />
<div>GNUstep opens up some fairly interesting opportunities to target a number of platforms with the same source code, for example porting Mac OS X Cocoa applications to Linux, the BSDs, other Unices and (ultimately) Windows without significant re-engineering effort or degraded end-user functionality. <br />
<br />
Some portability gotchas are listed below (please update when you run into a new one!):<br />
<br />
== Porting Applications ==<br />
<br />
You can generally convert NIB bundles from NeXTSTEP and OPENSTEP to<br />
GNUstep using the nib2gmodel tool. <br />
<br />
* nib2gmodel Something.nib Something.gmodel<br />
* Open the gmodel file in Gorm on GNUstep and save it as gorm<br />
<br />
The nib2gmodel step must be done on either an OPENSTEP or Cocoa platform.<br />
<br />
=== Porting from NeXTSTEP (NX*) to GNUstep ===<br />
<br />
For this you should have access to an old OPENSTEP installation, or find a friend who has one, otherwise you're simply better off just rewriting the application from scratch.<br />
<br />
There are some scripts which can be used to convert an application from NeXTSTEP to OPENSTEP located in:<br />
<br />
/NextDeveloper/OpenStepConversion/ConversionScripts<br />
<br />
They use a scripting language called "tops". I haven't been able, as yet, to locate a version of tops for Linux or any other operating system other than Mac OS X or OPENSTEP/Mach or NeXTSTEP.<br />
<br />
There are a few conversion applications which basically just use the tops scripts to do the conversion. They are actually two versions of the same program, but the second one doesn't run on NeXT, so here's both. These are:<br />
<br />
[ftp://next-ftp.peak.org/openstep/mach/apps/devtools/Conversion.0.5.NI.tar.gz]<br />
[ftp://next-ftp.peak.org/openstep/mach/apps/devtools/ConversionII.1.0.I.tar.gz]<br />
<br />
You should be able to point it at the project directory you wish to convert and start the conversion. The GUI is very straightforward.<br />
<br />
You can also run the tops scripts on a Mac simply by saying:<br />
<br />
tops -verbose -scriptfile {scriptfilename} {filestoconvert}<br />
<br />
All of the files are converted in place. You must run all of the tops scripts in the ConversionScripts directory against the application code. It is considerably simply to use the existing applications. Unfortunately these scripts do not exist on Mac OS X, otherwise porting the Conversion application might be useful.<br />
<br />
When you start the scripts, if you're running them on black hardware you should go get a cup of coffe and watch a movie with your wife or go code something else for a while. The conversion will take a good long while on an older machine. I haven't timed it on the Mac, though. Once this is done, there is still a long way to go. Read on.<br />
<br />
OPENSTEP4.2/Mach had a class called NSCStringText. This class was primarily for apps which were converted from NeXTSTEP to use as a stop-gap measure in OpenStep. This is one of the main reasons why it isn't in GNUstep. You will need to make sure that any classes modified by the scripts to use NSCStringText will use NSText and it's related classes as appropriate.<br />
<br />
OPENSTEP4.2/Mac also had some other extensions on the OpenStep standard such as NXStreams. You will also need to convert any and all instances of NXStream to use NSData instead in order to make your app work with GNUstep.<br />
<br />
If your app is fairly small, you shouldn't be in for a great shock, but if your app is heavily reliant on the old Text object from NeXTSTEP, you have a lot of work ahead. Other gaps which the scripts might leave are problems with NSUserDefaults which it can't fix on it's own.<br />
<br />
=== Porting from OPENSTEP (NS*) to GNUstep ===<br />
<br />
See the section on Porting from Cocoa. Basically, porting from OPENSTEP is the same with the exception of the "Don'ts" (as those are not available on OpenStep) and the "Stubling Blocks" sections.<br />
<br />
Unless otherwise noted here, follow the instructions there.<br />
<br />
=== Porting from GNUstep to Cocoa ===<br />
<br />
This should be an easy transition since GNUstep implements most of Cocoa, except for the very Apple specific classes such as the scripting extensions.<br />
<br />
Since Gorm does not yet save .nib files, you will need to create the interfaces using IB. Also there is a gorm reading/parsing framework for Cocoa in the works as well, so please stay tuned.<br />
<br />
Will will need to:<br />
<br />
* Make a Project Builder project for your app or<br />
* an Xcode project for your app<br />
<br />
Do the following:<br />
<br />
* Open Xcode.<br />
* Choose Application (if your project is an application)<br />
* Enter the name and location you wish the Project to reside at<br />
* Copy your files from your GNUstep application into the new project<br />
* Using the "Add Existing Files" option to add these file to your project.<br />
<br />
You should preserve your original directory structure if you want to distribute one package for both GNUstep and Cocoa.<br />
<br />
=== Porting from Cocoa to GNUstep ===<br />
<br />
Porting from Cocoa to GNUstep has different aspects.<br />
<br />
First there is the compatibility of the basic Foundation Kit and Application Kit. We support a lot of classes, but not all of them and the same is true for specific methods, Specifically newly introduced classes and methods may still be missing as GNUstep started out aiming at OpenStep compatibility.<br />
<br />
Second you have all the additional frameworks and libraries programmers on Mac OS X take for granted, for some of them free replacements exists, for most they are still missing.<br />
<br />
Mac OS X developers should try and avoid CoreFoundation as this will complicate your dependency situation on non-Mac hosts, even if that part of CoreFoundation has actually been ported.<br />
<br />
GNUstep Base and the FoundationKit offer many parts of the CoreFoundation functionality in a natural [[Objective-C]] manner.<br />
<br />
==== The porting itself ====<br />
<br />
short overview:<br />
* write a makefile <br />
* convert your NIB files to gmodel<br />
* provide an Info.plist.<br />
<br />
detailed instructions:<br />
# you need to write a new GNUstep make file for the project (very easy, still there is currently no automatic way to do so) <br />
# you need to convert the NIB files to GNUstep format. At some point in time GORM will be able to read NIB files, but currently you need to use the gmodel intermediate format for this and for this the above mentioned tools are used.<br />
<br />
==== Don'ts ====<br />
<br />
Don't use anything we do not provide:<br />
<br />
* don't use CoreFoundation<br />
* don't use KeyChain<br />
* don't use Carbon<br />
* don't use Quartz<br />
* don't use QuickTime<br />
<br />
gcc mainline currently doesn't support ObjC++ although it is already in the works somewhat (expected for gcc 4.1). that means:<br />
<br />
* don't use WebKit (currently)<br />
<br />
gcc mainline also does not support altivec, this is an apple specific extentsion, that means:<br />
* don't use altivec features or the vecLib.framework (a collection of functions for vector manipulation).<br />
<br />
== Stumbling Blocks ==<br />
<br />
* Apple's Cocoa.h<br />
<br />
it is there to enable pre-compiled headers and speed up compile time thusly. Anyway, it contains just two lines:<br />
<br />
#import <Foundation/Foundation.h><br />
#import <AppKit/AppKit.h><br />
<br />
So you can easily work around this by providing your own or replace your include of <Cocoa/Cocoa.h> with just the above, which will also work on OS-X.<br />
<br />
* When you need to distinguish between Cocoa and GNUstep, you may use the following<br />
<br />
#ifdef GNUSTEP<br />
''/* GNUstep code goes here ... */''<br />
#else<br />
''/* OS-X Cocoa native code goes here ... */''<br />
#endif<br />
<br />
<br />
=== Porting the .nib files ===<br />
<br />
First get [http://freshmeat.net/projects/nib2gmodel/ nib2gmodel], follow the included instructions to build and install it. Once that's done you're ready to begin:<br />
<br />
* Run the nib2gmodel program on your nib like so:<br />
<br />
nib2gmodel mygui.nib mygui.gmodel<br />
<br />
This should create the .gmodel as a plist. I recommend that you convert the gmodel to a "normal" plist instead of an XML plist. You can do that by doing this on OS X:<br />
<br />
pl < mygui.gmodel -output mygui.ser<br />
pl > mygui.gmodel -input mygui.ser<br />
rm mygui.ser<br />
<br />
* Now you can either use the gmodel as it is, or you can convert it to a .gorm file.<br />
<br />
==== Gmodel to .gorm conversion ====<br />
<br />
NOTE: Conversion from gmodel to .gorm is experimental and will probably remain so for a while. It currently works in the majority of cases, but there are still improvements which need to be made.<br />
<br />
Conversion to a .gorm file is relatively straightforward:<br />
<br />
* Start Gorm.app.<br />
* Choose Gorm->Document->Open and find the gmodel you wish to load.<br />
* Gorm will prompt you to either define the superclass for classes it doesn't know about or to parse the headers. <br />
<br />
After you've defined all of the unknown classes, Gorm should complete the conversion. Once this is done you should save the result to make sure you don't loose your work.<br />
<br />
''' ''FIXME: add following:'' '''<br />
* how to convert Xcode project to GNUstep project (creating a GNUstep [http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/index.html Makefile] or [[ProjectCenter]])<br />
<br />
== Notes ==<br />
<br />
=== Do not rely on tools available in development environment ===<br />
<br />
All the world is not Linux or FreeBSD or Windows. System constants may be different on different platforms. Paths to command-line tools, the parameters they accept and locations of temporary directories may be different to what you are used to on your platform.<br />
<br />
* [[Foundation|GNUstep Base]] and the [[Foundation|FoundationKit]] offer some of this functionality "for free".<br />
* Try not to hard code paths and so on into your code, use macros (not recommended), or even better an abstraction mechanism.<br />
* Avoid hard-coding system constants, or platform-specific ones where Posix or commonly-accepted ones exist (and we're not talking about glibc here :-)<br />
* Try to avoid advanced features of the linker, such as weak symbols, which may not be present on non-ELF systems. While this will work perfectly on most systems, it is not portable to all systems, most notably Windows.<br />
<br />
[[Category:Project procedures]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepIsNotWindowMaker&diff=1954GNUstepIsNotWindowMaker2005-08-29T14:34:03Z<p>Mguesdon: </p>
<hr />
<div>=== GNUstep is NOT [[Window Maker]] ===<br />
In order to prevent misinformation ...<br />
<br />
=== GNUstep is NOT a window manager ===<br />
<br />
Why is this confusion floating around? [[Window Maker]] is the most often-used NeXT-looking application on a non-NeXT system. [[Window Maker]] also uses a derivation of the GNUstep logo. [[Window Maker]] is the official GNUstep window manager, but GNUstep applications also work with any window manager, although you're most likely, currently, to have a more cohesive desktop experience if you use the two in conjunction.<br />
<br />
=== What is GNUstep ? ===<br />
<br />
[[GNUstep]] is an advanced, cross-platform, object oriented environment composed of frameworks, tools and servers (daemons). It is very close to the [http://developer.apple.com/cocoa/ Cocoa] frameworks from [http://www.apple.com Apple] and tries to maintain compatibility with Cocoa wherever it is desired and possible. The roots of the GNUstep application interface are same as the roots of Cocoa: Ne XT and [[OpenStep]].<br />
<br />
=== Relation to [[Window Maker]] ===<br />
<br />
[[Window Maker]] is a window manager, not a workspace manager nor a file browser. It is nothing more.<br />
[[Window Maker]] and GNUstep share almost no libraries or functionality. [[Window Maker]] is written in C, and GNUstep is written in [[Objective-C]]. [[Window Maker]] does make certain things easier for GNUstep, but it is not GNUstep itself, although it is a part of the project.<br />
<br />
=== The Importance of this difference ===<br />
<br />
In many people's minds the environment and the frameworks used to create programs merges. [[Window Maker]] can be used with QT or GNOME apps, just as easily as it can be used with GNUstep. Similarly GNUstep applications can run using KWM (KDE's preferred Window Manager) or Enlightenment (GNOME's old, old preferred Window Manager -- since then they went through Sawfish and now Metacity). This misconception can make one lose sight of the powerful programming frameworks underneath.<br />
<br />
=== Please note ===<br />
<br />
[[Window Maker]] is an excellent window manager and none of the preceeding should be construed to imply otherwise.</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Foundation&diff=1958Foundation2005-08-29T14:32:51Z<p>Mguesdon: </p>
<hr />
<div>The GNUstep base library 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 [[NSStrng|strings]] and [[NSArray|arrays]], [[NSDate|dates]] and times, [[NSConnection|distributed objects]], URLs and file systems (to name but a few).<br />
<br />
Features:<br />
<br />
* [[Strings]]<br />
* [[Collections]] (arrays, sets, dictionaries) and enumerators<br />
* [[File management]]<br />
* [[Archiving|object archiving]]<br />
* advanced calendar [[Date|date]] manipulation<br />
* [[Distributed Objects]] and inter-process communication<br />
* [[URL]] handling<br />
* [[Notifications]] (and distributed notifications)<br />
* easy [[Threading|multi-threading]]<br />
* [[Timer]]s<br />
* [[Lock]]s<br />
* [[Exception handling]]<br />
<br />
== Classes ==<br />
<br />
[[NSArray]]<br />
<br />
[[Category:Frameworks]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=OpenStep&diff=999OpenStep2005-08-29T14:32:11Z<p>Mguesdon: </p>
<hr />
<div>OpenStep is an Application Programming Interface (API) for creating applications using the [[Objective-C]] language. It was published by NeXT Computer Inc. in 1994.<br />
<br />
OpenStep consists of three parts:<br />
* the [[Foundation]]Kit, a library of non-graphical objects;<br />
* the [[AppKit]], a library of objects useful in creating graphical applications;<br />
* and [[Display Postscript]], an interface for drawing to the screen using the PostScript graphics language.<br />
<br />
The OpenStep specification is available in a couple of different formats from [http://www.gnustep.org/resources/resources.html].<br />
<br />
Commercial successor of the [[OpenStep]] is Apple's [[Cocoa]].</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepWeb&diff=1973GNUstepWeb2005-08-29T14:31:27Z<p>Mguesdon: </p>
<hr />
<div>GNUstepWeb is a library which was designed to be compatible with [[WebObjects]] 4.x (developed by NeXT (now Apple) Inc.).<br />
<br />
This library is a logic extension of the [[GNUstep]] project. I hope it can help [[Objective-C]], [[OpenStep]] and [[WebObjects]] to become standards.<br />
<br />
See: http://www.gnustepweb.org/<br />
<br />
[[Category:Frameworks]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepWeb&diff=926GNUstepWeb2005-08-29T14:30:22Z<p>Mguesdon: </p>
<hr />
<div>GNUstepWeb is a library which was designed to be compatible with WebObjects 4.x (developed by NeXT (now Apple) Inc.).<br />
<br />
This library is a logic extension of the GNUstep project. I hope it can help [[Objective-C]], OpenStep and WebObject to become standards.<br />
<br />
See: http://www.gnustepweb.org/<br />
<br />
[[Category:Frameworks]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Smalltalk&diff=1948Smalltalk2005-08-29T14:29:12Z<p>Mguesdon: </p>
<hr />
<div>Smalltalk is pure object oriented language with environment. In the context of the GNUstep, the Smalltalk is a ''[[Scripting language bundle]]'' for the [[StepTalk]] scripting framework.<br />
<br />
Note that the language bundle offers Smalltalk language only, that sits on top of the [[Objective-C]] object environment. Therefore, some classes and mechanisms known from Smalltalk are not (yet) available.<br />
<br />
== The Language ==<br />
<br />
The language has very straightforward and easy to learn syntax. It is said, that the syntax was inspired somehow by the english grammar.<br />
<br />
=== Basics ===<br />
<br />
The language is based on sending messages to objects, like:<br />
<br />
anObject message<br />
<br />
Here are few examples that you should try, for example by using the [[StepTalk shell]].<br />
For example to see current date, just send message ''date'' to the object ''NSDate'':<br />
<br />
NSDate date<br />
<br />
To assign a result to a variable:<br />
<br />
date := NSDate date<br />
<br />
or<br />
<br />
a := 10.<br />
b := 20.<br />
result := a + b.<br />
<br />
=== Literals and basic operations ===<br />
<br />
In a script you should have literal objects: strings, arrays, numbers and selectors.<br />
<br />
{| border=1<br />
|+<br />
| Strings || 'This is a string' 'This is another \'String\' with apostrophes'<br />
|+<br />
| Array || #(1 2 3) #('one' 'two' 'three')<br />
|+<br />
| Numbers || 1 2 0.1 -1.1e10<br />
|}<br />
<br />
To join two strings use , (comma), like:<br />
<br />
'This is ', 'a string'<br />
<br />
To get an object from an array (indexed from 0):<br />
<br />
#('one' 'two' 'three') @ 1<br />
<br />
To do computations with numbers:<br />
<br />
1 + 1<br />
<br />
Important note: Smalltalk does not take into account operator priority, so you have to enclose an expression into parentheses. Try:<br />
<br />
1 + 2 * 3<br />
1 + (2 * 3)<br />
<br />
You should use operators: + - * /<br />
<br />
=== Blocks ===<br />
<br />
Instead of explaining what blocks enclosed by [ ... ] are, try following examples, line by line, and you will get the idea:<br />
<br />
( 1 = 1 ) ifTrue: [ Transcript showLine: 'Yes']<br />
( 2 < 1 ) ifFalse: [ Transcript showLine: 'No']<br />
( 1 >= 4 ) ifTrue: [ Transcript showLine: 'Yes'] ifFalse: [ Transcript showLine: 'No']<br />
<br />
=== Cycles ===<br />
<br />
Cycles are created using blocks:<br />
<br />
1 to: 10 do: [ :i | Transcript showLine: (i description) ]<br />
0 to: 100 step: 10 do: [ :i | Transcript showLine: (i description) ]<br />
<br />
Other possibilities are:<br />
<br />
conditionBlock whileTrue: toDoBlock.<br />
conditionBlock whileFalse: toDoBlock.<br />
<br />
like:<br />
<br />
a := 0 . [ a < 10 ] whileTrue: [ a := a + 1 . Transcript showLine: (a description) ]<br />
<br />
=== Array iteration ===<br />
<br />
array := #('one' 'two' 'three').<br />
array do: [ :item | Transcript showLine: item ]<br />
array select: [ :item | item hasPrefix:'t' ]<br />
<br />
{| border=1<br />
|+<br />
| do: || Evaluate block for each object in array and return last evaluated expression<br />
|+<br />
| select: || Create new array which will contain those objects from receiver, for which value of block was true<br />
|+<br />
| reject: || Create new array which will contain those objects from receiver, for which value of block was false<br />
|+<br />
| collect:|| Create new array from block return values.<br />
|+<br />
| detect: || Return first object for which block evaluation result is true. Othervise return nil.<br />
|}<br />
<br />
== More information and examples ==<br />
<br />
More examples are included in the StepTalk source distribution in Examples directory, please refer to that place.<br />
<br />
For more information, please refer to the Documentation directory. For language reference see Smalltalk.txt file.<br />
<br />
[[Category:Scripting]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=DevelopmentKit&diff=1932DevelopmentKit2005-08-29T14:28:43Z<p>Mguesdon: </p>
<hr />
<div>Develompent Kit Framework is [[Objective-C]]/[[GNUstep]] framework for generating Objective C code based projects and sources from applications.<br />
<br />
Features:<br />
* class compositing<br />
* [[Objective-C]] source parsing and transforming into development objects (classes, methods, variables,...)<br />
* source file generation using templates<br />
* project building<br />
<br />
Project Page: https://savannah.nongnu.org/projects/develkit/<br />
<br />
[http://savannah.nongnu.org/cgi-bin/viewcvs/develkit/ Browse CVS Tree]<br />
<br />
Author: [[user:Stefan Urbanek|Stefan Urbanek]]<br />
<br />
== Tools ==<br />
<br />
=== dkautogen ===<br />
Autogenerate [[Objective-C]] Interface and Implementation methods<br />
<br />
Usage:<br />
dkautogen file1.h file2.h ...<br />
<br />
Type 'dkautogen help' for more information.<br />
<br />
To each .h and corresponding .m file a category DKGenerated is appended. If there is already such category, then it is replaced.<br />
<br />
Instance variable keywords<br />
<br />
hidden - do not generate accessor methods<br />
exposed - expose accessor methods<br />
retained - object is retained<br />
notretained - object is NOT retained (weak reference)<br />
readonly - instance variable is read only (setter is not generated)<br />
mutable - instance variable is mutable (setter is generated despite "readonly" class default)<br />
notarchived - ignore in archiving<br />
object - instance variable is an object (see below)<br />
customaccess - do not generate implementation of accessor methods, generate interface only<br />
<br />
Class keywords (defaults for all instance variables)<br />
<br />
hidden - all ivars are hidden<br />
exposed - all ivars are exposed (accessors are generated)<br />
retained - all objects are retained<br />
notretained - objects are NOT retained<br />
readonly - all instance variable are read only<br />
objects - treat all unknown types as objects<br />
customarchive - do not generate archiving methods<br />
nosuperarchive - do not call archiving in superclass<br />
customdealloc - do not generate -dealloc method<br />
<br />
'''Known types'''<br />
<br />
All standard C types including [[NSPoint]], [[NSSize]], [[NSRect]] and [[NSRange]] are treated as non-objects. By default only id and Class types are treated as objects.<br />
<br />
Generated methods by default: accessors (getter and setter), dealloc methon, initWithCoder:, and encodeWithCoder<br />
<br />
'''How to use'''<br />
<br />
Attributes are written in same comments used for auto-documentation. They are read from comments after the LAST pipe '|' character in the comment and they should be separated by spaces. Example:<br />
<br />
NSString *name; /** Object name | object readonly retained */<br />
<br />
Class defaults are written immediately before @interface:<br />
<br />
/** This is my class | nosuperarchive retained objects */<br />
@interface MyClass : NSObject<br />
<br />
Preferences (also usable as switches on commandline with '-' prefix):<br />
interfaceTemplate - path to .h file template<br />
implementationTemplate - path to .m file template<br />
beginTag - tag used to mark beginning of generated code<br />
endTag - tag used to mark end of generated code<br />
<br />
Example:<br />
dkautogen -implementationTemplate MyTemplate.m SomeClass.h<br />
<br />
== Classes ==<br />
<br />
* DKBuildMessage<br />
* DKClass<br />
* DKFramework<br />
* DKFrameworkManager<br />
* DKMethod<br />
* DKObjectiveCParser<br />
* DKProjectBuilder<br />
* DKProject<br />
* DKSourceGenerator<br />
* DKTemplateMerger<br />
* DKVariable<br />
<br />
DevelKit reuses class [[AGSParser]] from [[autogsdoc]].<br />
<br />
<br />
[[Category:Frameworks]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Glossary&diff=935Glossary2005-08-29T14:20:37Z<p>Mguesdon: /* O */</p>
<hr />
<div>''Please add mainly GNUstep related terms here.''<br />
<br />
== A ==<br />
* [[AppKit]]<br />
* [[Application]]<br />
<br />
== B ==<br />
* [[Back]]<br />
* [[Bundle]]<br />
* [[Bundle|Bundle, main]]<br />
<br />
== C ==<br />
* [[Category]]<br />
* [[Class]]<br />
* [[Controller]]<br />
<br />
== D ==<br />
* [[Delegate]]<br />
* [[DPS]]<br />
* [[Drag and Drop]]<br />
<br />
== E ==<br />
<br />
== F ==<br />
* First responder - see [[Responder]]<br />
* [[Foundation]]<br />
* [[Framework]]<br />
<br />
== G ==<br />
* [[GUI]]<br />
* [[GNUstep]]<br />
<br />
== H ==<br />
<br />
== I ==<br />
* [[Instance variable]]<br />
* [[Invocation]]<br />
<br />
== J ==<br />
<br />
== K ==<br />
* [[Key Value Coding]]<br />
* [[Key Value Observing]]<br />
* Key window - see [[Window]]<br />
* KVC - see [[Key Value Coding]]<br />
<br />
== L ==<br />
<br />
== M ==<br />
* Main window - see [[Window]]<br />
* [[Makefile]]<br />
* [[MVC]]<br />
<br />
== N ==<br />
* NeXTSTEP<br />
<br />
== O ==<br />
* [[Objective-C]]<br />
* [[OpenStep]] - API standard<br />
* [[OPENSTEP]] - operating system<br />
* Outlet - see FIXME<br />
<br />
== P ==<br />
* [[Protocol]]<br />
<br />
== Q ==<br />
<br />
== R ==<br />
* [[Responder]]<br />
* Responder, first - see [[Responder]]<br />
* Responder chain - see [[Responder]]<br />
<br />
== S ==<br />
* [[Scripting]]<br />
* [[Service]]<br />
* [[Application Services|Services, application]]<br />
<br />
== T ==<br />
* [[Target-Action]]<br />
* [[Tool]]<br />
<br />
== U ==<br />
<br />
== V ==<br />
* [[View]]<br />
<br />
== W ==<br />
* [[Window]], ~ key, ~ main<br />
<br />
== X ==<br />
<br />
== Y ==<br />
<br />
== Z ==</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Objective-C&diff=1167Objective-C2005-08-29T14:10:57Z<p>Mguesdon: </p>
<hr />
<div>Objective-C Language<br />
<br />
Some resources:<br />
# [http://www.objc.info Objective-C portal]<br />
# Apple Site: [http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/ The Objective-C Programming Language]<br />
# [http://www.toodarkpark.org/computers/objc/ Object-Oriented Programming and the Objective-C Language]<br />
# [http://www.faqs.org/faqs/computer-lang/Objective-C/faq/ Objective-C FAQ]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=FAQ&diff=1122FAQ2005-08-29T14:05:14Z<p>Mguesdon: </p>
<hr />
<div>* [http://www.gnustep.org/resources/documentation/User/GNUstep/userfaq_toc.html User FAQ]<br />
* [http://www.gnustep.org/resources/documentation/User/GNUstep/faq_toc.html Developer FAQ]<br />
* [[GNUstepIsNotWindowMaker]]<br />
<br />
<br />
Here are few FAQ from the old wiki :<br />
<br />
: <MrBIOS-TS> WELCOME TO GNUSTEP! Don't ever ask these questions. Before you ask them, here are the answers!</tongue-in-cheek><br />
<br />
:'''Q.''' Why don't you just have Gorm output Renaissance files?<br/><br />
:'''A.''' Philosophical and architectural incompatibilities.<br />
<br />
:'''Q.''' Is there a way to install GNUstep on Mac OS X? Perhaps some howto?<br/><br />
:'''Q.''' Is there any way to use gnustep-make and gnustep-base without using openapp/opentool?<br/><br />
:'''Q.''' Can GNUstep help with porting applications from MacOS-X? Is there any HOWTO on that? See for example Tamsys http://sourceforge.net/projects/tamsys. How difficult it should be to port it to Linux and GNUstep?<br/><br />
:'''A.''' Somehow relevant may be discussion on http://groups.google.com/groups?th=f8a07de1a707dbeb. Unfortunately this link is broken now. Dredge around in the google discussion group, I guess. I couldn't find anything helpful.<br />
<br />
:'''Q.''' Can I deploy my GNUstep application without requiring people to install GNUstep?<br />
:'''A.''' No. Compare it to running Java applications without people requiring to install Java runtime environment.<br />
<br />
:'''Q.''' How can I get more information on Objective-C ?<br />
:'''A.''' Here: [[Objective-C]]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=FAQ&diff=921FAQ2005-08-29T14:03:41Z<p>Mguesdon: </p>
<hr />
<div>* [http://www.gnustep.org/resources/documentation/User/GNUstep/userfaq_toc.html User FAQ]<br />
* [http://www.gnustep.org/resources/documentation/User/GNUstep/faq_toc.html Developer FAQ]<br />
* [[GNUstepIsNotWindowMaker]]<br />
<br />
<br />
Here are few FAQ from the old wiki :<br />
<br />
: <MrBIOS-TS> WELCOME TO GNUSTEP! Don't ever ask these questions. Before you ask them, here are the answers!</tongue-in-cheek><br />
<br />
:'''Q.''' Why don't you just have Gorm output Renaissance files?<br/><br />
:'''A.''' Philosophical and architectural incompatibilities.<br />
<br />
:'''Q.''' Is there a way to install GNUstep on Mac OS X? Perhaps some howto?<br/><br />
:'''Q.''' Is there any way to use gnustep-make and gnustep-base without using openapp/opentool?<br/><br />
:'''Q.''' Can GNUstep help with porting applications from MacOS-X? Is there any HOWTO on that? See for example Tamsys http://sourceforge.net/projects/tamsys. How difficult it should be to port it to Linux and GNUstep?<br/><br />
:'''A.''' Somehow relevant may be discussion on http://groups.google.com/groups?th=f8a07de1a707dbeb. Unfortunately this link is broken now. Dredge around in the google discussion group, I guess. I couldn't find anything helpful.<br />
<br />
:'''Q.''' Can I deploy my GNUstep application without requiring people to install GNUstep?<br />
:'''A.''' No. Compare it to running Java applications without people requiring to install Java runtime environment.<br />
<br />
:'''Q.''' How can I get more information on Objective-C ?<br />
:'''A.''' [Objective-C Here]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=376GNUstep in production2005-02-20T20:06:37Z<p>Mguesdon: </p>
<hr />
<div>''Note: Please leave a short note about how is the company related to GNUstep.''<br />
<br />
== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept]<br>is working mainly on [http://www.gnustepweb.org GNUstepWeb] and gdl2 for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom]<br>uses [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and gdl2 to run its shop since may 2003.<br />
* [http://www.seat-1.com seat-1 Software GmbH ], business software for small to medium-sized production, trading and service companies. The software product IntarS is powered by GNUstepWeb on GNU based operating systems.<br />
* Orillion<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=248GNUstep in production2005-02-17T23:57:24Z<p>Mguesdon: /* Companies which use and support GNUstep */</p>
<hr />
<div>== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept]<br>is working mainly on [http://www.gnustepweb.org GNUstepWeb] and gdl2 for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom<br>use [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and gdl2 to run its shop [http://www.cyberdvdfilms.com CyberDVDFilms] since may 2003.<br />
* Orillion<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=226GNUstep in production2005-02-17T23:56:56Z<p>Mguesdon: /* Companies which use and support GNUstep */</p>
<hr />
<div>== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept]<br>is working mainly on [http://www.gnustepweb.org GNUstepWeb] and gdl2 for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom<br><br />
use [http://www.eCommStep.com eCommStep], an eCommerce engine based on [http://www.gnustep.org GNUstep], [http://www.gnustepweb.org GNUstepWeb] and gdl2 to run its shop [http://www.cyberdvdfilms.com CyberDVDFilms] since may 2003.<br />
* Orillion<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=225GNUstep in production2005-02-17T23:52:27Z<p>Mguesdon: /* Corporations & Companies actively developing for GNUstep */</p>
<hr />
<div>== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept]<br>is working mainly on [http://www.gnustepweb.org GNUstepWeb] and gdl2 for it's eCommerce engine: [http://www.eCommStep.com eCommStep]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom/CyberDVDFilms]<br />
* Orillion<br />
* [http://www.theinternetco.net/ The Internet Company]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Help:Editing&diff=1941Help:Editing2005-02-17T23:49:39Z<p>Mguesdon: </p>
<hr />
<div>See: http://meta.wikimedia.org/wiki/Help:Editing</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=User:Mguesdon&diff=1940User:Mguesdon2005-02-17T11:35:45Z<p>Mguesdon: </p>
<hr />
<div>== Manuel Guesdon ==<br />
<br />
<br />
'''Home''': [http://www.orange-concept.com Orange Concept]<br />
<br />
'''Email''': mguesdon [at] orange-concept.com<br />
<br />
<br />
'''GNUstep Stuff''': [http://www.gnustepweb.org GNUstepWeb] and gdl2</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=202GNUstep in production2005-02-17T11:30:06Z<p>Mguesdon: /* Corporations & Companies actively developing for GNUstep */</p>
<hr />
<div>== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.orange-concept.com/ Orange Concept]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom/CyberDVDFilms]<br />
* Orillion</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstep_in_production&diff=190GNUstep in production2005-02-17T11:29:44Z<p>Mguesdon: /* Companies which use and support GNUstep */</p>
<hr />
<div>== Corporations & Companies actively developing for GNUstep ==<br />
<br />
* [http://www.sbuilders.com/ Software Builders]<br />
* [http://www.orange-concept.com/ Orange Concept]<br />
* [http://www.brainstorm.co.uk/ Brainstorm Computer Solutions]<br />
* [http://www.turbocat.de/ Turbocat's Development]<br />
<br />
<br />
== Companies which use and support GNUstep ==<br />
<br />
* [http://www.cyberdvdfilms.com Microcom/CyberDVDFilms]<br />
* Orillion</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=GNUstepWiki:Bureaucrat_log&diff=1897GNUstepWiki:Bureaucrat log2005-02-06T01:41:42Z<p>Mguesdon: Rights for user "Aperez" set "+sysop +bureaucrat"</p>
<hr />
<div><ul><li>01:41, 6 Feb 2005 [[User:Mguesdon|Mguesdon]] Rights for user "Aperez" set "+sysop +bureaucrat"</li><br />
<br />
</ul></div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Main_Page&diff=4Main Page2005-02-05T20:38:51Z<p>Mguesdon: </p>
<hr />
<div>[http://meta.wikimedia.org/wiki/MediaWiki_development Wiki Dev Doc]<br />
<br />
[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide User'sGuide]<br />
<br />
[http://meta.wikimedia.org/wiki/MediaWiki_FAQ FAQ]<br />
<br />
[http://wikipedia.sourceforge.net WikiPedia]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Main_Page&diff=3Main Page2005-02-05T20:37:25Z<p>Mguesdon: </p>
<hr />
<div>[http://meta.wikimedia.org/wiki/MediaWiki_development Wiki Dev Doc]<br />
[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide User'sGuide]<br />
[http://wikipedia.sourceforge.net WikiPedia]</div>Mguesdonhttps://mediawiki.gnustep.org/index.php?title=Main_Page&diff=2Main Page2005-02-05T20:33:00Z<p>Mguesdon: </p>
<hr />
<div>[http://meta.wikimedia.org/wiki/MediaWiki_development WikiDoc]</div>Mguesdon