X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Yahoo-Newman-Id:	412361 DOT 48644 DOT bm AT smtp110 DOT biz DOT mail DOT gq1 DOT yahoo DOT com
X-Yahoo-Newman-Property:	ymail-3
X-YMail-OSG:	O9kTzNAVM1k2rj7FGpyR1iqydqaPESN53mXOCW5LvRk6Nu.
	EvZy76u1XFaERjxJL4VGpY3p4Aoo7iRHgwi62k.3X.JudaRewVU3xKH65xHT
	VEgSkF8MJDr764v8DZBZpqlKBFBwmhgBIiBxtKXEmnROuOvQkCc9iK5Fd2xX
	WagiIsvhuSdQ.CUakNpGBZDiCfbi8mCgojHEcfewstqCzxHnltdYRalfDvyX
	huaBLazps4_TSjG3lZTEx7aOINczPHZplDG3Lv1Oww8kVmqVB3gFHQWygE4U
	ERlOmq1g7U_wqBlsHnXY_HpnF8IvWLbqDZwtmQQNtffhFLT2oe8kjwu7FVoh
	mJUzAa3o2PRgtQhN_mBmBCEQZNGJBpr10xUMw7h2e4KYA4bENZ3YdL_83o5h
	gN39_bgpIsjm684iG9uYQuX.1ZQrR3Ycgo6XYWSwNmaVph8u7g4C2xGj.xQp
	v31Bbm9zp21tqLwTgtrn9nNCcEdMEW_KqnChKGnSNuykj.6x806_0xNiA1Xv
	d9M6KV2vuh9avwexonkojEe3HROxLLId2T90RkHnGcA--
X-Yahoo-SMTP:	7zb8EAqswBCnSUMm5KccNoxZ2QYVikaLwu.J
Subject:	Re: [geda-user] PHDL to PCB conversion path?
From:	Mike Crowe <mcrowe AT gcdataconcepts DOT com>
To:	geda-user AT delorie DOT com
In-Reply-To:	<BAY167-W13054F420737D6BC4ABA461C4E50@phx.gbl>
References:	<BAY167-W13054F420737D6BC4ABA461C4E50 AT phx DOT gbl>
Date:	Mon, 11 Mar 2013 10:17:52 -0500
Message-ID:	<1363015072.3013.114.camel@crowe.localdomain>
Mime-Version:	1.0
X-Mailer:	Evolution 2.30.3 (2.30.3-1.fc13)
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

On Thu, 2013-03-07 at 03:21 -0700, peter dudley wrote:
Greetings
I am very interested in your work!  I too have problems with the
scalability and maintainability of graphical programming languages.

I have a few questions after spending a few minutes on your site.  

Is there a reference somewhere that describes the syntax a little more?
Specifically how would someone include a library of components (possibly
"#include")?  How do sub-circuits work?  How do you handle non-numeric
pin designators?

Schematic, layout, and BOM maintenance is a big issue for me.  Is there
a tool that allows attributes be back annotated from a database?

I'd like to see a tool that takes a gschem schematic and produces PHDL.
The work may be half done.  I have existing tools that convert gschem
files into XML documents.  Is there a tool that takes XML and converts
it to a PHDL?

As far as pushing PHDL to PCB,  I think it would be pretty simple to
implement with a PHDL->XML->XSLT->PCB chain.  PCB artwork updates would
probably be a little more difficult to implement, since components and
nets need to be inserted and removed.



> Hello All,
> 

> I am currently part of a small group of people developing a new
>  Hardware Description Language (HDL) specifically for Printed Circuit
>  Board (PCB) development.  We call our language PHDL.  It is a
>  open-source project and you can find some information about it here if
>  you are interested, http://sourceforge.net/p/phdl/wiki/Home/.  We have
>  written version 1 and version 2 of the PHDL compiler and quite a few
>  utilities to support it.  
> 
> PHDL replaces schematic entry in the the PCB design flow.  As such, our
>  compiler must write out netlist files in the correct format for each
>  layout tool we want to support.  So far, PHDL 2.1 can write netlist
>  files for Mentor PADS and CadSoft Eagle PCB.  We are currently doing a
>  rewrite of the PHDL compiler to improve maintainability and
>  extensibility and we would very much like to write netlist files that
>  are compatible with the gEDA/PCB layout tool.
> 
> I am seeking advice here.  Can anyone offer an opinion as to the best
>  file format to write in order to get our netlist into the gEDA/PCB
>  layout tool?
> 
> I see gnetlist converts gEDA schematic files to something that geda/pcb
>  can read.  Does it make sense for us to write gEDA schematic files? 
>  Is there a simpler or more stable file format we should write to get
>  into this open source layout tool.
> 
> I also stumbled across a webpage for a gEDA Translate project but it
>  looks to be just conceptual at this point.
> 
> Anyway, all constructive advice is appreciated.
> 
> Regards,
> 
>     Pete Dudley  		 	   		  

- Raw text -