X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Fri, 3 Jul 2015 18:11:24 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: "Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] gEDA/gschem still alive? In-Reply-To: Message-ID: References: <1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de> <20150703030409 DOT 32398 DOT qmail AT stuge DOT se> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 Fri, 3 Jul 2015, Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: >You also have the big issues like the choice of scheme as gEDAs scripting >language and the gEDA file formats. Is there anything to gain by changing >and if so then what would be better and how do we transition? I feel your pain. FYI, earlier in this thread I mentioned a project of mine that makes it trivial to write netlisters (and in general, any exporter that requires the attributes only, and not the graphical stuff) in any language that can read text or xml or json or lihata. Even if this does not solve the problem some people have with scheme, at least it solved my problem about easy exporting and glue-making towards other tools and flows without having to do scheme. Regards, Igor2