www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/06/29/12:14:29

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=Y/KWWH2mNwP0dPcCXez/If+LkRKW1EAl/KCT2cMOAMU=;
b=FuTkQ6CtfLlUnBj5EJTqza2jN15bAE6yuBs995luidu6w80xlNQZleJEOPjwppUk0q
QYcBc3KV8u/qZjoOf+PLZjmou3c0eT4bOlWGAJtXJaaxPfZnHQBkShjCj90F7/Kk2DCN
xPQQAUV8y+6Clvpi65OhI2H09PP9LM0x8fOMCcPP2jmuDke+xM3bJ8wOmGIComMbUbFe
xyt6tnYKwZqCkrEBcCUJ5keaYXYAMFe7J0xhrPVfQwQZI1EXlTjMXWoMLB2v7jY4Hnbb
/lmhnWU4xIsBbdZO3VefSTfaE9cysZlsz/aydGtMObMbE8n0t+GVJWxoevu3nKsH5poN
1a1A==
MIME-Version: 1.0
X-Received: by 10.60.62.180 with SMTP id z20mr15518105oer.56.1435594447682;
Mon, 29 Jun 2015 09:14:07 -0700 (PDT)
In-Reply-To: <1435592698.1607.17.camel@ssalewski.de>
References: <1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de>
<55902AB9 DOT 9000004 AT neurotica DOT com>
<alpine DOT DEB DOT 2 DOT 00 DOT 1506281932040 DOT 6924 AT igor2priv>
<20150629113018 DOT GH19654 AT fi DOT muni DOT cz>
<1435581145 DOT 1447 DOT 19 DOT camel AT ssalewski DOT de>
<CAOFvGD7npho6fPKAEmce6L1nXy=5EEsVaEH-Vj_XEuiLddodDA AT mail DOT gmail DOT com>
<1435592698 DOT 1607 DOT 17 DOT camel AT ssalewski DOT de>
Date: Mon, 29 Jun 2015 12:14:07 -0400
Message-ID: <CAOFvGD7CCD80=s5nZaGkzTCv=hkEmW3C-Qy_gZ2Ua4kVXZ7O2A@mail.gmail.com>
Subject: Re: [geda-user] gEDA/gschem still alive?
From: "Jason White (whitewaterssoftwareinfo AT gmail DOT com)" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
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

--001a11c21da61882dd0519aa617b
Content-Type: text/plain; charset=UTF-8

Stefan,

Perhaps in addition to having different color nets, the line style could
also be altered. For instance different patterns of dashed lines, or the
thickness of the line could be altered so that the user would specify
"skinny" or "fat" in conjunction with color and the dash pattern.

I would think that would allow for quite a number of different net classes.

On Mon, Jun 29, 2015 at 11:44 AM, Stefan Salewski <mail AT ssalewski DOT de> wrote:

> On Mon, 2015-06-29 at 10:47 -0400, Jason White
> (whitewaterssoftwareinfo AT gmail DOT com) wrote:
> > Stefan, I think the easiest solution to net grouping attributes such as
> > "Power", "Analog", or "Digital" is to allow for each net to be displayed
> > with a different color.
>
> Yes, that is generally the first idea. Problem is, that we may not have
> enough different high contrast colors. We may have analog and digital
> ground, analog and digital power and ground, high speed signals,
> impedance controlled traces, short traces i.e. for bypass capacitors and
> much more. We discussed about all that about 4 years ago, when I started
> work on my Peted editor. I think one idea was to not add direct
> properties to nets, but net classes like "HighSpeed" which may be mapped
> to 50 Ohm with 2 inch maximum length. I will read that discussion again
> some time -- but next 300 hours is for finishing release 1.0, which
> provides only a subset functionality of gschem, but has nice look and is
> easy to use.
>
> One question, which I asked myself some days ago:
>
> gschem has multiline text, but generally only single line attributes.
> What when users try to enter multiline attributes? Accept or ignore it
> for netlist? And how to display on screen? ShowName, ShowValue and that?
> My feeling is that we should allow multiline attributes, but let
> ShowName, ShowValue be set only for all the lines at once. But some
> lines may be valid attributes, and some plain text? Not very easy to
> handle.
>
>


-- 
Jason White

--001a11c21da61882dd0519aa617b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Stefan,<br><br>Perhaps in addition to having differen=
t color nets, the line style could also be altered. For instance different =
patterns of dashed lines, or the thickness of the line could be altered so =
that the user would specify &quot;skinny&quot; or &quot;fat&quot; in conjun=
ction with color and the dash pattern.<br><br></div>I would think that woul=
d allow for quite a number of different net classes.<br></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 29, 2015 at 11:44 =
AM, Stefan Salewski <span dir=3D"ltr">&lt;<a href=3D"mailto:mail AT ssalewski.=
de" target=3D"_blank">mail AT ssalewski DOT de</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">On Mon, 2015-06-29 at 10:47 -0400, Jason White<br>
<span class=3D"">(<a href=3D"mailto:whitewaterssoftwareinfo AT gmail DOT com">whit=
ewaterssoftwareinfo AT gmail DOT com</a>) wrote:<br>
&gt; Stefan, I think the easiest solution to net grouping attributes such a=
s<br>
&gt; &quot;Power&quot;, &quot;Analog&quot;, or &quot;Digital&quot; is to al=
low for each net to be displayed<br>
&gt; with a different color.<br>
<br>
</span>Yes, that is generally the first idea. Problem is, that we may not h=
ave<br>
enough different high contrast colors. We may have analog and digital<br>
ground, analog and digital power and ground, high speed signals,<br>
impedance controlled traces, short traces i.e. for bypass capacitors and<br=
>
much more. We discussed about all that about 4 years ago, when I started<br=
>
work on my Peted editor. I think one idea was to not add direct<br>
properties to nets, but net classes like &quot;HighSpeed&quot; which may be=
 mapped<br>
to 50 Ohm with 2 inch maximum length. I will read that discussion again<br>
some time -- but next 300 hours is for finishing release 1.0, which<br>
provides only a subset functionality of gschem, but has nice look and is<br=
>
easy to use.<br>
<br>
One question, which I asked myself some days ago:<br>
<br>
gschem has multiline text, but generally only single line attributes.<br>
What when users try to enter multiline attributes? Accept or ignore it<br>
for netlist? And how to display on screen? ShowName, ShowValue and that?<br=
>
My feeling is that we should allow multiline attributes, but let<br>
ShowName, ShowValue be set only for all the lines at once. But some<br>
lines may be valid attributes, and some plain text? Not very easy to<br>
handle.<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature">Jason White</div>
</div>

--001a11c21da61882dd0519aa617b--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019