X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: Re: [geda-user] pcb-rnd feature poll: please vote Date: Sat, 25 Jul 2015 17:09:49 +0200 Lines: 89 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: a89-182-126-155.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com gedau AT igor2 DOT repo DOT hu wrote: I'll reorder according to my prefererences: > 1. {large} merge pcb-gpmi in pcb-rnd: scripting within pcb, using > 10 different languages (includes python, perl, awk, lua and guile) > Languages (and the dependencies they mean) are all optional. The ability to actually apply scripting to parts of the layout process is potentially huge. However, there needs to be an eco system of documentation and user provided examples to actually reap the benefits. > 2. {large} resurrect the win32 port - only if there are volunteer > windows testers There is a number of geda users at my day-work who prefer to do their electronics projects on windows rather than set-up and get used to a linux desktop just for this application. (They are sort of hard-locked into windows for their main tasks because of certain large CAD and science packages -- SolidWorks, Comsol, MathCAD, ...) You may remember that we even compiled a ready to use windows installer back when geda still cross compiled successfully. I'd cater a windows port to these users for testing. A prerequisite would be that there is full compatibility with standard pcb files on file format level. The reason I did not put the windows port on the top of this list is, the lack of transparency. If I remember correctly, the introduction of openGL triggered you to fork your own version of pcb. So I guess, there is no road to a transparency enabled version of pcb-rnd, be it in linux or windows. > 5. {small} UI: component dialog: filter by component tags, not only > by name I see only weak reason to use the chooser in pcb in the first place. Footprints are chosen in the schematic. I only use chooser dialogue in pcb as a catalogue to see the what is available. This is of course a bit of a crutch which is only necessary because gschem lacks proper UI mechanisms to scan the library of footprints. > 3. {small} UI: drill adjust: set drill and/or ring to current style > individually or all pins on a component Never felt the need for this. rings and holes should be set to sensible values in the footprint file. > 3. {small} UI: trace length calculation and display I don't do enough high speed circuitry to feel the need. > 4. {small} UI: be able to manually change text line width What use case would benefit from this? > 6. {medium?} CORE: clear poly should be a per layer flag (on each > objects); so that a line can clear poly on solder-gnd but join > solder-pwr This would break file level compatibility with mainstream pcb. As such it would make pcb-rnd, or t least this feature unusable for me. > 7. {medium?} CORE: optional inverse silk or copper text: draw a fill > rect around the text and make the text a cutout of this fill rect. When done in a way that is compatible with mainstream pcb, I'd put this into the nice-to-have-department. > 8. {small} BUILD: menuconfig and a config file for scconfig low priority for me. > 9. {medium} HID: resurrect the lesstif HID (pcb-rnd supports gtk at > the moment) The few times I looked at the lesstif version, did not make me like it.