Mail Archives: geda-user/2015/02/06/13:48:42
--047d7bdcab847bdb07050e6fdade
Content-Type: text/plain; charset=UTF-8
On Fri, Feb 6, 2015 at 10:20 AM, Jason White <
whitewaterssoftwareinfo AT gmail DOT com> wrote:
> On Fri, Feb 6, 2015 at 1:07 PM, Edward Hennessy <ehennes AT sbcglobal DOT net>
> wrote:
> >> On Feb 6, 2015, at 9:07 AM, John Doty <jpd AT noqsi DOT com> wrote:
> >>> On Feb 6, 2015, at 9:29 AM, Jason White <
> whitewaterssoftwareinfo AT gmail DOT com> wrote:
> >>>
> >>> For those who have not seen, I implemented an example program in C
> >>> using Lua to safely read data defined in Lua files.
> >>
> >> And that is of little use. The schematic and configuration files need
> to be trivially readable/writable by *any* language
> > <snip>
> > Additionally, it becomes more difficult to create a GUI to edit the data
> when the data uses a complex file format.
> >
> > I'd prefer simple configuration and data file formats and save the
> languages for extensions.
>
> What is more simple than name=value or name={value, value, value}? I
> do no see how that is any more difficult to parse than the current
> format.
>
> --
> Jason White
>
While some people may enjoy writing parsers, I am not one of them. I would
rather choose something like xml where I can download a parser for any
language that was written by someone who is a better at that sort of thing
than I am.
I also understand that while the primary goals of this group are Printed
circuit boards I do hope that you keep it flexible enough to extend down
into asic/fpgas or up into multiboard product design. You want to have
symbols and footprints for fpgas but you really do not want to use the
generic symbols from the chip vendor. You want the symbol to have all the
names chosen by the designer to show its circuit names. IO_PAD_1,IO_PAD_2
etc is no way to build a schematic.
The library part for a fpga should contain all the design files needed to
create the bit file for the part. The symbol and bsdl files should contain
all the circuit names.
John Eaton
--047d7bdcab847bdb07050e6fdade
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 6, 2015 at 10:20 AM, Jason White <span dir=3D"ltr"><<a h=
ref=3D"mailto:whitewaterssoftwareinfo AT gmail DOT com" target=3D"_blank">whitewat=
erssoftwareinfo AT gmail DOT com</a>></span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><span class=3D"">On Fri, Feb 6, 2015 at 1:07 PM, Edward Hennessy <=
;<a href=3D"mailto:ehennes AT sbcglobal DOT net">ehennes AT sbcglobal DOT net</a>> wro=
te:<br>
>> On Feb 6, 2015, at 9:07 AM, John Doty <<a href=3D"mailto:jpd AT no=
qsi.com">jpd AT noqsi DOT com</a>> wrote:<br>
>>> On Feb 6, 2015, at 9:29 AM, Jason White <<a href=3D"mailto:=
whitewaterssoftwareinfo AT gmail DOT com">whitewaterssoftwareinfo AT gmail DOT com</a>>=
; wrote:<br>
>>><br>
>>> For those who have not seen, I implemented an example program =
in C<br>
>>> using Lua to safely read data defined in Lua files.<br>
>><br>
>> And that is of little use. The schematic and configuration files n=
eed to be trivially readable/writable by *any* language<br>
</span>> <snip><br>
<span class=3D"">> Additionally, it becomes more difficult to create a G=
UI to edit the data when the data uses a complex file format.<br>
><br>
> I'd prefer simple configuration and data file formats and save the=
languages for extensions.<br>
<br>
</span>What is more simple than name=3Dvalue or name=3D{value, value, value=
}? I<br>
do no see how that is any more difficult to parse than the current<br>
format.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Jason White<br></font></span></blockquote><div><br><br></div><div>While som=
e people may enjoy writing parsers, I am not one of them. I would rather ch=
oose something like xml where I can download a parser for any language that=
was written by someone who is a better at that sort of thing than I am.<br=
><br><br></div><div>I also understand that while the primary goals of this =
group are Printed circuit boards I do hope that you keep it flexible enough=
to extend down into asic/fpgas or up into multiboard product design. You w=
ant to have symbols and footprints for fpgas but you really do not want to =
use the generic symbols from the chip vendor. You want the symbol to have a=
ll the names chosen by the designer to show its circuit names. IO_PAD_1,IO_=
PAD_2 etc is no way to build a schematic.<br><br></div><div>The library par=
t for a fpga should contain all the design files needed to create the bit f=
ile for the part. The symbol and bsdl files should contain all the circuit =
names.<br><br><br></div><div>John Eaton<br><br><br></div><div><br><br><br><=
br></div><div><br></div><div><br><br>=C2=A0</div></div><br></div></div>
--047d7bdcab847bdb07050e6fdade--
- Raw text -