X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 11 Jan 2016 01:36:56 -0500
Message-Id: <201601110636.u0B6augO009880@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <56934C45.7080605@iee.org> (geda-user@delorie.com)
Subject: Re: [geda-user] A new PCB file format - modular system
References: <5692CBD5 DOT 3020101 AT prochac DOT sk> <CAC4O8c8iQnuy2L8QG=absBhnUTuVRj-jJyVNhoqeSiPmiT0gWw AT mail DOT gmail DOT com> <201601110319 DOT u0B3JTVl025695 AT envy DOT delorie DOT com> <56934C45 DOT 7080605 AT iee DOT 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
Precedence: bulk


> Whilst I take your point in that the HID module is presently the
> be-all and end-all of access to pcb data,

The HID interface doesn't quite work that way, see src/hid.h for
details.  The API is strictly one-way - the core uses the API to talk
to the plugins, not the other way around, and typically just to
trigger actions.  Modules can read the core data without going through
the HID api at all.