[Kicad-developers] Rev 6210: Unify help menus across top level windows.

The separator are missed in help menu over info entry in pl_editor and gerbview. === modified file 'gerbview/menubar.cpp' --- gerbview/menubar.cpp 2015-09-29 08:57:58 + +++ gerbview/menubar.cpp 2015-09-30 08:22:13 + @@ -231,6 +231,9 @@ _( "Open \"Getting Started in

Re: [Kicad-developers] Packaging the python footprint wizards for the release

Le 30/09/2015 01:25, Wayne Stambaugh a écrit : > JP, > > Your name is on the initial commit for qfn_wizard.py. I don't have time > to figure out these patches should be included. Do these patches make > sense? Let me know so I can make a decision on whether or not to commit > them. > >

Re: [Kicad-developers] Packaging the python footprint wizards for the release

I agree with JP here, QFP and QFN may be separate wizards. If there are common parts, feel free to use inheritance from a common base to reuse code. About naming: footprint generators sound better, or whatever, at that time I was following an industry leader on naming it..., but I agree

Re: [Kicad-developers] Packaging the python footprint wizards for the release

I just committed a fix so at least the python plugins will get installed in share/kicad/scripting which seems to work properly on msys2/mingw64 builds. I'll test it on Linux when I get a chance. I'm going to pass on the python scripting example folder unless someone can confirm that all of the

Re: [Kicad-developers] Push shove router documentation.

On 30.09.2015 15:18, Wayne Stambaugh wrote: > There was a question > https://answers.launchpad.net/kicad/+question/271926 posted and I was > going to add the link to the diff pair routing documentation when I > discovered that is it no where to be found in the Pcbnew manual. I > thought there was

Re: [Kicad-developers] Packaging the python footprint wizards for the release

The contents of the pcbnew/scritping/plugins folder will be installed which contains the scripts you are describing. It currently is not installed on windows or linux. Ironically it is install on osx. I'm not sure how that happened. The contents of pcbnew/scripting/examples will not be

Re: [Kicad-developers] Rev 6210: Unify help menus across top level windows.

Please include your patch as an attachment. Bzr doesn't really handle inline email patches gracefully so it makes my life easier if you just attach the patch. Thanks, Wayne On 9/30/2015 4:36 AM, Константин Барановский wrote: > The separator are missed in help menu over info entry in pl_editor

Re: [Kicad-developers] Rev 6210: Unify help menus across top level windows.

Patch in attachment. 2015-09-30 15:49 GMT+03:00 Wayne Stambaugh : > Please include your patch as an attachment. Bzr doesn't really handle > inline email patches gracefully so it makes my life easier if you just > attach the patch. > > Thanks, > > Wayne > > On 9/30/2015

[Kicad-developers] Push shove router documentation.

There was a question https://answers.launchpad.net/kicad/+question/271926 posted and I was going to add the link to the diff pair routing documentation when I discovered that is it no where to be found in the Pcbnew manual. I thought there was documentation written for the diff pair router. If

Re: [Kicad-developers] Push shove router documentation.

Thanks a bunch. I appreciated it! On 9/30/2015 9:34 AM, Tomasz Wlostowski wrote: > On 30.09.2015 15:18, Wayne Stambaugh wrote: >> There was a question >> https://answers.launchpad.net/kicad/+question/271926 posted and I was >> going to add the link to the diff pair routing documentation when I

Re: [Kicad-developers] Packaging the python footprint wizards for the release

On 9/30/2015 2:50 AM, jp charras wrote: > Le 30/09/2015 01:25, Wayne Stambaugh a écrit : >> JP, >> >> Your name is on the initial commit for qfn_wizard.py. I don't have time >> to figure out these patches should be included. Do these patches make >> sense? Let me know so I can make a decision

Re: [Kicad-developers] Packaging the python footprint wizards for the release

Thanks for the update. I'll leave the python examples uninstalled until we can confirm that they are not broken. I don't think it's all that important for the stable release. Users can always look at the python plugins to get an idea of how the python scripting works. On 9/30/2015 3:59 AM,

Re: [Kicad-developers] Packaging the python footprint wizards for the release

Hi Wayne, please reconsider to leave the python wizard installed The wizard is giving: BGA, DIP/SIP, QFP, Circular array and BarCode just out of the box. May be they are improvable (exposed pad, thermal vias etc), but at this state they are fully usable (without any crash or prob) and much

Re: [Kicad-developers] Packaging the python footprint wizards for the release

On 30 September 2015 at 21:19, Wayne Stambaugh wrote: > I just committed a fix so at least the python plugins will get installed > in share/kicad/scripting which seems to work properly on msys2/mingw64 > builds. I'll test it on Linux when I get a chance. I'm going to pass

Re: [Kicad-developers] Rev 6210: Unify help menus across top level windows.

Patch committed in r6228. Thanks. On 9/30/2015 9:15 AM, Константин Барановский wrote: > Patch in attachment. > > 2015-09-30 15:49 GMT+03:00 Wayne Stambaugh >: > > Please include your patch as an attachment. Bzr doesn't really handle >

Re: [Kicad-developers] Packaging the python footprint wizards for the release

So what exactly are we going to do? We need to fix up the CMake files and the real search paths. What should the paths be? 2015-09-30 15:51 GMT+02:00 Wayne Stambaugh : > The contents of the pcbnew/scritping/plugins folder will be installed > which contains the scripts you

Re: [Kicad-developers] Packaging the python footprint wizards for the release

Le 30/09/2015 14:30, Wayne Stambaugh a écrit : > Thanks for the update. I'll leave the python examples uninstalled until > we can confirm that they are not broken. I don't think it's all that > important for the stable release. Users can always look at the python > plugins to get an idea of how