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=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=288MgvaAspzH8jOxGix1qdOAnWkAOuAXFTACw2+x+1I=; b=hTG82G7KhT5f8+3Et2+I4+MmRiBP4fujcGxLcj02RTNaN8cCnxizNvZuFhUNwS8bo3 szeE4S2xwrZnr9WEsw5EFxQ1bpj9HibyLIpWpc/sgPKDZxeZAGxPWsNF5jJLEu2QDCIb TrRIRrfGHKmcSJYqV3bPMz/SWriygO3KOsoNhHiYOv2oV3UknJ8uAt5s3sZ+ErVFyn1P Le8OSdM1kpHDNP8sTJKsXvYmdLHhw8dzl1WoNPYJIhcpwioIgnodU7KgP1XRuXDlGKez NnqERQa1AwENoXb9NbdMzbjp2Qd2TIR24oPXkxNlQb6wCuEXP9M4wuLy6ft2HY/PZVJ2 W93Q== X-Received: by 10.180.86.138 with SMTP id p10mr14221975wiz.39.1442130265025; Sun, 13 Sep 2015 00:44:25 -0700 (PDT) Date: Sun, 13 Sep 2015 09:44:23 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] shortest way towards parsing .pcb files outside pcb Message-Id: <20150913094423.2673a8fdf1369b0d4bd158a6@gmail.com> In-Reply-To: References: <201509120239 DOT t8C2dAiO026962 AT envy DOT delorie DOT com> <201509122223 DOT t8CMNhaZ024482 AT envy DOT delorie DOT com> <20150913092016 DOT bc0a237e5f1d94f561578533 AT gmail DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Sun, 13 Sep 2015 09:35:55 +0200 (CEST) gedau AT igor2 DOT repo DOT hu wrote: > > > On Sun, 13 Sep 2015, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > > Are there really an problems with the current file format that's hampering development? > > I think there are problems with the internal data model, which are in turn > reflected in the file format. I believe the syntax of the current file > format is flexible enough to follow changes in the data model. > > The current data model makes it hard to implement some of the features > popping up in these threads. Then I guess it would be better to start with the internal data model and change file format then figured out how it could better represented.