X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=zoEmFVJ/geE7VKG6Q5GRFsXrmovjgOnpuFW6OutjDn0=;
        b=dGXwxcsZajWFtOzf4DSiBFBpmwDA502E3z6Jeleus2/aIdBkfOh2tvxuG0dRm9K53R
         J1++qKOO5mZCd7Q8YDnPx3IAn1jer6dln5xZ260GI+Y9OY1UVv/Vxk1HdTDCyN0VJbYr
         nd9mtgJIh0Js8nIFzxfQA98vfXYHbN/EDf+1eeG2CgRRnuoZd6ebBKAUrqCX0z4Sor2k
         jpvbcJMp7gr3uMK18NKk1FX8vZcJ4FtY9xilt03geHD0Bqlp91uiKXl0w9iVbLe3iZHF
         cXKLCowub+G+n9qx4C6PSUlx58bPw59MF/vEPsHYVLipzCXtjQebeqdHragMUC5gAIoz
         BJfQ==
MIME-Version: 1.0
X-Received: by 10.60.45.10 with SMTP id i10mr11519230oem.75.1442848406955;
 Mon, 21 Sep 2015 08:13:26 -0700 (PDT)
In-Reply-To: <CACwWb3DhZCvy7sffoG5GW-=-EYAC5Ym8KOQ2HJnGe6kov+pXRQ@mail.gmail.com>
References: <20150921001659 DOT 0c211170 AT jive DOT levalinux DOT org>
	<55FF3F4B DOT 8000406 AT jump-ing DOT de>
	<CACwWb3DhZCvy7sffoG5GW-=-EYAC5Ym8KOQ2HJnGe6kov+pXRQ AT mail DOT gmail DOT com>
Date: Mon, 21 Sep 2015 11:13:26 -0400
Message-ID: <CAOFvGD7zFq=ypb5gWWvqv_FemiJucm_cDfAPfeeTmGiu-zKNyg@mail.gmail.com>
Subject: Re: [geda-user] Apollon the technical thread
From: "Jason White (whitewaterssoftwareinfo AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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

Hello Lev, I am interested in seeing how the database will turn out.

I don't see a text primitive. How do you intend to handle text on the
circuit board? I suppose could define each symbol as a component (very
similar to what PCB does already).

If you get a chance, I it would be helpful for my understanding to
have a mock-up database to look at. (I'm afraid the specification's
formatting is somewhat hard for me to follow) A sqlite file containing
a few components, pad-stacks, nets, and tracks is all I'd like to see.
(ie. surface mount resistor hooked to 2 pin jumper).

Once that exists, I think it should be easy to see if there are any
omissions or redundancies in the specification.

On Mon, Sep 21, 2015 at 4:57 AM, Levente (leventelist AT gmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Thanks. I'll add them.
>
> Please note that users can define own layer types like mechanical
> documentation, etc.
>
> Lev
>
> On Mon, Sep 21, 2015 at 1:20 AM, Markus Hitter (mah AT jump-ing DOT de) [via
> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>
>> Am 21.09.2015 um 00:16 schrieb Lev:
>> > INSERT INTO layer_type (id, name) VALUES (0, "conductive");
>> > INSERT INTO layer_type (id, name) VALUES (1, "silk");
>> > INSERT INTO layer_type (id, name) VALUES (2, "mask");
>> > INSERT INTO layer_type (id, name) VALUES (3, "paste");
>>
>> You can find more layer types in src/hid.h.
>>
>>
>> Markus
>>
>> --
>> - - - - - - - - - - - - - - - - - - -
>> Dipl. Ing. (FH) Markus Hitter
>> http://www.jump-ing.de/
>
>



-- 
Jason White