X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 24 Dec 2015 13:43:03 +0100 From: "Stephen R. van den Berg (srb AT cuci DOT nl) [via geda-user AT delorie DOT com]" To: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] A fileformat library Message-ID: <20151224124303.GA22838@cuci.nl> References: <20151223194905 DOT 7676 DOT qmail AT stuge DOT se> <0AB5D926-731F-4A49-AA26-D06DAE7C2CB0 AT noqsi DOT com> <201512240626 DOT tBO6QuW0031998 AT envy DOT delorie DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: >The flip side, and a point that is hopefully still compatible with this >view - is that for some tasks, _having_ to hand edit the data file means >that our gui is failing (badly). True in some cases. But sometimes you need to do something awkward and time consuming that is possible to describe in a few sentences, but a nightmare to do in any GUI. This even happens to me on databases at times. Ever tried to migrate a Wordpress site to a different domainname? Easiest way is to get an SQL ASCII dump, then do find-replace on it, then reload the database. With regard to gschem and pcb; it would be trivial to throw everything into an SQL schema, and then write an exporter and importer from SQL to the existing fileformats and back. When you then extend the structure in SQL which the exporter/importer don't understand, you either live with the fact that you lose information when you export/import it, or you extend the exporter/importer as well to support the new structures. -- Stephen.