X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h=
	message-id:date:from:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	uOxSRfWF6xd2SaeD1X/Nb0kMLj1qeUMSDhfyZLGZdFA=; b=c+bMUbz4EkNI0alW
	ataSB78yrepQsBPWwUChcaEXnKqjVgu1xcxfX3SgX9DGTCUqtQZKY8BQNAx/DuYM
	dLQE9/grJwPp9V/+ctV8uFeu492oshsigQ91g/gWPCz8bP5tY1VXdY0HhB9Jvmh8
	+f+8elF4ObRJZlykDL/PPo4qnt8=
Message-ID: <509282C1.3080407@jump-ing.de>
Date: Thu, 01 Nov 2012 15:10:09 +0100
From: Markus Hitter <mah AT jump-ing DOT de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was:
 Pin hole size)
References: <CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com> <1511E63C-F435-44B1-9734-C7AF7AF49A92 AT sbcglobal DOT net> <20121030132922 DOT GY32696 AT fi DOT muni DOT cz> <k6tu8g$f3n$1 AT ger DOT gmane DOT org>
In-Reply-To: <k6tu8g$f3n$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

Am 01.11.2012 14:42, schrieb Kai-Martin Knaak:
>> Again, as a newcomer, I find the documentation of geda to be
>> >one of the weakest points.
> As a user since 2005 I too find documentation a weak spot.

Well, both of you can work on that. I'm pretty sure people on this list 
happily answer questions which can't be answered from the wiki.

For developers, writing documentation is double work, after all, 
sometimes leading to a day of finding all the spots needing updates, 
while implementing the feature it's self was the easiest part of that. 
Greatly distracting, as an average human brain has some 1400 grams, 
only. ;-)


Another view: for myself, I don't like reading documentation. For some 
overview, perhaps, but in general a piece of software should be 
intuitive and self-explaining. Like the Git command line tool, for 
example, which gives hints to the likely next steps on each command sent.

In the same vicinity I've made the tooltips in the G-code exporter much 
more verbose. People having a vague idea of what G-code is should find 
the exporter-specific bits in the tooltips and with a bit of experimenting.


my $0.02,
Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/