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=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=+39UJLbvMBR6wKobU56GBWVEYpCWTswa+VoVjJL3pPQ=;
        b=eB418ox8gQuglpWg3HsPsd8FCKuOeulBovoDALEAiX3ygkN3FnTgScNi5DuDuJmXO6
         dMKZOeKjuE+7z4aV5IO/UVbtgeVXEgob+rpROxVYFscOL1pB0Miu2w0nY9c9aojeYJHi
         svrL+DOT3M6RU+N2px07sMG4IsnX74t4/jK0QI1w9bi+MpZ0INHTv4oSQYvxLDs+5eOc
         SyaHKTMNSEyGT6wPjvyknUiH3bmDqJDOPhjzKpnXOOcfMagdEz6aqySH+huLsCdup8rj
         kpeFoMEBlyDnLun1DJPtuYR4q1ueK++BHTa46RF40ULkiSHbLBnnrpf7rVxMfwO9GDDB
         Wlsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=+39UJLbvMBR6wKobU56GBWVEYpCWTswa+VoVjJL3pPQ=;
        b=ZaGJhROB9+yNNdg3WWlPOoKUBF/tJ0mYH9DKIjnSg1iDUuBI2acqPyCpLfO/KOhsHb
         ZvQ+BHad/fvvS6IgTfUx/G6yKEelCXevkMI1D2KQeJIIpA/44Z0ypw3wrqgj4dLJpcon
         Siqb4LjplNtPxyU5WDUUBjgF4tPKDr874P6fw9se9Wt80os8mFPHLjPhp3SfSiG2qlK5
         q1SINSmTo29sR3SQMlfrCbEyR8OXaxxjETYt8PouBXkTsyPvTmSBguxGPKxvv7dldwgu
         IV8T2CKrUcnmgT7OYjk2XV9sfiF/XJA1NGQ5H8914fbssp4yQj7xa5TDnnKalDzUJDm5
         1Hvw==
X-Gm-Message-State: ALyK8tKL4V8/Us0DuoeLYeoHEzOaX1MrBOcfyk4v+lILf+OorSp4XM/ENvRD8F6ca5wMKg==
X-Received: by 10.28.216.75 with SMTP id p72mr35056455wmg.67.1469318458613;
        Sat, 23 Jul 2016 17:00:58 -0700 (PDT)
Date: Sun, 24 Jul 2016 02:00:53 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Stay or go?
Message-Id: <20160724020053.a598f73dcc0773aa43f2bf6a@gmail.com>
In-Reply-To: <CAM2RGhQJozEEoH45xD8fndA+8XyrHJ2r0sW9QAESn6m4Y-qf6Q@mail.gmail.com>
References: <98D1C4E4-581D-4A03-94E4-E0330960EADF AT wellesley DOT edu>
	<CAM2RGhS+cHu3g_D21uW-=dB8pUOKcCxEb_+V6LyQhfvi+ep8GQ AT mail DOT gmail DOT com>
	<20160723224811 DOT 2e9f59de5a5898c59003ff85 AT gmail DOT com>
	<CAM2RGhQJozEEoH45xD8fndA+8XyrHJ2r0sW9QAESn6m4Y-qf6Q AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

> > With attribute handling I mean pin mapping, BOM generation and similar which is handled thru attached attributes. I think gschem use non of the attributes itself, just assign and display which work great.
> 
> Yes but to be fair slotting has it's issues.

Attribute for pin may be changed from layout in pcb or assigned later in workflow. This is a feedback issue and attribute is not interpreted by gschem.

If gschem assign pinnumber which I think slotting mechansim do, it must interpret the attributes and define rules for them. There is a problem because same symbol may be used at different positions for different packages and package may not be known or changed afterwards. I think point to mapping with attribute or embedded would or have solved it. Not all circuits end up on a circuit board and for these package pin numbers may not make any sense and better removed.

This pin mapping selection is also a problem for some circuits available in different packages.