X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<20151223195846.8392.qmail@stuge.se>
Date:	Wed, 23 Dec 2015 20:58:46 +0100
From:	"Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Project leadership
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<CAJXU7q_3XwthnN_8mp7B+-ShHeK+=7J=54ZavKBUG3S3bSKp2A AT mail DOT gmail DOT com> <5AC3D5C5-144F-41AE-9562-47BC34D9047F AT noqsi DOT com> <CAJXU7q_GnuGNMtUWkB-xgBiKgY5R5W4ZCjtnz5EJizG+46dm1w AT mail DOT gmail DOT com> <C7FDF8B6-B335-46C3-8A25-F95ACECF4B79 AT noqsi DOT com> <CAJXU7q_3XwthnN_8mp7B+-ShHeK+=7J=54ZavKBUG3S3bSKp2A AT mail DOT gmail DOT com> <20151222193859 DOT 26898 DOT qmail AT stuge DOT se> <20151223202851 DOT 637d5b1f AT jive DOT levalinux DOT org>
MIME-Version:	1.0
In-Reply-To:	<20151223202851.637d5b1f@jive.levalinux.org>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]"
> <geda-user AT delorie DOT com> wrote:
> 
> > I would cautiously nominate myself. Cautious because:
..
> > My first priority for a major change would be to move PCB to a
> > generic geometry data model.
> 
> Yes! Finally! Please go ahead and do it. I failed.
..
> Do you have some plan?

I want to make it clear that I do not believe that I would be able to
work very much with the code - I just don't have the time - but I
would try to find and give direction and help with the big picture.

I looked at the proposed C++ geometry library, but I'm not at all
convinced that it is such a good fit for gEDA/PCB. Starting from
scratch seemed a better alternative to me than that library. Things
like snapping to a grid could then be implemented efficiently right
from the start, as opposed to being added on top after the fact, with
benefits likely for both implementation and performance.


//Peter

- Raw text -