ID: | 288 |
From: | ge...@igor2.repo.hu |
Date: | Sat, 17 Dec 2016 06:04:53 +0100 (CET) |
Subject: | Re: [pcb-rnd] gsch2pcb-rnd bugs and refactoring |
in-reply-to: | 287 from James Battat <jb...@wellesley.edu> |
replies: | 289 from James Battat <jb...@wellesley.edu> |
On Fri, 16 Dec 2016, James Battat wrote: >Hi folks, >Are there downsides to using the ?import schematics? option in pcb-rnd (or pcb), >as opposed to gsch2pcb(-rnd)? Conceptually no. It's the GUI user vs. Makefiles. Evan and I are more the Makefile type of users so we prefer gsch2pcb-rnd. Technically there are problems with both paths at the moment, but I am working on fixing them. Currently they use totally different code. gsch2pcb-rnd is broken because it duplicates too much of pcb-rnd code; the import schematics is broken because it does too much in scheme instead of in C, which makes it too dependent on gnetlist and harder to maintain/fix. At the end, we will have the same code behind both features, while the UI won't change much. >I find "import schematics? to be a very clear, intuitive, single step >operations, run from within the (usually already open) pcb-rnd program. >No need to run a command line script, followed by a series of in-GUI >commands (e.g. import the updated netlist). (gsch2pcb-rnd will probably become single step too, today, at least for the GUI-part). >That said, my projects are really basic and so there may be more >subtle/complex tasks that ?import schematics? cannot handle? Not really - in mainline I think the policy is that gsch2pcb is abandoned and they recommend using import schematics, so in that sense it's the opposite, gsch2pcb should be the less capable one. I want to provide both paths, with equally good services. Regards, Igor2
Reply subtree:
288 Re: [pcb-rnd] gsch2pcb-rnd bugs and refactoring from ge...@igor2.repo.hu
289 Re: [pcb-rnd] gsch2pcb-rnd bugs and refactoring from James Battat <jb...@wellesley.edu>
292 Re: [pcb-rnd] gsch2pcb-rnd bugs and refactoring from ge...@igor2.repo.hu
293 Re: [pcb-rnd] gsch2pcb-rnd bugs and refactoring from James Battat <jb...@wellesley.edu>