X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=PCMADsqj9zUZYKxk/jfpv8KqCDquiFc+62t229d9VLU=; b=ZCneicCxgCVat+c9JbNuxML6kZjg5ipQwnN3h260opTC9TY/xGIhkFWc75Q8PB0xR8 NZcXQlk7rP3Rm9rzVur9dtpbiAbkNVURvWmOihylpqmF2i3l0HseItTt2t0ua3/bIuTX +REHdknH7SEVTSllFQGRhU33wgrlMpnMdC6+JOsLF2m92/Kf3OOYWR3VcFQoSCei6IvN rjHs7p70krs1QHjLYvZkBLZidsIzWdlh6fzo12G5G5CuCB44yb+SA8u2ZdAQf2MkC708 VB6LtxoU5bajO+QldQtkC2D658vMUFTEdJTfZaiizdDLf/hq70oJCpJYhEcmo3om+Wei rssQ== MIME-Version: 1.0 X-Received: by 10.194.187.235 with SMTP id fv11mr10418863wjc.16.1423248453259; Fri, 06 Feb 2015 10:47:33 -0800 (PST) In-Reply-To: References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de> <90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net> <201502042333 DOT t14NX28o024789 AT envy DOT delorie DOT com> <7C1A5871-3056-482C-BC58-173D90D80F77 AT icloud DOT com> Date: Fri, 6 Feb 2015 10:47:33 -0800 Message-ID: Subject: Re: [geda-user] FOSDEM From: Ouabache Designworks To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=047d7bdcab847bdb07050e6fdade 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 Precedence: bulk --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 > wrote: > >> On Feb 6, 2015, at 9:07 AM, John Doty 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 > > > > 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


On Fri, Feb 6, 2015 at 10:20 AM, Jason White <whitewat= erssoftwareinfo AT gmail DOT com> wrote:
On Fri, Feb 6, 2015 at 1:07 PM, Edward Hennessy <= ;ehennes AT sbcglobal DOT net> wro= te:
>> 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 n= eed to be trivially readable/writable by *any* language
> <snip>
> Additionally, it becomes more difficult to create a G= UI 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=3Dvalue or name=3D{value, value, value= }? I
do no see how that is any more difficult to parse than the current
format.

--
Jason White


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.

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.

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.


John Eaton





<= br>



=C2=A0

--047d7bdcab847bdb07050e6fdade--