ftp.delorie.com/archives/browse.cgi | search |
On 12/24/2015 08:28 AM, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: > Stephen R. van den Berg (srb AT cuci DOT nl) [viageda-user AT delorie DOT com] wrote: >> >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. > Or stay with the status quo, which I don't think is good enough. >8 I want to be able to sift the data. Now there is a way with scheme/LISP similar to Skill code I used to do, but having SQL could be very good also -- there could even be generic GUIs for it. On 12/24/2015 09:18 AM, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: > John Doty wrote: >> >I want to liberate users, not control them. > The argument doesn't hold because users must learn the .sch format > in order to work with it by hand. This remains true for any format. > > One important point is that reusing any existing representation makes > it more likely for users to already be familiar with that format or > language, as opposed to the 0 probability for gEDA-proprietary (open) > formats. What effort level is it going to be to keep using a .sch file as well as SQL and keep them in sync? By sync'd I mean every read of .sch updates the SQL, and every change to SQL writes to the .sch file. On 12/24/2015 04:58 PM, John Doty wrote: > Except that records delimited by newlines containing fields delimited by whitespace is a far more common and transparent convention than others. I have to agree with that feeling. On 12/25/2015 03:13 PM, John Doty wrote: > I’m not talking about pcb. I’m talking about geda-gaf. Geda-gaf is a much cleaner design. The pcb format doesn’t even represent a > proper model of what a printed circuit board is. Not talking about PCB doesn't solve many wants for very many people, so I want to talk about PCB, but yeah, its data model is spaghetti, and needs rework.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |