On Sat, 2011-09-10 at 13:35 +0200, Stefan Salewski wrote: > A lot of documentation can be bad. > Consider the toys from the big company with the damaged fruit: A reason > for the success of the toys is that documentations seems to be not > needed. > A lot of documentation can make people think that it is very > complicated. This can be true if you don't manage the "reveal" well. IMO, what we could do with is a showcase of the kinds of things people have done with the tools - simple, complex and in-between, so people can gain confidence that the tools can do what they want them to do, before having even picked them up. Others have done good things with gEDA - haven't torn their hair out and given up... it _CAN_ be used to make a relatively complex design. There is a place for technical documentation on file-formats, but a getting started guide should not look like a Lord of the Rings style manuscript ;) -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user