Mail Archives: geda-user/2016/01/09/12:32:06
--Apple-Mail=_95CC858F-C3C3-45D0-A248-F4DAE4169014
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Jan 9, 2016, at 12:06 PM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>=20
> On 09/01/16 16:48, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) =
[via
> geda-user AT delorie DOT com] wrote:
>>>> Whether or not this is fully factored in the code or not, from the =
graphical entity point of view these are effectively sub-type =
specialisations of the line primitive, as John has suggested. Whilst it =
would be technically possible to take this as a more "duck typed" =
approach, I'd probably not suggest it.
>>> What I was trying to get at is that I see line drawing style as a =
fundamentally orthogonal issue to line =93type". What we have now is =
hard-wired, except for purely graphical lines. That doesn=92t fit all =
uses. It gets us into unresolvable arguments over thick net segments for =
power versus thin segments for signals. Conventions are good. Defaults =
implementing conventions are good. Hard wiring them is bad.
>>>=20
>>> John Doty Noqsi Aerospace, Ltd.
>>> http://www.noqsi.com/
>>> jpd AT noqsi DOT com
>> You mean if a line should be considered: net, bus, pin, ... should =
depend on an assigned attribute?
>>=20
>>=20
>> Nicklas Karlsson
> As it stands, a line is a line is a line .. its either a graphical
> element or a net.
Or a pin. Or a bus.
> It has no 'knowledge' of a pcb trace/track or anything
> else.
> I don't see this is a problem for the existing functionality ..
The issue is merely to disconnect the line drawing style from the line =
semantics, to allow the person drafting the schematic to communicate =
better with the person reading the schematic.
> you know (presumably) what you're routing/laying out when you do it?
> We've always had the schematic up on a second screen whilst routing =
any
> PCBs .. is there another way!?
>=20
> If you want to get into sophisticated routing, yes you're going to =
have
> to completely re-think how you do schematic capture. I would argue =
this
> is a major rewrite of sections of code .. something I'm not sure =
anyone
> has time or inclination to do? Correct me if I'm wrong, of course....
>=20
> MJE
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_95CC858F-C3C3-45D0-A248-F4DAE4169014
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWkUQJAAoJEF1Aj/0UKykRiUEQAJV/HEw9V+XUv9m3UJNB1XaA
t1yp7VdKhEiJ8DJaeOLmNHvB7jdpBIadcHM6YIgtU8AjuUbq1rbQ7O+XuukIRzm1
VMoBMwtVTPiWkAYGgooq+yAePTXTD6N/4CYQdqbXH+nY985tu9xPL/nYiZJe5/U5
SEkRGFOGaBN4XzQCoht+tXuMUr43hVKXL68oCzT8CGdYg+oCwFVggUe3lDrPftRF
P04FgZ75gKOB79rhQAC+SjAuSYjSSTsraTGLOiVim76XIxaBfEdCjUoMKvJSB9GW
ico1AQxxyPjg8Qn5KKy7AHZ32Y70u78TKkm3egGFolW9N21k4XuR2BQ8qMhvjOrX
KBCWP++noiNtABIXeAyU20fbYsonVfybt5f0lC+9ksl9RcErNTQCTfbC2gBOK8np
qWYf766Hm3Bq0no7uWDxAk/TLeUYKrplbbQhb4kjfHnd2ibVBBDVyAeoF55YFeur
FJ9hUxl8qeK54DxhnPF4yKT/JwkusHBlB6km1QOA3mFqD0NNUffeDEtQEO3NfOTI
59uD5KOVFfM/F6OG5UrcyBtNTXGdp07qbIa7d2aDmhmY8cX0nkfn+yiRo1IW+y5O
LC1KB2PPDsquPEeEm50TFumrkitNAo4dzG54QV+Ync/rbjIyN+NCb8HdLXO9Yvea
z/jo4WDioIyAk1pC3sBf
=Fx3h
-----END PGP SIGNATURE-----
--Apple-Mail=_95CC858F-C3C3-45D0-A248-F4DAE4169014--
- Raw text -