[Kicad-developers] [PATCH] Handle STEP export properly on MacOS when launched from standalone pcbnew.

Hi folks! This patch is meant to fix a crash Seth found when exporting STEP from standalone pcbnew on macOS. Thanks! My apologies for having this so late in the cycle. this is going to be an amazing release for everyone, especially macOS users! Adam Wolf

[Kicad-developers] Janitor needs a kick

I don't think it was my formatting but the last two patches to master seem to have stuck the Janitor in a loop. Anyone have time to reset it? Seth ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] ngspice-28 for KiCad

Yes, Carsten started working on the debian packaging (see https://sourceforge.net/p/ngspice/mailman/message/36332769/) Holger Am 12.06.2018 um 21:46 schrieb José Ignacio: That is great news! Is debian packaging underway for testing now that it is DFSG compliant? On Tue, Jun 12, 2018 at

Re: [Kicad-developers] The KiCad 5 Polish menu

On Sun, Mar 11, 2018 at 09:25:47PM +0100, Krzysztof Kawa wrote: > Good evening > > Attached, I am sending files of the Polish menu to KiCad 5. The translation > is now approximately 80% complete. > > Regards > Chris Committed thanks, but next time do a git format-patch! -- Marco Ciampa I

Re: [Kicad-developers] ngspice-28 for KiCad

Hi, Am 12.06.2018 um 21:46 schrieb José Ignacio: > That is great news! Is debian packaging underway for testing now that it > is DFSG compliant? yes, for a long time already. :) But now that ngspice upstream is completely DFSG compatible it's even easier to do an update of the ngspice package

Re: [Kicad-developers] ngspice-28 for KiCad

That is great news! Is debian packaging underway for testing now that it is DFSG compliant? On Tue, Jun 12, 2018 at 2:29 PM, Holger Vogt wrote: > Dear developers, > > > ngspice-28 is available. Please check if this can be part of the new KiCad > release. > > > Major advances: > > ngspice-28

[Kicad-developers] ngspice-28 for KiCad

Dear developers, ngspice-28 is available. Please check if this can be part of the new KiCad release. Major advances: ngspice-28 reads device libs with PSPICE syntax (no more manual tweaking of device vendors' device libraries) All licenses involved are DFSG compatible (no more mixing of

Re: [Kicad-developers] Stable release update.

On 12/06/18 16:18, John Beard wrote: > Hi Wayne, > > Great news! > > I have one suggestion for a currently-un-milestoned bug that I'd (partly > selfishly) really like to see fixed for v5: > https://bugs.launchpad.net/kicad/+bug/1518694 > > This is the one where you can't shift posture when

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

On 6/12/2018 9:47 AM, Nick Østergaard wrote: > I am not sure if this will slightly derail this patch's topic. Sorry if > that is the case and tell me to back off. > > There have been multiple attempts on getting the python API in better > shape. Originally it was Ajo and some others with >

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #3552

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] kicad doc build process

Hi, On 12.06.2018 16:54, Marco Ciampa wrote: >> I guess that there are some new dependencies that needs to be installed as >> of https://github.com/KiCad/kicad-doc/issues/588 > Every day it does not work I miss revisions from users... FWIW, I have a working setup at

[Kicad-developers] Jenkins build is back to normal : kicad-qa #4257

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #3551

See Changes: [Wayne Stambaugh] Minor Python scripting documentation fixes. -- [...truncated 151.80 KB...] [ 89%] Building CXX object

Re: [Kicad-developers] kicad doc build process

On Tue, Jun 12, 2018 at 10:31:55AM +0200, Nick Østergaard wrote: > tir. 12. jun. 2018 09.28 skrev Marco Ciampa : > > > Hi folks, > > I would like to know better the organization of the build process > > (Continuous Integration) for the doc files. > > > > What I would like to know precisely is: >

Re: [Kicad-developers] Stable release update.

@lkundrak, the Fedora KiCad package admin, should pick up my -rc2 changes very soon - they will go into Fedora Rawhide. So we should be well positioned for a stable release to appear there soon after everything is tagged for the official 5.0.0 release. Steve On 06/12/2018 10:18 AM,

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hi Thomas, I would like to see KiCad finally have a high level Python api as part of v6. It's something that has been long over due. If anyone wants to help Thomas out, the help would be appreciated. I would prefer that the development discussion for this stay on this mailing list for the sake

Re: [Kicad-developers] Stable release update.

On 6/12/2018 10:18 AM, John Beard wrote: > Hi Wayne, > > Great news! > > I have one suggestion for a currently-un-milestoned bug that I'd (partly > selfishly) really like to see fixed for v5: > https://bugs.launchpad.net/kicad/+bug/1518694 > > This is the one where you can't shift posture when

[Kicad-developers] Build failed in Jenkins: kicad-qa #4256

See Changes: [Wayne Stambaugh] Minor Python scripting documentation fixes. -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in workspace

Re: [Kicad-developers] Stable release update.

Hi Wayne, Great news! I have one suggestion for a currently-un-milestoned bug that I'd (partly selfishly) really like to see fixed for v5: https://bugs.launchpad.net/kicad/+bug/1518694 This is the one where you can't shift posture when routing to a pad in the PNS router. It's certainly not a

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hi As Nick already mentioned, I did one of the last attempts of a high-level abstraction. The goal would be to have this as proposal for an official API in the KiCad 6 release (and I will likely carry on with the work on July). My goal would be to have a "pythonic" and natural to use API, which

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hi John, Ok, thank your for your clarification. For the record, I am not opposing the change, but would just mention it looks strange to add it to the doxygen-docs target when we have the doxygen-python target. Nick 2018-06-12 16:11 GMT+02:00 John Beard : > Hi Nick, > > It's a related concept,

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hi Nick, It's a related concept, certainly. The drawing helper stuff acts as a "buffer" between the Pcbnew API and the plugin writer, but this isn't really a design aim, it's just a side effect. It certainly does not totally insulate the writer from the Pcbnew API as it's a very limited subset of

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

On 6/12/2018 9:34 AM, John Beard wrote: > Hi Nick and Wayne, > > The patches as they are don't hook into the existing Python API doxygen > stuff as it's not exactly the same as the Python API, it's a helper > layer on top of that, and I was't sure if that would be OK. > > I will take a look at

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #3550

See Changes: [jeff] Make sure initially loaded footprint is rendered. -- [...truncated 151.00 KB...] [ 88%] Building CXX object

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

I am not sure if this will slightly derail this patch's topic. Sorry if that is the case and tell me to back off. There have been multiple attempts on getting the python API in better shape. Originally it was Ajo and some others with https://github.com/kicad/kicad-python But the most recent work

Re: [Kicad-developers] Stable release update.

I should be able to get the Mac packaging release-candidate ready by the middle of next week, which gives us more than a week of testing of that version. I already have folks testing on it now. Adam On Tue, Jun 12, 2018 at 7:57 AM Wayne Stambaugh wrote: > > I apologize for being absent the last

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hi Nick and Wayne, The patches as they are don't hook into the existing Python API doxygen stuff as it's not exactly the same as the Python API, it's a helper layer on top of that, and I was't sure if that would be OK. I will take a look at adding it to the existing Python doc generation if

Re: [Kicad-developers] Untranslated strings

On Tue, Jun 12, 2018 at 08:43:53AM -0400, Wayne Stambaugh wrote: > Hey Carsten, > > On 6/12/2018 8:28 AM, Carsten Schoenert wrote: > > Hello Wayne, > > > > Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh: > >> I'm thinking we should probably wait until after v5 and back port the > >> fix to the

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #3549

See Changes: [Maciej Suminski] Fix -Wparentheses in track_cleaner.cpp -- [...truncated 153.44 KB...] [ 92%] Building CXX object

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

We already have doxygen generation for the python API, although people say that it is easier to read the C++ one. It is generated with the doxygen-python make target. See http://docs.kicad-pcb.org/doxygen-python/ Does the additions in 0002 add to the normal python docs? 2018-06-12 15:07

Re: [Kicad-developers] [PATCH] Python FP wizard helper: docstrings and rounded/chamfered rects

Hey John, I like the idea of using doxygen to document the python plugins. The current Doxyfile does not include .py files so that would need to change. Before we do that, I would like to see a new section (maybe "Python Plugins") added to the documentation to separate the python plugin code

[Kicad-developers] Stable release update.

I apologize for being absent the last few days but I had out of town guests visiting and I didn't want to be rude and spend a lot of time in front of my computer. Things seem to be coming along nicely for the v5 stable release and it appears that all of the critical bugs have been fixed.

[Kicad-developers] Build failed in Jenkins: kicad-qa #4255

See Changes: [jeff] Make sure initially loaded footprint is rendered. -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in workspace

Re: [Kicad-developers] Untranslated strings

Hey Carsten, On 6/12/2018 8:28 AM, Carsten Schoenert wrote: > Hello Wayne, > > Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh: >> I'm thinking we should probably wait until after v5 and back port the >> fix to the v5 branch but the string example you noted should definitely >> be translated. I

[Kicad-developers] Build failed in Jenkins: kicad-qa #4254

See Changes: [Maciej Suminski] Fix -Wparentheses in track_cleaner.cpp -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in workspace

Re: [Kicad-developers] Untranslated strings

Hello Wayne, Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh: > I'm thinking we should probably wait until after v5 and back port the > fix to the v5 branch but the string example you noted should definitely > be translated. I don't know how much grief this would cause our > translators this late

Re: [Kicad-developers] [PATCH] Fix -Wparentheses warning in track_cleaner.cpp

Hi John, Thank you for the patch, I have just pushed it to the master branch. Cheers, Orson On 06/12/2018 12:16 PM, John Beard wrote: > Hi, > > This is a very simple patch to address a -Wparentheses warning in > pcbnew/track_cleaner.cpp. > > It was "wxBusyCursor( dummy );", it is now

Re: [Kicad-developers] Untranslated strings

I'm thinking we should probably wait until after v5 and back port the fix to the v5 branch but the string example you noted should definitely be translated. I don't know how much grief this would cause our translators this late in the game. Would any of our translators care to comment on this?

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #3548

See Changes: [Maciej Suminski] Fix selection clearance for via and tracks -- [...truncated 151.31 KB...] [ 89%] Linking CXX executable pcb_calculator [ 89%]

[Kicad-developers] [PATCH] Fix -Wparentheses warning in track_cleaner.cpp

Hi, This is a very simple patch to address a -Wparentheses warning in pcbnew/track_cleaner.cpp. It was "wxBusyCursor( dummy );", it is now "wxBusyCursor dummy;" Cheers, John From 60b4e54c733934f42f1911c8c8a08d7c2ecf011a Mon Sep 17 00:00:00 2001 From: John Beard Date: Tue, 12 Jun 2018 10:49:08

[Kicad-developers] Build failed in Jenkins: kicad-qa #4253

See Changes: [Maciej Suminski] Fix selection clearance for via and tracks -- [...truncated 40.94 KB...] :248:11:

Re: [Kicad-developers] Untranslated strings

I think this would be ok as it does not change anything from the user even if the translation is not updated. But I am not really a translator, so there might be some subtle thing I have missed. 2018-06-12 5:28 GMT+02:00 Seth Hillbrand : > ​Hi Devs- > > We're in string freeze but I've run across

Re: [Kicad-developers] kicad doc build process

tir. 12. jun. 2018 09.28 skrev Marco Ciampa : > Hi folks, > I would like to know better the organization of the build process > (Continuous Integration) for the doc files. > > What I would like to know precisely is: > > - who is in charge to run the machines that build the docs > Ajo, but I

[Kicad-developers] kicad doc build process

Hi folks, I would like to know better the organization of the build process (Continuous Integration) for the doc files. What I would like to know precisely is: - who is in charge to run the machines that build the docs - what is the frequency of the build process - where I can find the links to