<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://mediawiki.gnustep.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Pinkwerks</id>
	<title>GNUstepWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://mediawiki.gnustep.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Pinkwerks"/>
	<link rel="alternate" type="text/html" href="https://mediawiki.gnustep.org/index.php/Special:Contributions/Pinkwerks"/>
	<updated>2026-04-22T16:30:51Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.7</generator>
	<entry>
		<id>https://mediawiki.gnustep.org/index.php?title=ProjectCenter&amp;diff=2882</id>
		<title>ProjectCenter</title>
		<link rel="alternate" type="text/html" href="https://mediawiki.gnustep.org/index.php?title=ProjectCenter&amp;diff=2882"/>
		<updated>2005-11-22T21:05:13Z</updated>

		<summary type="html">&lt;p&gt;Pinkwerks: Added FAQ link.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;ProjectCenter is a clone of the ProjectBuilder application under OPENSTEP4.2/Mach.  It's main function is to manage the files which comprise the application, and manage any and all associated resources.   (This is a stub page, if you have more detail to add, please do so.)&lt;br /&gt;
&lt;br /&gt;
*[[ProjectCenter FAQ]]&lt;/div&gt;</summary>
		<author><name>Pinkwerks</name></author>
	</entry>
	<entry>
		<id>https://mediawiki.gnustep.org/index.php?title=ProjectCenter_FAQ&amp;diff=2881</id>
		<title>ProjectCenter FAQ</title>
		<link rel="alternate" type="text/html" href="https://mediawiki.gnustep.org/index.php?title=ProjectCenter_FAQ&amp;diff=2881"/>
		<updated>2005-11-22T21:04:06Z</updated>

		<summary type="html">&lt;p&gt;Pinkwerks: Started FAQ.  Created custom text editor section.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Frequently Asked Questions =&lt;br /&gt;
&lt;br /&gt;
== PC? ==&lt;br /&gt;
PC is an abbreviation for [[ProjectCenter]].&lt;br /&gt;
&lt;br /&gt;
== Using custom text editors with ProjectCenter? ==&lt;br /&gt;
Why a custom text editor?  Let's face it, PC's built-in text editor is lacking features many programmers have come to expect in an IDE such as 'syntax highlighting' and 'auto indentation'.  After all, PC's focus is to manage a project and not edit source files.  The basic idea here is one chooses a custom editor to work on the files.&lt;br /&gt;
&lt;br /&gt;
=== General Strategy ===&lt;br /&gt;
First one must tell PC which command invokes the custom text editor.   Navigate to the ''PC &amp;gt; Info &amp;gt; Preferences'' Menu.  When the window appears, change the pulldown to ''Miscellaneous''.   Their you'll find the ''Editor'' preference, which by default is set to 'ProjectCenter'.  Change this value to reflect the location of a custom editor.&lt;br /&gt;
&lt;br /&gt;
=== Emacs ===&lt;br /&gt;
In short, tell emacs to start a server on startup that allows it to share editing contexts.&lt;br /&gt;
*First add the line '(server-start)' to your ~/.emacs file.  You may skip this but you'll have to manually issue this command everytime you start emacs.  Below is an example of how to do this using the shell.&lt;br /&gt;
 echo '(server-start)' &amp;gt;&amp;gt; ~/.emacs&lt;br /&gt;
*Launch Emacs.  Checking the *messages* buffer should show that the server has started.&lt;br /&gt;
*Set the ''Editor Preference'' in PC to the location of your `emacsclient` (see General Strategy above) and tell it to not wait around for the buffer to exit.&lt;br /&gt;
 /usr/bin/emacsclient -n&lt;br /&gt;
*Click a file in PC and it should appear in the buffer in your emacs client.&lt;br /&gt;
&lt;br /&gt;
Again, make sure that emacs is running before you open the file in PC.  `emacsclient` doesn't have the ability to create a new emacs server, only connect to an existing one.  It's done this way versus using plain old `emacs` to prevent multiple instances of 'foo.h' being open.&lt;br /&gt;
&lt;br /&gt;
=== Nano ===&lt;br /&gt;
Possible values for ''Editor'' in the ''Preferences'' window.  Be sure to prefix with the location of `nc`.&lt;br /&gt;
 nc  --noask&lt;br /&gt;
On Debian :&lt;br /&gt;
 nedit-nc --noask&lt;/div&gt;</summary>
		<author><name>Pinkwerks</name></author>
	</entry>
	<entry>
		<id>https://mediawiki.gnustep.org/index.php?title=Development_tools&amp;diff=2880</id>
		<title>Development tools</title>
		<link rel="alternate" type="text/html" href="https://mediawiki.gnustep.org/index.php?title=Development_tools&amp;diff=2880"/>
		<updated>2005-11-22T19:50:45Z</updated>

		<summary type="html">&lt;p&gt;Pinkwerks: Added FAQ link.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;More abou development tools: http://www.gnustep.org/experience/DeveloperTools.html&lt;br /&gt;
&lt;br /&gt;
== Gorm - Graphical Object Relationship Modeller ==&lt;br /&gt;
&lt;br /&gt;
Gorm stands for &amp;quot;Graphical Object Relationship Modeller&amp;quot; and is GNUstep's easy-to-use interface designer. &lt;br /&gt;
&lt;br /&gt;
With Gorm designing tough and complex graphical interfaces for your applications can be done easily and quickl, using drag &amp;amp; drop, powerful inspectors and teamwork with ProjectCenter.&lt;br /&gt;
&lt;br /&gt;
Gorm allows developers to quickly create and edit graphical application interfaces using a whole lot of GUI elements: windows, menus, buttons, labels, sliders, tables, textfields, browsers, images, altert panels and more. Custom palettes can be dynamically loaded to add additional elements or functionality.&lt;br /&gt;
&lt;br /&gt;
After creating the interface, objects can be linked using mouse operations. Also Gorm features interactive testing of interfaces.&lt;br /&gt;
&lt;br /&gt;
Please see the following wiki sections to learn tips on how to effectively utilize Gorm:&lt;br /&gt;
&lt;br /&gt;
* [[Gorm Manual]]&lt;br /&gt;
* [[Gorm FAQ]]&lt;br /&gt;
* [[Gorm Installation On Windows]]&lt;br /&gt;
&lt;br /&gt;
Also see the following external links:&lt;br /&gt;
&lt;br /&gt;
* ''' [http://www.gnustep.org/experience/Gorm.html Official Gorm page] '''&lt;br /&gt;
&lt;br /&gt;
* '''[http://packages.debian.org/cgi-bin/search_packages.pl?keywords=gorm&amp;amp;searchon=names&amp;amp;version=all&amp;amp;exact=1&amp;amp;release=all  Debian Offical Release]'''&lt;br /&gt;
&lt;br /&gt;
* '''[http://www.freshports.org/devel/gorm FreeBSD Ports]'''&lt;br /&gt;
&lt;br /&gt;
== Project Center ==&lt;br /&gt;
''' [http://www.gnustep.org/experience/ProjectCenter.html Project Center] '''&lt;br /&gt;
&lt;br /&gt;
ProjectCenter is GNUstep's integrated developement environment (IDE). It is based in part on NeXT's original Project Builder. It assists you in starting new projects and lets you manage your project files using a intuitive and well ordered graphical user interface.&lt;br /&gt;
&lt;br /&gt;
* [[ProjectCenter FAQ]]&lt;br /&gt;
&lt;br /&gt;
== Other tools ==&lt;br /&gt;
&lt;br /&gt;
=== Unit Testing ===&lt;br /&gt;
&lt;br /&gt;
GNUstep is blessed with a number of unit test frameworks: &lt;br /&gt;
&lt;br /&gt;
* Traditionally, it has provided a [http://www.gnustep.org/resources/documentation/testdoc_toc.html testing environment] based around Guile, an implementation of Scheme that has been blessed as the preferred GNU scripting language. It has been hard to convince Objective-C programmers to write tests in this language, and the utility of the package has not lived up to expectations.&lt;br /&gt;
&lt;br /&gt;
* GNUstep now also contains a unit testing framework intended as general framework for testing the core GNUstep libraries, called [http://lists.gnu.org/archive/html/gnustep-dev/2005-06/msg00050.html Testsuite]. This may not be suitable for more general unit testing of applications as it's been designed to operate with little of the GNUstep environment actually running. ''Tip: use this if you're describing or fixing bugs or features in base, gui etc.''&lt;br /&gt;
&lt;br /&gt;
* [https://gna.org/projects/etoile Étoilé] contains a port to GNUstep of [http://unitkit.org/ UnitKit 1.1]. This is a straight-forward unit testing environment, suited to the needs of application developers. It also works under X-code on MacOS X.&lt;br /&gt;
&lt;br /&gt;
* [http://www.sente.ch/ Sen:te] have provided a unit testing environment called [http://www.sente.ch/software/ocunit/ OCUnit] which apparently works under GNUstep, although there are comments in the mailing lists about difficulty getting it working.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
* [http://ide.roard.com/wakka.php?wiki=Main GNUstep IDE (idea)]&lt;br /&gt;
* [[Frameworks#Development|Official Development Frameworks]]&lt;br /&gt;
* [[Frameworks#Development_2|Development Frameworks]]&lt;/div&gt;</summary>
		<author><name>Pinkwerks</name></author>
	</entry>
</feed>