Re: [Kicad-developers] Boomerang with locale dependent entries in .kicad_pcb

2015-01-15 Thread Nick Østergaard
2015-01-16 3:19 GMT+01:00 LordBlick : > In response to a message written on 16.01.2015, 01:38, from LordBlick: > >> I just discovered that for some reason Pcbnew does not display complete >> zones in >> just designed project. >> Looking into project file: >>(layers >> -> (0 Gorna jumper) >>

[Kicad-developers] [PATCH] two minor fixes

2015-01-15 Thread Mark Roszko
First patch fixes the Save library file as dialog which had the library extension instead of library extension wildcard used. Second patch fixes a null termination in eeschema/cross-probing.cpp. The char array line is in block scope and is never preinitialized to all 0s. There's also no guarantee

Re: [Kicad-developers] Boomerang with locale dependent entries in .kicad_pcb

2015-01-15 Thread LordBlick
In response to a message written on 16.01.2015, 01:38, from LordBlick: I just discovered that for some reason Pcbnew does not display complete zones in just designed project. Looking into project file: (layers -> (0 Gorna jumper) -> (31 Dolna signal) (32 B.Adhes user) (33 F.Adhe

[Kicad-developers] Boomerang with locale dependent entries in .kicad_pcb

2015-01-15 Thread LordBlick
I just discovered that for some reason Pcbnew does not display complete zones in just designed project. Looking into project file: (layers -> (0 Gorna jumper) -> (31 Dolna signal) (32 B.Adhes user) (33 F.Adhes user) (34 B.Paste user) (35 F.Paste user) (36 B.SilkS user)

Re: [Kicad-developers] file version compatibility (optional tokens in s-expression files)

2015-01-15 Thread Tomasz Wlostowski
On 15.01.2015 23:40, Miguel Ángel Ajo wrote: > I was talking about Altium in my previous email, and I believe > the points you made are quite reasonable (in favor and against). Hi Miguel, Fully agree here. > > I also didn’t know about the measures of not saving the unchanged > defaults, which are

Re: [Kicad-developers] file version compatibility (optional tokens in s-expression files)

2015-01-15 Thread Miguel Ángel Ajo
I was talking about Altium in my previous email, and I believe the points you made are quite reasonable (in favor and against). I also didn’t know about the measures of not saving the unchanged defaults, which are quite neat. What about a flag in the loader parameters, disabled by default, but wh

Re: [Kicad-developers] The library tables wizard

2015-01-15 Thread Nick Østergaard
Ahh, I just found the place. I have attached a patch that removed the extra slash and the extra semicolon. This interface looks much nicer to choose from instead of the browser window. :) Also, on the same dialog/form as the "Github Libs List" the button called "Add FP Library entry" does nothing

Re: [Kicad-developers] The library tables wizard

2015-01-15 Thread Nick Østergaard
Hi Jean-Pierre To me it seems like you have a double semicolor on pcbnew/github/github_getliblist.cpp 104wxString urlPrefix = wxT( "https://"; ) + repo.GetServer() + wxT( "/" );; Aslo I geth the following error when trying to fetch. The problem is the two slashes before repos. I could not fig

Re: [Kicad-developers] file version compatibility (optional tokens in s-expression files)

2015-01-15 Thread Kaspar Emanuel
My 2c: let the parser ignore unknown/incompatible s-expressions and warn the user when they are encountered. On 14 January 2015 at 22:24, Martijn Kuipers wrote: > > On 14 Jan 2015, at 21:07, Cirilo Bernardo > wrote: > > > > On Thu, Jan 15, 2015 at 3:27 AM, Tomasz Wlostowski < > tomasz.wlostow..

Re: [Kicad-developers] The library tables wizard

2015-01-15 Thread Miguel Ángel Ajo
As I said on the other email, awesome :-) I’m glad my advice made any sense. And I like your idea of being able to make a local copy via the KiCad plugin, that’s very nice. Miguel Ángel Ajo On Thursday, 15 de January de 2015 at 21:10, jp charras wrote: > Le 07/01/2015 23:38, Miguel Ángel Aj

Re: [Kicad-developers] [Branch ~kicad-product-committers/kicad/product] Rev 5370: More work on fp lib table wizard: add a button to import the full list of .pretty libs on github.

2015-01-15 Thread Miguel Ángel Ajo
Jean Pierre, amazing work, that was fast! Compiling, I want to see it in action :) Miguel Ángel Ajo On Thursday, 15 de January de 2015 at 21:03, nore...@launchpad.net wrote: > > revno: 5370 > committer: jean-pierre charras (mailto:

Re: [Kicad-developers] Some schematics library structure ideas

2015-01-15 Thread Chris Giorgi
Several years ago (20110412) on this list, I attempted to start a discussion on this topic with Dick, but gained no traction at that time. In hopes of providing some context in reconciling the physical vs. logical representations and associated nomenclature, here's a repost of the main text of my o

Re: [Kicad-developers] The library tables wizard

2015-01-15 Thread jp charras
Le 07/01/2015 23:38, Miguel Ángel Ajo a écrit : > > Hi Jean Pierre, just an idea for your wizard work: > > https://api.github.com/orgs/KiCad/repos > > You could save the need to work with the HTML viewer and pagination problems > using the above API endpoint, all the KiCad project repositories

Re: [Kicad-developers] Some schematics library structure ideas

2015-01-15 Thread Andy Peters
> On Jan 14, 2015, at 7:46 PM, Fat-Zer wrote: >> >> Sorry about accidental send previous message. >> >> 2015-01-14 18:53 GMT+03:00 Andy Peters : >> > 2. Different images of the same schematic component. >> > There are already such variants for some common components like CP, also >> > there ar

[Kicad-developers] Fedora 21 nightlies build

2015-01-15 Thread Miguel Ángel Ajo
I wanted to announce that I have created this repository with nightly builds for KiCad: https://copr.fedoraproject.org/coprs/mangelajo/kicad/ http://ci.kicad-pcb.org/job/fedora-nightlies/ It has wxPython and python scripting enabled, and it’s based on wxWidgets 3.0.0, as kicad is now. For now y

Re: [Kicad-developers] more pythonic scripting API for pcbnew

2015-01-15 Thread Miguel Ángel Ajo
Yesterday I wrote a proposal for discussion here: http://pads.kicad-pcb.org/p/kicad-scripting-layer (please write your name for your color using the top right icon, so what you write can be identified to you). I tried not to look too much into the original Piers proposal, to do a true top-down