| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| X-EIP: | [Q7YVLu8nFfFav3GeogUVs2LUrebKyy0/] |
| X-Originating-Email: | [hdlguy AT hotmail DOT com] |
| Message-ID: | <BAY167-W11556B6D353B298678B836FC4E60@phx.gbl> |
| From: | peter dudley <hdlguy AT hotmail DOT com> |
| To: | <geda-user AT delorie DOT com> |
| Subject: | RE: [geda-user] PHDL to PCB conversion path? |
| Date: | Fri, 8 Mar 2013 06:43:44 -0700 |
| Importance: | Normal |
| In-Reply-To: | <5139E570.9060509@laserlinc.com> |
| References: | <BAY167-W13054F420737D6BC4ABA461C4E50 AT phx DOT gbl> |
| <3B7337D3-C547-42A5-8480-38379A3EB076 AT noqsi DOT com>,<5139E570 DOT 9060509 AT laserlinc DOT com> | |
| MIME-Version: | 1.0 |
| X-OriginalArrivalTime: | 08 Mar 2013 13:43:45.0679 (UTC) FILETIME=[F46F99F0:01CE1C02] |
| 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 |
--_ac8d6ce6-6161-4470-a3fd-f8afd7e6456d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Josh=2C
Thank you for your reply (and to others who replied earlier).
Your suggestion is interesting. Honestly=2C one of our goals has always be=
en to have a way to graphically review the PHDL design. Writing the gEDA s=
chematic file would be one way to accomplish that.
Your tagging idea would allow the user to pretty up their schematics while =
incrementally adding to those schematics. New items would not mess up previ=
ous edits to the schematics.
Pete
> Date: Fri=2C 8 Mar 2013 08:19:44 -0500
> From: Joshua DOT Lansford AT laserlinc DOT com
> To: geda-user AT delorie DOT com
> Subject: Re: [geda-user] PHDL to PCB conversion path?
>=20
>=20
> On 03/07/2013 10:37 PM=2C John Doty wrote:
> >> Does it make sense for us to write gEDA schematic files?
> > Quite possibly. While creating schematics with human-readable graphics =
is an AI problem=2C schematics that gnetlist can handle are much easier. Se=
ehttp://www.gedasymbols.org/user/john_doty/tools/pins2gsch.html
>=20
> Here is a fun idea: When you generate the schematic file=2C tag each=20
> component with an id. (gschem allows custom tags) Then when you export=
=20
> again=2C any components and connections that already exist can stay where=
=20
> they are and only the difference in wiring and components would be added=
=20
> which would then be adjusted by hand. All graphical decoration stuff=20
> could be left alone.
> This would allow folks to iteratively complete their design using PHDL=20
> as the foundation and graphically place the symbols. Just as it helps=20
> to make a schematic before making a pcb layout=2C it would help to make a=
=20
> PHDL design before making a schematic. Thus the relationship between=20
> the first two probably would apply to the second. Just a higher=2C more=
=20
> powerful abstraction level. This would give the users of PHDL the added=20
> bonus of having a graphical representation to double check that their=20
> language use is correct as well as something to give the layout folks=20
> with the netlist if they are not going to do the layout themselves.
>=20
> Just my 2 cents. :-) Someone had to mention this idea. It was begging=
=20
> to be brought up.
> ~Joshua
=
--_ac8d6ce6-6161-4470-a3fd-f8afd7e6456d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>
Josh=2C<br><br>Thank you for your reply (and to others who replied earlier)=
.<br><br>Your suggestion is interesting. =3B Honestly=2C one of our goa=
ls has always been to have a way to graphically review the PHDL design.&nbs=
p=3B Writing the gEDA schematic file would be one way to accomplish that.<b=
r><br>Your tagging idea would allow the user to pretty up their schematics =
while incrementally adding to those schematics. New items would not mess up=
previous edits to the schematics.<br><br> =3B Pete<br><br><div><div id=
=3D"SkyDrivePlaceholder"></div>>=3B Date: Fri=2C 8 Mar 2013 08:19:44 -050=
0<br>>=3B From: Joshua DOT Lansford AT laserlinc DOT com<br>>=3B To: geda-user AT del=
orie.com<br>>=3B Subject: Re: [geda-user] PHDL to PCB conversion path?<br=
>>=3B <br>>=3B <br>>=3B On 03/07/2013 10:37 PM=2C John Doty wrote:<br=
>>=3B >=3B>=3B Does it make sense for us to write gEDA schematic fi=
les?<br>>=3B >=3B Quite possibly. While creating schematics with human-=
readable graphics is an AI problem=2C schematics that gnetlist can handle a=
re much easier. Seehttp://www.gedasymbols.org/user/john_doty/tools/pins2gsc=
h.html<br>>=3B <br>>=3B Here is a fun idea: When you generate the sche=
matic file=2C tag each <br>>=3B component with an id. (gschem allows cus=
tom tags) Then when you export <br>>=3B again=2C any components and conn=
ections that already exist can stay where <br>>=3B they are and only the =
difference in wiring and components would be added <br>>=3B which would t=
hen be adjusted by hand. All graphical decoration stuff <br>>=3B could b=
e left alone.<br>>=3B This would allow folks to iteratively complete thei=
r design using PHDL <br>>=3B as the foundation and graphically place the =
symbols. Just as it helps <br>>=3B to make a schematic before making a p=
cb layout=2C it would help to make a <br>>=3B PHDL design before making a=
schematic. Thus the relationship between <br>>=3B the first two probabl=
y would apply to the second. Just a higher=2C more <br>>=3B powerful abs=
traction level. This would give the users of PHDL the added <br>>=3B bonu=
s of having a graphical representation to double check that their <br>>=
=3B language use is correct as well as something to give the layout folks <=
br>>=3B with the netlist if they are not going to do the layout themselve=
s.<br>>=3B <br>>=3B Just my 2 cents. :-) Someone had to mention this =
idea. It was begging <br>>=3B to be brought up.<br>>=3B ~Joshua<br></d=
iv> </div></body>
</html>=
--_ac8d6ce6-6161-4470-a3fd-f8afd7e6456d_--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |