delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Recipient: | geda-user AT delorie DOT com |
Message-ID: | <52026104.2090004@sonic.net> |
Date: | Wed, 07 Aug 2013 08:00:20 -0700 |
From: | Dave Curtis <davecurtis AT sonic DOT net> |
User-Agent: | Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 |
MIME-Version: | 1.0 |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] libgeda Python bindings? |
References: | <51DCEE37 DOT 9040303 AT sonic DOT net> <alpine DOT DEB DOT 2 DOT 10 DOT 1307101421060 DOT 5186 AT home DOT local> <51DD9F48 DOT 90908 AT sonic DOT net> <alpine DOT DEB DOT 2 DOT 10 DOT 1307102353160 DOT 4392 AT home DOT local> <51DED0D4 DOT 2020705 AT sonic DOT net> <alpine DOT DEB DOT 2 DOT 10 DOT 1308071457340 DOT 5268 AT home DOT local> |
In-Reply-To: | <alpine.DEB.2.10.1308071457340.5268@home.local> |
Reply-To: | geda-user AT delorie DOT com |
On 08/07/2013 06:20 AM, Roland Lutz wrote: > A short update for the Python bindings/translation: > > I tried both ways (creating a Python wrapper using swig, and > translating the relevant parts of libgeda to Python) and found it to > be much more difficult than expected. The main problems I experienced > are: > > 1. The gschem GUI code is not cleanly separated from the libgeda code; > in fact, about half of libgeda is dealing with GUI issues. > > 2. There is some semi-working (e.g., no arcs) support for SVG paths > which has been implemented by copying and adapting parts of rsvg. > > 3. The bounding box of text objects can only be determined using the > Cairo renderer. (This is the main reason why libgeda has to know > about TOPLEVEL contexts.) Extracting this functionality from the > renderer is not practical. > > 4. .sch/.sym files can only be parsed correctly after executing the > configuration files. (I consider this a major anti-feature.) > > I'm still working an the Python issue, but with somewhat less > priority. Maybe I'm going to remove these features at the price of > compatibility; I'm not sure yet. > > Roland > Thanks for the update. It answers several questions for me. -dave
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |