Date: Sun, 22 Dec 2013 01:06:34 +0600
From: Alexey Shaposhnikov <canisdirusleidy AT yandex DOT ru>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] [PATCH] Customizable graphical elements
Message-ID: <20131222010634.2e9d5ba8@warrawoona.sti>
In-Reply-To: <20131221143249.GA31097@localhost.localdomain>
References: <20131213050140 DOT 4ae1f52c AT warrawoona DOT sti>
	<20131221143249 DOT GA31097 AT localhost DOT localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

On Sat, 21 Dec 2013 18:32:49 +0400
Vladimir Zhbanov <vzhbanov AT gmail DOT com> wrote:

> IMO, the part with buses should be made as a separate patch.  Your
> vision of buses may not be applicable to all. For instance, how to
> distinguish the case where buses don't connect and just cross one another?

IMNSHO this (crossed but not connected buses) is a clearly bad thing and a sign
(like more then 3 indentation levels in source code) that the schematic needs
to be redrawn with less spaghetti. Plus with current default values (cue
diameter for buses intersection is equal to the bus line thickness) in gEDA is
difficult to distinguish connected buses from just crossed, and after export to
monochrome image (which is default in gaf export) just impossible.

> I think the way buses are displayed should be at least configurable.

(Remembering xkcd strip about workflow) But here you're probably right.

> I think you should not call eda_config_get_context_for_file every
> time gschem creates an object.

I think in a similar way, but there is a small problem: can't come up how to
send these values to libgeda and libgedacairo functions. Now I see two possible
ways: add argument to o_..._new and cue drawing function or add new properties
for TOPLEVEL and EdaRenderer objects. And I dislike them both (due to obvious
API changing).

-- 
С уважением, Алексей Шапошников.