Re: gEDA-user: pads, mask and solder paste
Kai-Martin Knaak wrote: The solder paste pattern emitted by PCB seems to coincide exactly with the copper of the pads. This is a reasonable default. But there are use cases where a different solder paste size is better. 1) A pad completely covered with solder mask should not receive any solder paste. This kind of pads are useful a way to achieve tracks in footprints. Add the nopaste flag 2) Pads partly covered by solder mask should receive a solder mask pillow that corresponds to the hole in the mask, rather than to the pads copper dimensions. Such partly covered pads are useful as a heat sink. My way is to make the main pad nopaste and add smaller pads within the bigger pad. And my own question to add: is there a way to shrink all solder paste openings, say, 5%? Cory ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 02:29:40AM +0100, Kai-Martin Knaak wrote: Kai-Martin Knaak, can I ask you to start the wiki page on an appropriate place? You seems to have already done something on the wiki(s). I started a page in the developers brainstorming corner of the wiki. To get things started, I added some issues from the top of my head: http://geda.seul.org/wiki/geda:pcb_layers Great. I will have a look and try to keep track with it. Martin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 04:04:21AM +0100, Kai-Martin Knaak wrote: Martin Kupec wrote: It is not possible to unmask general shape. There is the possibility with converting rectangle to pad, but that is probably not the best way. Is the right way to have a layer of negative soldermask. Pads and pins will be there automatically and you would be able to add any shape there? Or something else is better? IMHO, negativeness should be a property of objects, not something specific to a layer. I'd like to draw positive and negative lines on anything, be it copper, or mask. Ok. So layer would have object and object has a property if it is positive or negative. Negative from nothing will endup being nothing. Positive in positive will endup in positive. And by defaul a layer would be an empty sufrace(like one big negative rectangle)? Or do we need a special treatment for some layers. Martin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Advanced grids in GTK Pcb
Am 14.02.2011 um 07:37 schrieb jpka: Now i know my work is welcomed, so i will try to do it according to your suggestions. Does the grid still change in case you swap the measurement unit? This behaviour should probably go away. Switching to mm doesn't neccessarily mean you want a mm-related grid. For the more general target, I think it would be a good idea to have a grid-free future in mind. It's not neccessary to do that immediately, but one day the grid-based approach might be replaced with one using alignment functions, similar to how general drawing applications work these days. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Am 13.02.2011 um 22:32 schrieb Martin Kupec: My question is: What is impossible to achive with the current implementation and what would one like to achive? So far I couldn't find a select by layer function. Now, if layers could be hidden individually, and not only in groups, that would almost equal a select all. Perhaps I missed something, but that enforced hiding in groups should probably be optional. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Krzysztof: On Fri, Feb 11, 2011 at 08:38:47AM +0100, Karl Hammar wrote: ... Attached patch corrects that. Can you file the patch on the tracker so it isn't forgotten? http://bugs.launchpad.net/geda/+filebug The patches of (numslots=0 thing, oc/oe drc2): http://www.seul.org/pipermail/geda-user/2010-September/049354.html http://www.seul.org/pipermail/geda-user/2011-February/052384.html are so small and obvious. Do we really need the overhead of a bug tracker for them? But I wouldn't mind if you upload them. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Karl Hammar wrote: The patches of (numslots=0 thing, oc/oe drc2): http://www.seul.org/pipermail/geda-user/2010-September/049354.html http://www.seul.org/pipermail/geda-user/2011-February/052384.html are so small and obvious. Do we really need the overhead of a bug tracker for them? Well, developers of geda and/or pcb, those with write access to the source, tend to ignore patches on the mailing list. That said, patches on the tracker have been on hold indefinitely in the past, too. To change this habit, was one of the motivations for the with the switch from sourceforge to launchpad (hint, hint...) At least patches can be more easily retrieved on the trackers. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 11:03:24AM +0100, Markus Hitter wrote: Am 13.02.2011 um 22:32 schrieb Martin Kupec: My question is: What is impossible to achive with the current implementation and what would one like to achive? So far I couldn't find a select by layer function. Now, if layers could be hidden individually, and not only in groups, that would almost equal a select all. Perhaps I missed something, but that enforced hiding in groups should probably be optional. Ok. The possibility to show/hide just one layer seems reasonable. I have a little difficulty. How to get wiki login? Or is it just for developers? Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pads, mask and solder paste
Cory Cross wrote: 1) A pad completely covered with solder mask should not receive any solder paste. This kind of pads are useful a way to achieve tracks in footprints. Add the nopaste flag Thanks. I forgot about this one. ---)kaimartin(--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Kai-Martin: Karl Hammar wrote: The patches of (numslots=0 thing, oc/oe drc2): ... are so small and obvious. Do we really need the overhead of a bug tracker for them? Well, developers of geda and/or pcb, those with write access to the source, tend to ignore patches on the mailing list. That said, patches on the tracker have been on hold indefinitely in the past, too. One dev have said [1] we should nag them about theese patches. To change this habit, was one of the motivations for the with the switch from sourceforge to launchpad (hint, hint...) At least patches can be more easily retrieved on the trackers. I understand the hint etc., but we should have one or more person that could actually *commit* thoose simple fixes, either at the official or a seperate site. I could possible set up a git repo for thoose simple fixes. Do anyone want to join? Regards, /Karl Hammar [1] http://www.seul.org/pipermail/geda-user/2009-October/021044.html --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pads, mask and solder paste
And my own question to add: is there a way to shrink all solder paste openings, say, 5%? I use a perl script to build a paste.pcb out of the working pcb, which has objects on a copper layer that correspond to the calculated paste openings from the original. That way, the perl script can apply all the adjustment rules I need for that particular board. PCB itself has no way of controlling the paste output, other than the nopaste flag. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
http://geda.seul.org/wiki/geda:pcb_layers I already have a master PCB Roadmap at http://geda.seul.org/wiki/pcb:roadmap It already has a Wish List in it, and already has a bullet for a layer design update. Please stop making new pages for every new individual idea when there's already pages for them. Also, please keep all the pcb-specific pages in the pcb: namespace, not the geda: namespace. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Ok. So layer would have object and object has a property if it is positive or negative. Negative from nothing will endup being nothing. Positive in positive will endup in positive. You can't have both positive and negative drawing objects in a single layer without prioritizing them, and once you prioritize them, you then have more layers! So, might as well segretate objects into positive-acting layers and negative-acting layers, and let the stackup manage the priorities. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
At least patches can be more easily retrieved on the trackers. When I have time to work on PCB (rare though that is), usually the FIRST thing I do is go through the patches in the tracker and apply whatever I can. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 12:49:50PM -0500, DJ Delorie wrote: Ok. So layer would have object and object has a property if it is positive or negative. Negative from nothing will endup being nothing. Positive in positive will endup in positive. You can't have both positive and negative drawing objects in a single layer without prioritizing them, and once you prioritize them, you then have more layers! So, might as well segretate objects into positive-acting layers and negative-acting layers, and let the stackup manage the priorities. Seems reasonable. That is what I was thinking at the beggining. I was not thinking yet, how to implement suggested behaviour. But this is exactly what is needed...to brainstorm what is possible/impossible and how keep it simple. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Martin Kupec wrote: I have a little difficulty. How to get wiki login? You have to ask Ales Hezda for a login (ahvezda AT geda.seul.org). http://geda.seul.org/wiki/#about_this_wiki Martin is not the first to miss this crucial bit of information. Any objections against moving it to the top of the page? ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 08:14:27PM +0100, Kai-Martin Knaak wrote: Martin Kupec wrote: I have a little difficulty. How to get wiki login? You have to ask Ales Hezda for a login (ahvezda AT geda.seul.org). http://geda.seul.org/wiki/#about_this_wiki Ok. I will ask him. Martin is not the first to miss this crucial bit of information. Any objections against moving it to the top of the page? What would probably help. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Ok. But I think, that still the best would be to have a separete page. Or perhaps a separete section in the roadmap. Note that I have a partial patch for this work already, which adds layer type flags to the layer data structre in PCB. The file format already allows an optional string-flags in the layer line for this purpose. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Feb 14, 2011 at 02:27:58PM -0500, DJ Delorie wrote: Ok. But I think, that still the best would be to have a separete page. Or perhaps a separete section in the roadmap. Note that I have a partial patch for this work already, which adds layer type flags to the layer data structre in PCB. The file format already allows an optional string-flags in the layer line for this purpose. Great. Where can one get that patch? Martin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Great. Where can one get that patch? http://archives.seul.org/geda/dev/Jul-2007/msg00221.html ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Hi, another set of questions needed to be answered before I can start any real work. Or better a set of thought how to do it. Current state: One physicaly connected surface is called layer group. What is called layer is something that one can work on and will end up in some surface layer group. There are special Layers called silk, ratlines, mask, outline,.. Proposed state: I think it is common to call layer one electricaly connected sufrace. Cannot we come up with some other name for layer, so we can leave layer for one electricaly connected surface? A problem with user configurable layers: If there are more (ie. silk) layers, where to put the silk layer of an footprint? Should we somehow link cooper layer and silk layer? What if we link more than one silk layer to cooper layer? Or do we want to have some default silk and cooper layer and move all footprints from that one to desired one? One of the problems someone wants to solve is to be able to put outline of an footprint to one silk layer and refdef to another. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Current state: One physicaly connected surface is called layer group. What is called layer is something that one can work on and will end up in some surface layer group. There are special Layers called silk, ratlines, mask, outline,.. Proposed state: I think it is common to call layer one electricaly connected sufrace. Cannot we come up with some other name for layer, so we can leave layer for one electricaly connected surface? We've discussed this before, came up with something like drawing sheet vs physical layer. If there are more (ie. silk) layers, where to put the silk layer of an footprint? Should we somehow link cooper layer and silk layer? What if we link more than one silk layer to cooper layer? Aside from numbering layers from 1 .. N, there are symbolic names for top, inner, and bottom layers. Footprints use symbols names, they're mapped to numeric layers as appropriate for each board. That doesn't mean footprints *can't* use numeric layers, but they're more reusable if they don't. Each drawing layer has a record of which physical layer it corresponds to (if at all), so you could (for example) assign a silk layer to one of your internal layers, despite that not making sense. However, assigning a documentation layer to an inner layer *might* make sense. Or do we want to have some default silk and cooper layer and move all footprints from that one to desired one? The stackup needs to understand the concept of inner and outer layers at least, so it can map a library footprint to a specific element. Of course, I leave open what outer layer means, esp in the context of flex cables where a given layer might be an inner layer over here, and an outer layer over there... One of the problems someone wants to solve is to be able to put outline of an footprint to one silk layer and refdef to another. Again, we need to have some way of mapping a well-known set of symbolic names to specific physical layers. For text, perhaps we adopt gschem's named attribute method? So we have some text *named* refdes, with *value* of R4, that happens to be on layer topsilk:refdes - it looks for a topsilk:refdes mapping rule, and if it doesn't find one, looks for a topsilk mapping rule, etc. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
DJ Delorie wrote: http://geda.seul.org/wiki/geda:pcb_layers I already have a master PCB Roadmap at http://geda.seul.org/wiki/pcb:roadmap It already has a Wish List in it, and already has a bullet for a layer design update. Martin did not ask for a general pcb wish list, but for an in depth discussion of a single topic. Please stop making new pages for every new individual idea when there's already pages for them. I didn't even start. The roadmap is definitely not a page for brainstorming about layer issues. Instead, the kind of single topic page Martin asked for, matches the ones listed in http://geda.seul.org/wiki/#work-in-progress_and_or_brainstorming Also, please keep all the pcb-specific pages in the pcb: namespace, not the geda: namespace. You mean, unlike: http://geda.seul.org/wiki/geda:pcb-quick_reference http://geda.seul.org/wiki/geda:pcb_footprints http://geda.seul.org/wiki/geda:pcb_tips http://geda.seul.org/wiki/geda:faq-pcb http://geda.seul.org/wiki/geda:pcb_funding_sow http://geda.seul.org/wiki/geda:pcb_mp http://geda.seul.org/wiki/geda:pcb_footprint_naming_conventions What pages are in the pcb hierarchy anyway? The root http://geda.seul.org/wiki/pcb:start does not exist. A search for pcb in the wiki returns only the roadmap in pcb name space. Everything else is in top name space, or in the geda name space. http://geda.seul.org/wiki/?do=searchid=pcb If separation of name spaces is an important issue, I suggest to start with the pages linked above. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
On Mon, Feb 14, 2011 at 02:39:38PM +0100, Karl Hammar wrote: To change this habit, was one of the motivations for the with the switch from sourceforge to launchpad (hint, hint...) At least patches can be more easily retrieved on the trackers. I understand the hint etc., but we should have one or more person that could actually *commit* thoose simple fixes, either at the official or a seperate site. I could possible set up a git repo for thoose simple fixes. Do anyone want to join? In what way a git repo would be better than separate patches? For testing? Each separate set of changes would still have to be reviewed, and I suppose that (together with the discussion/suggestion of improvements) constitutes the main effort for accepting changes to the main source tree. -- Krzysztof Kościuszkiewicz Simplicity is the ultimate sophistication -- Leonardo da Vinci ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
You mean, unlike: Yes. If separation of name spaces is an important issue, I suggest to start with the pages linked above. Sounds great. Go for it. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
In what way a git repo would be better than separate patches? A separate git repo would make it harder for me to review patches. I'm much more interested in the history and discussion of the patch, than in the actual patch itself, and if there's anything wrong with the patch, LP/SF is a better way to manage those issues than git. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
DJ Delorie wrote: If separation of name spaces is an important issue, I suggest to start with the pages linked above. Sounds great. Go for it. Sorry, I don't feel separation of name spaces is a priority issue. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, 2011-02-14 at 04:04 +0100, Kai-Martin Knaak wrote: Martin Kupec wrote: It is not possible to unmask general shape. There is the possibility with converting rectangle to pad, but that is probably not the best way. Is the right way to have a layer of negative soldermask. Pads and pins will be there automatically and you would be able to add any shape there? Or something else is better? IMHO, negativeness should be a property of objects, not something specific to a layer. I'd like to draw positive and negative lines on anything, be it copper, or mask. Gerber output only really works well if you a layer which is made up of negative or positive primitives. Other tools I've encountered use negative layers for things like planes (where tracks define the clearance separation between planes). The difficulty is that you can't easily have this bit as negative + this bit as positive. I guess we can do better than other tools in some cases, but the output might be a lot more polygon-y than would be otherwise achievable with a pure positive or negative layer. I suppose if it matters, we could let the user emit output in either form. (Assuming objects on the layer make that possible). Fallback to polygons could always work I guess. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, 2011-02-14 at 22:06 +0100, Kai-Martin Knaak wrote: DJ Delorie wrote: If separation of name spaces is an important issue, I suggest to start with the pages linked above. Sounds great. Go for it. Sorry, I don't feel separation of name spaces is a priority issue. KMK - I think I emailed you off-list with my brief analysis of the spider-web which is our wiki. From a snapshot a few months ago, I started playing around with moving content about and making much more extensive use of hierarchy within the wiki (ensuring we have a sub-index page for each level of hierarchy). By installing the include plugin for docuwiki, I was able to re-construct some of our current massive link pages with includes of neat sub-section contents lists. Obviously we'd have to re-do this work based on a non-out of date wiki snapshot, but I think we should look at it at some point. Best wishes. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
2011/2/14 DJ Delorie d...@delorie.com: A separate git repo would make it harder for me to review patches. I'm much more interested in the history and discussion of the patch, than in the actual patch itself, and if there's anything wrong with the patch, LP/SF is a better way to manage those issues than git. github's pull request/code review system works pretty well for discussing a patch (https://github.com/features/projects/codereview). I also like the way Google Project hosting does code reviews, especially the voting system. I'm not sure if github has something similar. Thought I'd throw that out there, even though we should probably just stick to LP for everything since we just moved over to it. (Although I'm still unclear how to differentiate bugs and patches in the LP tracker) I think maybe what Karl was getting at was a group of Junior devs that commit to a repo to indicate they have looked at and agree with the patch. The senior dev, if he trusts the junior dev's judgement, issues a few git commands and the patch is in. Perhaps now that we are on LP, the ideas in this thread are more realizable: http://www.seul.org/pipermail/geda-user/2010-March/045968.html Maybe make an official LP tag of vetted or something that junior developers can add to a patch, allowing a senior dev to concentrate on those first, not spending on time on patches that need work. Jared ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, 2011-02-14 at 22:16 +0100, Stephan Boettcher wrote: Kai-Martin Knaak k...@lilalaser.de writes: Martin did not ask for a general pcb wish list, but for an in depth discussion of a single topic. A discussion where most people cannot contribute? What is wrong with this list for discussion? Wiki pages aren't a discussion - they are a forum for collaborative editing, so can be far more suited to design brainstorming than a linear (or threaded) email conversation. Everyone who wants one can get a Wiki login - you just have to request one from Ales to help avoid the spammers. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
On Mon, 2011-02-14 at 13:31 -0800, Jared Casper wrote: Maybe make an official LP tag of vetted or something that junior developers can add to a patch, allowing a senior dev to concentrate on those first, not spending on time on patches that need work. Sounds like a good idea - call it patch-tested or something? We should probably set up a team as a place-holder to get assigned as a job-list for patches which are ready to be pushed. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Karl Hammar wrote: I understand the hint etc., but we should have one or more person that could actually *commit* thoose simple fixes, ack. Patches are the result of non-trivial efforts. The contributers deserve some attention. Even a short note, that the patch will not applied is way better than let the patch rot until forever and a day. IMHO, this kind of ignorance is a sure way to drive away potential developers. See bug 699454 by Ineiev: https://bugs.launchpad.net/pcb/+bug/699454 The patch was filed in October 2008. danmc asked for some clarification in November. Ineiev responded in December and updated the patch. In February somebody not logged in suggested to split the patch into smaller blobs. Ineiev resonded the next day and provided a series of patches two weeks later in March 2009. Then nothing until today. either at the official or a seperate site. I could possible set up a git repo for thoose simple fixes. Do anyone want to join? Not another semi fork, please. It is already a pain to have the OpenGL only in Peter Cliftons version. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Stephan Boettcher wrote: A discussion Well, I didn't mean discussion in the literal sense of persons talking. More like a structured collection of thoughts ideas. where most people cannot contribute? Ask Ales (ahvezda AT geda.seul.org) for a login and you are in. What is wrong with this list for discussion? It is a real discussion. The focus wanders on and off topic. And there is no comprehensive summary. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Best use of my time? [WAS: Re: Open Collector Error Checking]
On Mon, 2011-02-14 at 22:39 +0100, Kai-Martin Knaak wrote: Karl Hammar wrote: I understand the hint etc., but we should have one or more person that could actually *commit* thoose simple fixes, Myself, Peter-B, DJ, Dan, Ales, Ben Jackson, Stuart Brorson, Anthony Blake We all seem to be either busy, or just not familiar enough with the code in question to make this an easy problem to fix. Reviewing patches isn't its-self trivial though, as to do it well often requires an intimate knowledge of the code-base - perhaps deeper than the patch submitter may have had. (That is - if we wish to spot any potential system-level gotchas). I won't commit patches I view to be of low quality, but I do try and address this with the submitter. For cases where I don't know enough - I am prepared to give the submitter the benefit of the doubt if they seem switched on and the code looks good. Just prod me to do that.. We can always revert if it turns out to be a bad change. ack. Patches are the result of non-trivial efforts. The contributers deserve some attention. Even a short note, that the patch will not applied is way better than let the patch rot until forever and a day. IMHO, this kind of ignorance is a sure way to drive away potential developers. I fully agree, and I'm trying my best where I can, but I have a lot of much more critical things taking up my life at the moment. I'm sure this applies to many other of the devs too. See bug 699454 by Ineiev: https://bugs.launchpad.net/pcb/+bug/699454 The patch was filed in October 2008. danmc asked for some clarification in November. Ineiev responded in December and updated the patch. In February somebody not logged in suggested to split the patch into smaller blobs. Ineiev resonded the next day and provided a series of patches two weeks later in March 2009. Then nothing until today. The last comment on that bug was me doing a bit of mass-triage on bugs with patches attached. For our sins, if people don't keep pushing issues - they will sadly get forgotten. My triaging by adding the tag wasn't indicating that I'd paid a great deal of notice to what the patches were in detail, or whether I could commit them right away. A more thorough triage would have done that though, yes. Perhaps we should just give Ineiev commit access - this would be a way of addressing the issue in this particular case. His patches are generally good, and we'd not be in the way then. He is known to the community, so would probably be approved without much hesitation. Ineiev - fancy requesting commit access? (I approve - but you'll have to ask Dan / DJ, and possibly Harry Eaton). Not another semi fork, please. It is already a pain to have the OpenGL only in Peter Cliftons version. I'll fix it - sometime ;) Right now I've got PhD work which I'm failing at (I'm on medical leave due to being depressed), and some part-time paid work trying to avoid going broke (which is otherwise imminent) so I can keep paying the rent. My girlfriend lives ~2.5 hours drive away, and I do like to see her when I can (e.g. weekends), so add running a car to the list of expenses, and take weekends away from free time for paid work or gEDA activities. After a long list of personal problems, I'm trying to sort my life out - and that means less time for gEDA (where it doesn't overlap with paid work). Unfortunately (as I love gEDA), the times I'm working most on gEDA have often corresponded to the times where I've been most depressed, or least effective with time management in other aspects of my life. I would love to get the PCB+GL stuff finished and merged soon - but I'm trying to keep sensible hours, manage a decent work/life balance and generally sort things out. I will schedule some gEDA time periodically, but there has to be a balance between patch-review and progress on PCB +GL. I can do both, but there will be a trade-off due to the finite time I can spend. I'm hoping that I've been able to invigorate some interest in the project recently, and I see that we have several up and coming new developers who might be able to take the torch for a while - in terms of driving gEDA forward. FWIW... one of the work projects I'm doing at the moment will hopefully benefit gEDA and PCB. I hope to be able to talk more about that if and when the details of the project. are sorted out. Best regards, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Peter Clifton wrote: Maybe make an official LP tag of vetted or something that junior developers can add to a patch, allowing a senior dev to concentrate on those first, not spending on time on patches that need work. Sounds like a good idea - call it patch-tested or something? We should probably set up a team as a place-holder to get assigned as a job-list for patches which are ready to be pushed. There should probably be more active core developers in the first place. What is the process to become one? Who are candidates? ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pads, mask and solder paste
On Mon, Feb 14, 2011 at 8:08 AM, Kai-Martin Knaak k...@lilalaser.de wrote: 2) Pads partly covered by solder mask should receive a solder mask pillow that corresponds to the hole in the mask, rather than to the pads copper dimensions. Such partly covered pads are useful as a heat sink. This patch against GIT head does what you describe: --- a/src/draw.c +++ b/src/draw.c @@ -544,7 +544,10 @@ DrawEverything (BoxTypePtr drawn_area) || (!TEST_FLAG (ONSOLDERFLAG, pad) side == COMPONENT_LAYER)) if (!TEST_FLAG (NOPASTEFLAG, pad)) - DrawPadLowLevel (Output.fgGC, pad, false, false); + if (pad-Mask pad-Thickness) + DrawPadLowLevel (Output.fgGC, pad, true, true); + else + DrawPadLowLevel (Output.fgGC, pad, false, false); } ENDALL_LOOP; } I've only given this a quick test, it works for the S005.fp mentioned before. I'd appreciate it if other could check the patch to see if it causes problems in other areas. Limiting the paste size to min(Mask, Thickness) seems like a good idea, but can anyone think of a case where you'd actually want the paste opening to be larger than the solder mask opening ? Stephen ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Best use of my time? [WAS: Re: Open Collector Error Checking]
Right now I've got PhD work which I'm failing at (I'm on medical leave due to being depressed), and some part-time paid work trying to avoid going broke (which is otherwise imminent) so I can keep paying the rent. Do take care - I've had depression and know how debilitating it is. I really value your contributions to GEDA, and hope that your situation will improve soon! With best wishes for your well being, Stephen ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pads, mask and solder paste
Limiting the paste size to min(Mask, Thickness) seems like a good idea, but can anyone think of a case where you'd actually want the Can you add a check for a fully tented pad? I.e. if mask==0, don't draw anything? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Open Source Hardware (OSHW) Definition 1.0
http://freedomdefined.org/OSHW mentioned today by german heise magazin http://www.heise.de/newsticker/meldung/Open-Source-Hardware-Definition-veroeffentlicht-1189508.html ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Source Hardware (OSHW) Definition 1.0
Ideally, open source hardware uses . . . open-source design tools . . . The license may require that the design files are provided in fully-documented, open format(s). :-) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pads, mask and solder paste
On Tue, Feb 15, 2011 at 10:14 AM, DJ Delorie d...@delorie.com wrote:
Limiting the paste size to min(Mask, Thickness) seems like a good
idea, but can anyone think of a case where you'd actually want the
Can you add a check for a fully tented pad? I.e. if mask==0, don't
draw anything?
Sure.
--- a/src/draw.c
+++ b/src/draw.c
@@ -543,8 +543,13 @@ DrawEverything (BoxTypePtr drawn_area)
if ((TEST_FLAG (ONSOLDERFLAG, pad) side == SOLDER_LAYER)
|| (!TEST_FLAG (ONSOLDERFLAG, pad)
side == COMPONENT_LAYER))
- if (!TEST_FLAG (NOPASTEFLAG, pad))
- DrawPadLowLevel (Output.fgGC, pad, false, false);
+ if (!TEST_FLAG (NOPASTEFLAG, pad) pad-Mask 0L)
+ {
+ if (pad-Mask pad-Thickness)
+ DrawPadLowLevel (Output.fgGC, pad, true, true);
+ else
+ DrawPadLowLevel (Output.fgGC, pad, false, false);
+ }
}
ENDALL_LOOP;
}
I've given it a quick check, works fine for my current project (mixed
TH SMD, some SMD with mask opening smaller than copper area for
sinking heat).
Any other feedback ? I'll let this sit for a day or so, if there are
no further corrections or suggestions I'll then log it on LP.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Hi all, -Original Message- From: geda-user-boun...@moria.seul.org [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Stephan Boettcher Sent: Monday, February 14, 2011 10:17 PM To: gEDA user mailing list Subject: Re: gEDA-user: General Layers questions Kai-Martin Knaak k...@lilalaser.de writes: Martin did not ask for a general pcb wish list, but for an in depth discussion of a single topic. A discussion where most people cannot contribute? What is wrong with this list for discussion? -- Stephan Maybe this is a good opportunity to start using Blueprints on Launchpad, these can be linked to bugs, milestones and thus releases. AFAICT, these are for code specific write ups and ideas. This gives the roadmap a possible timeline (relative or absolute), date are not mandatory, I think the devs like to work without pressure of calender deadlines ;-). The positive side effect can be that it keeps traffic on both geda-dev and geda-user low, and ideas can be tracked for progress. Just my EUR 0.02 Kind regards, Bert Timmerman. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Collector Error Checking
Hi Peter, -Original Message- From: geda-user-boun...@moria.seul.org [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Peter Clifton Sent: Monday, February 14, 2011 10:34 PM To: gEDA user mailing list Subject: Re: gEDA-user: Open Collector Error Checking On Mon, 2011-02-14 at 13:31 -0800, Jared Casper wrote: Maybe make an official LP tag of vetted or something that junior developers can add to a patch, allowing a senior dev to concentrate on those first, not spending on time on patches that need work. Sounds like a good idea - call it patch-tested or something? We should probably set up a team as a place-holder to get assigned as a job-list for patches which are ready to be pushed. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) Maybe add a LP user geda-push and/or pcb-push (or geda-dev and/or pcb-dev), and assign to this user. Just my EUR 0.02 Kind regards, Bert Timmerman ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
