X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] The new to do
Date: Mon, 13 Jul 2015 02:18:38 +0200
Lines: 50
Message-ID: <mnv04v$if0$1@ger.gmane.org>
References: <CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-9-99.net-htp.de
User-Agent: KNode/4.14.1
Reply-To: geda-user AT delorie DOT com

Evan Foss (evanfoss AT gmail DOT com) [via 
geda-user AT delorie DOT com] wrote:

> * PCB clean up documentation so that people can actually code with
> out heroic measures.
> * Fill in missing documentation on gEDA
> * Make an API that allows for C instead of Scheme.
> * Back annotation
> * Fixing the 45 degree preservation patch so dragging works
> * Clean up PCB's concept of a design with a unified data structure

I'd add:
* have a nice working library by default. That is, a set of symbols 
and footprints for the most common components that works out of the 
box.
* a consistent manual for all major components of geda.
* make gschem scriptable in a widely known language.
* make pcb scriptable in a widely known language. Preferably the same 
scripting language as for gschem.
* a wizard/template/whatever mechanism to aid building a hierarchy of 
schematics
* cross-selection between pcb and gschem
* more sophisticated search and replace dialogs (both, in gschem and 
in pcb)
* separate design rules for different route styles
* separate design rules for inner and outer layers
* better handling of design rules in the GUI of gschem and pcb
* more consistent handling of "settings" and "preferences" in pcb
* a dialogue to set colors on a per user base in gschem
* generalized layers in pcb rather than internal special casing

And of course, my personal favorite:

* the notion of "packages", a container format for all information on 
a component. E.g. symbol(s), footprint(s), value(s), spice model, 3D 
models, notes, data sheets, ...


> * DVCS for PCB

I got the impression, that pcb source is already managed in a git 
repository ( git://git.geda-project.org/pcb.git ).

> 
> My last minute thoughts
> * Export to Eagle CAD?

This would be nice. But I'd prioritize import/export to kicad. 

---<)kaimartin(>---