> # maybe we have an author with licensing issues ?
> author = "me, myself and I"
> use-license ="unlimited2 ;-) "
> dist-license = "LGPL"
Well, we could carry forth the Attribute list:
attributes = (
author = "foo"
license = "..."
)
but really, you coul
Hi DJ,
On Wed, 2008-06-11 at 11:32 -0400, DJ Delorie wrote:
> > ?? which is what?
>
> The format we use for pcb-menu.res and gpcb-menu.res. It's a
> heirarchical text format with tagging and grouping. Semantically,
> it's like XML, but without all the heavy baggage that comes with XML.
> It all
> ?? which is what?
The format we use for pcb-menu.res and gpcb-menu.res. It's a
heirarchical text format with tagging and grouping. Semantically,
it's like XML, but without all the heavy baggage that comes with XML.
It allows forward compatibility and third-party expansion, is easy to
parse, a
> Now, of course, old lex/yacc hands will point out that this kind of
> communication is dangerous, since the parser looks ahead,
The parser looks ahead to scan tokens, which means you need to
recognize all the tokens in the parser, not half in the parser and
half in the lexer. It will reduce r
> One of these days we should just switch to the resource file format
> and be done with it. Then you could fairly easily (I think) let the
> current default units basically be set as you go down a tree.
I still have "layer types megapatch" and "blind/buried vias" on my
plate too, I'll probably
Dan McMahill wrote:
> One of these days we should just switch to the resource file format
?? which is what?
-dave
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
DJ Delorie wrote:
>
>> As a handy extension, it would be convenient to be able to specify a
>> default unit that applies to an entire footprint, so that a unit of
>> "mm" or whatever didn't have to appear after every number.
>
> That would be tricker because you'd have to have communication betwe
DJ Delorie wrote:
>> DJ is fast on the draw... by the time I saw this thread he already
>> has a patch. I was thinking of doing something similar. This will
>> be quite handy.
>
> :-)
>
>> As a handy extension, it would be convenient to be able to specify a
>> default unit that applies to an en
> DJ is fast on the draw... by the time I saw this thread he already
> has a patch. I was thinking of doing something similar. This will
> be quite handy.
:-)
> As a handy extension, it would be convenient to be able to specify a
> default unit that applies to an entire footprint, so that a un
DJ Delorie wrote:
>> - it is difficult for me (and no one did/do it),
>
> Try this. It allows "um", "mm", "mil", or "in" as suffixes after
DJ is fast on the draw... by the time I saw this thread he already has a
patch. I was thinking of doing something similar. This will be quite
handy.
As
> given the 0.01 mill base unit I would like to have a grid of 4 mills.
:SetValue(grid,4,mil)
You can create a local pcb-menu.res (or gpcb-menu.res) in ~/.pcb and
add that to the grid list.
___
geda-user mailing list
geda-user@moria.seul.org
http://w
given the 0.01 mill base unit I would like to have a grid of 4 mills.
This would allow 4 mill traces and 4 mills of clearance between traces.
The grid error for 50 mill pitch components would be no greater then 2
mills the grid error for 1mm devices would be under 48 microns (~1.8
mills)
for the
> - it is difficult for me (and no one did/do it),
Try this. It allows "um", "mm", "mil", or "in" as suffixes after
floating point numbers (no space between), anywhere an integer is
otherwise allowed. Example:
Line[1.5mm 0 1.5mm 0.5 in 1mil 2mil "clearline"]
Index: parse_l.l
=
> What unit should we define for PCB default units?
For compatibility, the default (no units specified) should remain 0.01
mil.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
I would like a base unit that supports both metric and English units and
that allows me to pick a grid such that the pads of metric parts and
English parts always center (with a reasonable tolerance) upon the grid
Allowing me to snap traces to the grid for boards with both types.
Steve Meier
On
Steven -
On Tue, Jun 10, 2008 at 02:57:33PM -0700, Steven Michalske wrote:
> Remember the high school science teacher docking points for not using
> units?
It's burned into my skull!
> What unit should we define for PCB default units?
> They are mill/100, one hundred thousandth of an inch, or
This allows for nm or feet, I like it! add units not confusion!
Remember the high school science teacher docking points for not using
units?
What unit should we define for PCB default units?
They are mill/100, one hundred thousandth of an inch, or a dmil;
deci-mil ha ha a pun for a uni
DJ Delorie wrote:
>> So I made a really simple patch of parse_y.y, by which I can use um
>> (micrometer) to specify the items. The format is same as in "[" "]" case
>> but the specifier is "<" and ">". All the other thing is the same.
>
> Please, no more "syntax determines content" patches. If
> So I made a really simple patch of parse_y.y, by which I can use um
> (micrometer) to specify the items. The format is same as in "[" "]" case
> but the specifier is "<" and ">". All the other thing is the same.
Please, no more "syntax determines content" patches. If you want um,
let it pars
Dear All,
Nowadays I find lot of datasheets, in which the dimensions are appear
only in metric system. I don't know whether any of you interested in
creating footprints in mm instead of mil or mil/100, but it was a
nightmare for me to calculate every value from metric to English units.
So I
20 matches
Mail list logo
