On Mon, Aug 20, 2012 at 04:04:55PM -0500, Dick Hollenbeck wrote:
> If this is repeatable from one spin to the next on any given board, I see
> this having
> great potential to achieve better consistency, and with less human error,
> than what is
> currently achievable.
Also means less than 30 mi
I will be short: awesome!!!
Enviado desde un móvil
El 20/08/2012, a las 23:04, Dick Hollenbeck escribió:
> On 08/20/2012 12:02 PM, Lorenzo Marcantonio wrote:
>> # We have just generated 21 plotfiles with a single script
>
> You so freely give away credit. :)
>
>
>
> Take a bow, please.
>
On 08/20/2012 12:02 PM, Lorenzo Marcantonio wrote:
> # We have just generated 21 plotfiles with a single script
You so freely give away credit. :)
Take a bow, please.
If this is repeatable from one spin to the next on any given board, I see this
having
great potential to achieve better consi
On Mon, Aug 20, 2012 at 08:54:09PM +0200, jean-pierre charras wrote:
>
> The actual size when printed depends on paper size, margins...
Another itchy point, paper size and margin:P 10mm or 20mm, with or
without filing margin and that's only scraping the issues
*I* know that, people with quality a
Le 20/08/2012 20:28, Lorenzo Marcantonio a écrit :
Is there a reason for eeschema to only have imperial grids? (probably
because internally works in mils?)
There are people which would like to work in metric in eeschema, too
(with custom libs, obviously)
Lorenzo,
For a schematic tool, the gri
Is there a reason for eeschema to only have imperial grids? (probably
because internally works in mils?)
There are people which would like to work in metric in eeschema, too
(with custom libs, obviously)
--
Lorenzo Marcantonio
Logos Srl
___
Mailing li
OK, done the deed, it seems to work. There is one thing I'm still
undecided for, mostly for the user's convenience of use.
I attached a test script which showcases most of the features.
As you can see with the BOARD you can create a PLOT_CONTROLLER. The plot
controller contains the plot setting o
On 08/20/2012 05:41 AM, Kaspar Bumke wrote:
> That's the SWEET library right?
No, SWEET pertains only to the part descriptions, i.e. what you find in a
schematic library.
> Is that documented somewhere beyond the proposal?
The new schematic file format is in proposal form, and is an *.odt doc
That's the SWEET library right?
Is that documented somewhere beyond the proposal?
Any example files?
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-
On Mon, Aug 20, 2012 at 06:11:16AM -0400, Carl Rash wrote:
> Why not a context free grammar definition. It seems to me that the so-called
> parser is actually nothing but a character stream scanner.
> A formal definition would help in many ways.
The old file formats are being deprecated. The new o
I've done the scripted plotting patch and it substantially
works-as-advertised; now I'll just have to port it to the main branch
(not a lot of work usually). I'd expect to have a public patch tonight.
During test I've noticed/tought about a couple of things, mostly due to
my ignorance about python
Why not a context free grammar definition. It seems to me that the so-called
parser is actually nothing but a character stream scanner.
A formal definition would help in many ways.
-Original Message-
From: kicad-developers-bounces+crash=triad.rr@lists.launchpad.net
[mailto:kicad-develo
On Sun, Aug 19, 2012 at 04:22:33PM +0200, Edwin van den Oetelaar wrote:
> Should this not read "$EndSchematic\n"
> to be consistent?
Uhmm.. *maybe*
> It appears that during reading of the file just "$End" is matched.
Exactly, so in practice it doesn't matter XD eeschema parser is easy to
please
13 matches
Mail list logo
