Re: [Kicad-developers] KiCad 5 release announcement update

[Nick Østergaard]

I have now published the page, feel free to add PR's to make it better
or correct errornous info.
Den søn. 22. jul. 2018 kl. 20.04 skrev Nick Østergaard :
>
> I added some more information to the release note.
> Den søn. 22. jul. 2018 kl. 19.18 skrev Nick Østergaard :
> >
> > Depending on what you like, I think we should just release the doc
> > today, I will be away from tomorrow anyways, and it looks like
> > different linux packagers starting to package it anyways, so it should
> > begin to be available for many users anyways. We can just add a note
> > that the macos package is not quite ready yet.
> > Den søn. 22. jul. 2018 kl. 18.44 skrev Wayne Stambaugh 
> > :
> > >
> > > I just pushed the updated version of the v5 release announcement[1].
> > > Please let me know if you find any missing features.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > [1]:
> > > https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] KiCad 5 release announcement update

[Nick Østergaard]

I added some more information to the release note.
Den søn. 22. jul. 2018 kl. 19.18 skrev Nick Østergaard :
>
> Depending on what you like, I think we should just release the doc
> today, I will be away from tomorrow anyways, and it looks like
> different linux packagers starting to package it anyways, so it should
> begin to be available for many users anyways. We can just add a note
> that the macos package is not quite ready yet.
> Den søn. 22. jul. 2018 kl. 18.44 skrev Wayne Stambaugh :
> >
> > I just pushed the updated version of the v5 release announcement[1].
> > Please let me know if you find any missing features.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]:
> > https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] KiCad 5 release announcement update

[Nick Østergaard]

Depending on what you like, I think we should just release the doc
today, I will be away from tomorrow anyways, and it looks like
different linux packagers starting to package it anyways, so it should
begin to be available for many users anyways. We can just add a note
that the macos package is not quite ready yet.
Den søn. 22. jul. 2018 kl. 18.44 skrev Wayne Stambaugh :
>
> I just pushed the updated version of the v5 release announcement[1].
> Please let me know if you find any missing features.
>
> Cheers,
>
> Wayne
>
> [1]:
> https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

Thank you.
Den søn. 22. jul. 2018 kl. 15.04 skrev Steven A. Falco :
>
> I took a look, and no changes to the web site are needed regarding Fedora 
> packages.  Thanks for the pointers.
>
> Steve
>
> On 07/20/2018 09:48 PM, Adam Wolf wrote:
> > Hi Steven,
> >
> > The website is actually managed via github, and you can fork the
> > repository and make the edit and make a pull request for it.
> >
> > Of course, if you don't want / can't do that, let us know and one of
> > us can handle it too.
> >
> > Adam
> > On Fri, Jul 20, 2018 at 8:44 PM Steven A. Falco  
> > wrote:
> >>
> >> I looked at that page, and I opened a bug to update the text from 
> >> 5.0.0-rc3 to 5.0.0:
> >>
> >> https://bugs.launchpad.net/kicad/+bug/1782858
> >>
> >> The page looks a little strange in Fedora's Firefox, although it looks 
> >> fine in chrome.
> >>
> >> I attached a screenshot showing how part of the text is chopped off.  I 
> >> hesitate to write a bug for that because it may just be something strange 
> >> about my system, but I'd be happy to write one for that if you like.
> >>
> >> Steve
> >>
> >>
> >> On 07/20/2018 05:21 PM, Nick Østergaard wrote:
> >>> Hi Steven,
> >>>
> >>> Thank you.
> >>>
> >>> Will you submit a pr for changes on the fedora download page if at all 
> >>> needed?
> >>>
> >>> http://kicad-pcb.org/download/fedora/
> >>>
> >>> Nick
> >>> Den fre. 20. jul. 2018 kl. 20.02 skrev Steven A. Falco 
> >>> :
> >>>>
> >>>> I've made a build of 5.0.0 for Fedora rawhide:
> >>>>
> >>>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1129084
> >>>>
> >>>> This will take a little while to push out to the Fedora mirror servers.
> >>>>
> >>>> Steve
> >>>>
> >>>> On 07/20/2018 07:53 AM, Wayne Stambaugh wrote:
> >>>>> Great work Rene and thanks to all of the library developers.  Our
> >>>>> libraries will be one of the most noticeable improvements in the v5 
> >>>>> release.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Wayne
> >>>>>
> >>>>> On 07/19/2018 06:51 PM, Nick Østergaard wrote:
> >>>>>> Awesome, thanks for the update!
> >>>>>> Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl 
> >>>>>> :
> >>>>>>>
> >>>>>>> The library repos should now all be tagged. (Github had some server
> >>>>>>> problems so it all took quite some time. I hope nothing got damaged
> >>>>>>> because of that.)
> >>>>>>>
> >>>>>>> On 19/07/18 10:49, Nick Østergaard wrote:
> >>>>>>>> This sounds good. Thank you.
> >>>>>>>> Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl 
> >>>>>>>> :
> >>>>>>>>> On 18/07/18 19:59, Carsten Schoenert wrote:
> >>>>>>>>>> Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>>>>>>>>>>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>>>>>>>>>>> DebConf in Taiwan and working on packaging kicad-packages3d on a 
> >>>>>>>>>>>> laptop
> >>>>>>>>>>>> is PITA. So I'd like to this at home on a more powerful machine 
> >>>>>>>>>>>> at home
> >>>>>>>>>>>> latest on Friday afternoon.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>
> >>>>>>>>>>> By the way when giving deadlines stating your timezone might be
> >>>>>>>>>>> required. As you did not state one i choose to use CET summer 
> >>>>>>>>>>> time ;)
> >>>>>>>>>> Argh, yes, a damn phone call has interrupted me while writing ...
> >>>>>>>>>> But yes, CEST is the timezone I currently live. :-)
> >>>>>>>>>>
> >>>>>>>>>>&g

Re: [Kicad-developers] Fix CMakeLists.txt

[Nick Østergaard]

The patches look fin for me.

I suggest you add the [PATCH] tag to your email title next time.
Den lør. 21. jul. 2018 kl. 16.21 skrev Aimylios :
>
> Hi!
>
> While trying to build KiCad for Fedora 28 I discovered some minor
> problems in the main CMakeLists.txt file. Patches attached.
>
> Best regards,
> Marcus
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

Hi Steven,

Thank you.

Will you submit a pr for changes on the fedora download page if at all needed?

http://kicad-pcb.org/download/fedora/

Nick
Den fre. 20. jul. 2018 kl. 20.02 skrev Steven A. Falco :
>
> I've made a build of 5.0.0 for Fedora rawhide:
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1129084
>
> This will take a little while to push out to the Fedora mirror servers.
>
> Steve
>
> On 07/20/2018 07:53 AM, Wayne Stambaugh wrote:
> > Great work Rene and thanks to all of the library developers.  Our
> > libraries will be one of the most noticeable improvements in the v5 release.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 07/19/2018 06:51 PM, Nick Østergaard wrote:
> >> Awesome, thanks for the update!
> >> Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
> >>>
> >>> The library repos should now all be tagged. (Github had some server
> >>> problems so it all took quite some time. I hope nothing got damaged
> >>> because of that.)
> >>>
> >>> On 19/07/18 10:49, Nick Østergaard wrote:
> >>>> This sounds good. Thank you.
> >>>> Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
> >>>>> On 18/07/18 19:59, Carsten Schoenert wrote:
> >>>>>> Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>>>>>>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>>>>>>> DebConf in Taiwan and working on packaging kicad-packages3d on a 
> >>>>>>>> laptop
> >>>>>>>> is PITA. So I'd like to this at home on a more powerful machine at 
> >>>>>>>> home
> >>>>>>>> latest on Friday afternoon.
> >>>>>>>>
> >>>>>>>> Thanks!
> >>>>>>>>
> >>>>>>> By the way when giving deadlines stating your timezone might be
> >>>>>>> required. As you did not state one i choose to use CET summer time ;)
> >>>>>> Argh, yes, a damn phone call has interrupted me while writing ...
> >>>>>> But yes, CEST is the timezone I currently live. :-)
> >>>>>>
> >>>>>>> But if everything goes to plan i will tag the libs in a few hours 
> >>>>>>> anyway
> >>>>>>> giving you guys ample time.
> >>>>>> Thanks!
> >>>>>>
> >>>>> Sadly i worked too long yesterday so i have been too tired to fully
> >>>>> check the libs.
> >>>>>
> >>>>> I also have one or two PRs open that i want to check if they are correct
> >>>>> as they would fix some more minor issues. (Not a holdup but if they are
> >>>>> ready i would like to include them.)
> >>>>>
> >>>>>
> >>>>> So i will create the tags today in the evening. (Thursday 23:59 CEST
> >>>>> plus or minus two hours) Sorry about the delay.
> >>>>>
> >>>>>
> >>>>> ___
> >>>>> Mailing list: https://launchpad.net/~kicad-developers
> >>>>> Post to : kicad-developers@lists.launchpad.net
> >>>>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>>>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

Awesome, thanks for the update!
Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
>
> The library repos should now all be tagged. (Github had some server
> problems so it all took quite some time. I hope nothing got damaged
> because of that.)
>
> On 19/07/18 10:49, Nick Østergaard wrote:
> > This sounds good. Thank you.
> > Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
> >> On 18/07/18 19:59, Carsten Schoenert wrote:
> >>> Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>>>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>>>> DebConf in Taiwan and working on packaging kicad-packages3d on a laptop
> >>>>> is PITA. So I'd like to this at home on a more powerful machine at home
> >>>>> latest on Friday afternoon.
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>> By the way when giving deadlines stating your timezone might be
> >>>> required. As you did not state one i choose to use CET summer time ;)
> >>> Argh, yes, a damn phone call has interrupted me while writing ...
> >>> But yes, CEST is the timezone I currently live. :-)
> >>>
> >>>> But if everything goes to plan i will tag the libs in a few hours anyway
> >>>> giving you guys ample time.
> >>> Thanks!
> >>>
> >> Sadly i worked too long yesterday so i have been too tired to fully
> >> check the libs.
> >>
> >> I also have one or two PRs open that i want to check if they are correct
> >> as they would fix some more minor issues. (Not a holdup but if they are
> >> ready i would like to include them.)
> >>
> >>
> >> So i will create the tags today in the evening. (Thursday 23:59 CEST
> >> plus or minus two hours) Sorry about the delay.
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
>

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

Re: [Kicad-developers] Signed Installers

[Nick Østergaard]

If you need it for something, then I made this build of the 5.0 branch
with only kicad and libs.

http://downloads.kicad-pcb.org/windows/testing/patched/kicad-patched-58-5.0.1-dev-4-g3dcf04fdb-x86_64.exe

It should be suitable to install on top of a rc3 or nightly. Please do
install and test it if possible.

Nick
Den tor. 19. jul. 2018 kl. 10.49 skrev Nick Østergaard :
>
> As the installer package everything we can not make a proper 5.0.0
> stable before it has been tagged.
> Den tor. 19. jul. 2018 kl. 10.21 skrev Maciej Sumiński
> :
> >
> > Hi Simon,
> >
> > The installer works well, no warnings observed here. Do you think you
> > could create one for 5.0.0 stable and upload it to windows/stable directory?
> >
> > Cheers,
> > Orson
> >
> > On 07/19/2018 01:17 AM, Simon Richter wrote:
> > > Hi,
> > >
> > > I've just rebuilt the latest MSYS2 nightly and the rc3 package in
> > > /windows/testing with signing enabled, so these should now install with
> > > fewer complaints.
> > >
> > >Simon
> > >
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help   : https://help.launchpad.net/ListHelp
> > >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Signed Installers

[Nick Østergaard]

As the installer package everything we can not make a proper 5.0.0
stable before it has been tagged.
Den tor. 19. jul. 2018 kl. 10.21 skrev Maciej Sumiński
:
>
> Hi Simon,
>
> The installer works well, no warnings observed here. Do you think you
> could create one for 5.0.0 stable and upload it to windows/stable directory?
>
> Cheers,
> Orson
>
> On 07/19/2018 01:17 AM, Simon Richter wrote:
> > Hi,
> >
> > I've just rebuilt the latest MSYS2 nightly and the rc3 package in
> > /windows/testing with signing enabled, so these should now install with
> > fewer complaints.
> >
> >Simon
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

This sounds good. Thank you.
Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
>
> On 18/07/18 19:59, Carsten Schoenert wrote:
> > Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>> DebConf in Taiwan and working on packaging kicad-packages3d on a laptop
> >>> is PITA. So I'd like to this at home on a more powerful machine at home
> >>> latest on Friday afternoon.
> >>>
> >>> Thanks!
> >>>
> >> By the way when giving deadlines stating your timezone might be
> >> required. As you did not state one i choose to use CET summer time ;)
> > Argh, yes, a damn phone call has interrupted me while writing ...
> > But yes, CEST is the timezone I currently live. :-)
> >
> >> But if everything goes to plan i will tag the libs in a few hours anyway
> >> giving you guys ample time.
> > Thanks!
> >
>
> Sadly i worked too long yesterday so i have been too tired to fully
> check the libs.
>
> I also have one or two PRs open that i want to check if they are correct
> as they would fix some more minor issues. (Not a holdup but if they are
> ready i would like to include them.)
>
>
> So i will create the tags today in the evening. (Thursday 23:59 CEST
> plus or minus two hours) Sorry about the delay.
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

I am away from monday, so no worries.

ons. 18. jul. 2018 16.27 skrev Wayne Stambaugh :

> Nick,
>
> Please let me know if you can't get around to tagging the i18n and doc
> repos.  I can tag them on Friday if need be.
>
> Cheers,
>
> Wayne
>
> On 7/18/2018 10:23 AM, Nick Østergaard wrote:
> > I probably didn't mention this clearly. It is also good for me if
> > everything is tagged on friday, I guess that is mostly about the libs,
> > as I will probably tag i18n and doc myself.
> >
> > I am on vacation next week with no connectivity.
> >
> > Nick
> >
> > Den ons. 18. jul. 2018 kl. 16.19 skrev Wayne Stambaugh <
> stambau...@gmail.com>:
> >>
> >> Sorry about that.  I missed the restructure info.  I think I covered
> >> most of the changes in my repo.  I will try to get my changes pushed
> >> tonight so I can get some feedback before the official release
> announcement.
> >>
> >> On 7/18/2018 10:13 AM, Nick Østergaard wrote:
> >>> Ohh, well, I wrote that. He just restructured the dir structure
> >>> recently. I have only listed features added that could remember at
> >>> some point, there are certainly missing. So I suggest any developer
> >>> who have anything to add just creates a PR ASAP.
> >>> Den ons. 18. jul. 2018 kl. 16.10 skrev Wayne Stambaugh <
> stambau...@gmail.com>:
> >>>>
> >>>> Nick,
> >>>>
> >>>> A preliminary draft is already written[1] by Mark Roszko.  I just need
> >>>> to finish cleaning it up and remove the draft tag for the release
> >>>> announcement.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Wayne
> >>>>
> >>>> [1]:
> >>>>
> https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
> >>>>
> >>>> On 7/18/2018 10:01 AM, Nick Østergaard wrote:
> >>>>> Wayne,
> >>>>>
> >>>>> If you have a draft ready for the release announcement, please create
> >>>>> a pull request with it as a draft or push it as a draft, in case we
> >>>>> would like to add more info. This to avoid anyone else in attempting
> >>>>> to write  it.
> >>>>>
> >>>>> Nick
> >>>>> Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh <
> stambau...@gmail.com>:
> >>>>>>
> >>>>>> The goal is to have everything tagged by Friday and then give the
> >>>>>> package builders a few days to get the 5.0.0 packages (or a least
> most
> >>>>>> of them) built and added to the website before making the official
> >>>>>> announcement.  I still have some changes to make to the release
> >>>>>> announcement which I should have done by Friday.  Would the person
> >>>>>> responsible for providing the website patch for the v5 package links
> >>>>>> please let me know when that is ready to go.  Is there anything else
> >>>>>> that I missed?
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> Wayne
> >>>>>>
> >>>>>> On 7/18/2018 8:22 AM, Maciej Sumiński wrote:
> >>>>>>> Tell me if I am wrong, but I start to believe we are going to
> publish v5
> >>>>>>> this Friday. Is there anything missing I could help with? Do we
> have the
> >>>>>>> website updates ready?
> >>>>>>>
> >>>>>>> Cheers,
> >>>>>>> Orson
> >>>>>>>
> >>>>>>> On 07/11/2018 08:49 PM, Wayne Stambaugh wrote:
> >>>>>>>> Are there any critical bugs remaining to be fixed for the stable 5
> >>>>>>>> release?  I didn't see any thing outstanding but I may have missed
> >>>>>>>> something while I was on vacation.  I'm going to create a 5.0.0
> >>>>>>>> milestone for the last few remaining bugs and shoot for a 7/20
> tag date
> >>>>>>>> unless there are any more critical bugs lurking about.  I will
> also
> >>>>>>>> create 5.0 and 5.1 branches.  If I tag on 7/20, I would like to
> make the
> >>>>>>>> release announcement on 7/27.  Does anyone see any issues with
> these d

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

I probably didn't mention this clearly. It is also good for me if
everything is tagged on friday, I guess that is mostly about the libs,
as I will probably tag i18n and doc myself.

I am on vacation next week with no connectivity.

Nick

Den ons. 18. jul. 2018 kl. 16.19 skrev Wayne Stambaugh :
>
> Sorry about that.  I missed the restructure info.  I think I covered
> most of the changes in my repo.  I will try to get my changes pushed
> tonight so I can get some feedback before the official release announcement.
>
> On 7/18/2018 10:13 AM, Nick Østergaard wrote:
> > Ohh, well, I wrote that. He just restructured the dir structure
> > recently. I have only listed features added that could remember at
> > some point, there are certainly missing. So I suggest any developer
> > who have anything to add just creates a PR ASAP.
> > Den ons. 18. jul. 2018 kl. 16.10 skrev Wayne Stambaugh 
> > :
> >>
> >> Nick,
> >>
> >> A preliminary draft is already written[1] by Mark Roszko.  I just need
> >> to finish cleaning it up and remove the draft tag for the release
> >> announcement.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> [1]:
> >> https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
> >>
> >> On 7/18/2018 10:01 AM, Nick Østergaard wrote:
> >>> Wayne,
> >>>
> >>> If you have a draft ready for the release announcement, please create
> >>> a pull request with it as a draft or push it as a draft, in case we
> >>> would like to add more info. This to avoid anyone else in attempting
> >>> to write  it.
> >>>
> >>> Nick
> >>> Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh 
> >>> :
> >>>>
> >>>> The goal is to have everything tagged by Friday and then give the
> >>>> package builders a few days to get the 5.0.0 packages (or a least most
> >>>> of them) built and added to the website before making the official
> >>>> announcement.  I still have some changes to make to the release
> >>>> announcement which I should have done by Friday.  Would the person
> >>>> responsible for providing the website patch for the v5 package links
> >>>> please let me know when that is ready to go.  Is there anything else
> >>>> that I missed?
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Wayne
> >>>>
> >>>> On 7/18/2018 8:22 AM, Maciej Sumiński wrote:
> >>>>> Tell me if I am wrong, but I start to believe we are going to publish v5
> >>>>> this Friday. Is there anything missing I could help with? Do we have the
> >>>>> website updates ready?
> >>>>>
> >>>>> Cheers,
> >>>>> Orson
> >>>>>
> >>>>> On 07/11/2018 08:49 PM, Wayne Stambaugh wrote:
> >>>>>> Are there any critical bugs remaining to be fixed for the stable 5
> >>>>>> release?  I didn't see any thing outstanding but I may have missed
> >>>>>> something while I was on vacation.  I'm going to create a 5.0.0
> >>>>>> milestone for the last few remaining bugs and shoot for a 7/20 tag date
> >>>>>> unless there are any more critical bugs lurking about.  I will also
> >>>>>> create 5.0 and 5.1 branches.  If I tag on 7/20, I would like to make 
> >>>>>> the
> >>>>>> release announcement on 7/27.  Does anyone see any issues with these 
> >>>>>> dates
> >>>>>>
> >>>>>> How do stand with our installers?  I saw the macos installer was making
> >>>>>> some nice progress.
> >>>>>>
> >>>>>> Are the doc devs, library devs, and translators (except for the recent
> >>>>>> minor string changes) ready?
> >>>>>>
> >>>>>> Is there anything else I'm missing?  I really would like to make these
> >>>>>> dates.  I have an Olimex TERES laptop kit that I've been dying to play
> >>>>>> around with but I know once I start on that, everything else will get
> >>>>>> pushed to the back burner so I'm not going to start until version 5 is
> >>>>>> released. :)
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> Wayne
&

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

Ohh, well, I wrote that. He just restructured the dir structure
recently. I have only listed features added that could remember at
some point, there are certainly missing. So I suggest any developer
who have anything to add just creates a PR ASAP.
Den ons. 18. jul. 2018 kl. 16.10 skrev Wayne Stambaugh :
>
> Nick,
>
> A preliminary draft is already written[1] by Mark Roszko.  I just need
> to finish cleaning it up and remove the draft tag for the release
> announcement.
>
> Cheers,
>
> Wayne
>
> [1]:
> https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.0.0.adoc
>
> On 7/18/2018 10:01 AM, Nick Østergaard wrote:
> > Wayne,
> >
> > If you have a draft ready for the release announcement, please create
> > a pull request with it as a draft or push it as a draft, in case we
> > would like to add more info. This to avoid anyone else in attempting
> > to write  it.
> >
> > Nick
> > Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh 
> > :
> >>
> >> The goal is to have everything tagged by Friday and then give the
> >> package builders a few days to get the 5.0.0 packages (or a least most
> >> of them) built and added to the website before making the official
> >> announcement.  I still have some changes to make to the release
> >> announcement which I should have done by Friday.  Would the person
> >> responsible for providing the website patch for the v5 package links
> >> please let me know when that is ready to go.  Is there anything else
> >> that I missed?
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> On 7/18/2018 8:22 AM, Maciej Sumiński wrote:
> >>> Tell me if I am wrong, but I start to believe we are going to publish v5
> >>> this Friday. Is there anything missing I could help with? Do we have the
> >>> website updates ready?
> >>>
> >>> Cheers,
> >>> Orson
> >>>
> >>> On 07/11/2018 08:49 PM, Wayne Stambaugh wrote:
> >>>> Are there any critical bugs remaining to be fixed for the stable 5
> >>>> release?  I didn't see any thing outstanding but I may have missed
> >>>> something while I was on vacation.  I'm going to create a 5.0.0
> >>>> milestone for the last few remaining bugs and shoot for a 7/20 tag date
> >>>> unless there are any more critical bugs lurking about.  I will also
> >>>> create 5.0 and 5.1 branches.  If I tag on 7/20, I would like to make the
> >>>> release announcement on 7/27.  Does anyone see any issues with these 
> >>>> dates
> >>>>
> >>>> How do stand with our installers?  I saw the macos installer was making
> >>>> some nice progress.
> >>>>
> >>>> Are the doc devs, library devs, and translators (except for the recent
> >>>> minor string changes) ready?
> >>>>
> >>>> Is there anything else I'm missing?  I really would like to make these
> >>>> dates.  I have an Olimex TERES laptop kit that I've been dying to play
> >>>> around with but I know once I start on that, everything else will get
> >>>> pushed to the back burner so I'm not going to start until version 5 is
> >>>> released. :)
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Wayne
> >>>>
> >>>> ___
> >>>> Mailing list: https://launchpad.net/~kicad-developers
> >>>> Post to : kicad-developers@lists.launchpad.net
> >>>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>>> More help   : https://help.launchpad.net/ListHelp
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

Wayne,

If you have a draft ready for the release announcement, please create
a pull request with it as a draft or push it as a draft, in case we
would like to add more info. This to avoid anyone else in attempting
to write  it.

Nick
Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh :
>
> The goal is to have everything tagged by Friday and then give the
> package builders a few days to get the 5.0.0 packages (or a least most
> of them) built and added to the website before making the official
> announcement.  I still have some changes to make to the release
> announcement which I should have done by Friday.  Would the person
> responsible for providing the website patch for the v5 package links
> please let me know when that is ready to go.  Is there anything else
> that I missed?
>
> Cheers,
>
> Wayne
>
> On 7/18/2018 8:22 AM, Maciej Sumiński wrote:
> > Tell me if I am wrong, but I start to believe we are going to publish v5
> > this Friday. Is there anything missing I could help with? Do we have the
> > website updates ready?
> >
> > Cheers,
> > Orson
> >
> > On 07/11/2018 08:49 PM, Wayne Stambaugh wrote:
> >> Are there any critical bugs remaining to be fixed for the stable 5
> >> release?  I didn't see any thing outstanding but I may have missed
> >> something while I was on vacation.  I'm going to create a 5.0.0
> >> milestone for the last few remaining bugs and shoot for a 7/20 tag date
> >> unless there are any more critical bugs lurking about.  I will also
> >> create 5.0 and 5.1 branches.  If I tag on 7/20, I would like to make the
> >> release announcement on 7/27.  Does anyone see any issues with these dates
> >>
> >> How do stand with our installers?  I saw the macos installer was making
> >> some nice progress.
> >>
> >> Are the doc devs, library devs, and translators (except for the recent
> >> minor string changes) ready?
> >>
> >> Is there anything else I'm missing?  I really would like to make these
> >> dates.  I have an Olimex TERES laptop kit that I've been dying to play
> >> around with but I know once I start on that, everything else will get
> >> pushed to the back burner so I'm not going to start until version 5 is
> >> released. :)
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] kicad version and install location

[Nick Østergaard]

Why does this need to be so complicated?

I think we could just rename the kicad config folder created and
searched by kicad from "kicad" to "kicad5" and be happy in the 5.x
branches.
Den man. 16. jul. 2018 kl. 15.11 skrev Bob Gustafson :
>
> There is a tool which allows developers to quickly switch between different 
> versions of Ruby (and their associated gemsets).
>
> Perhaps it could be used for KiCad? Or perhaps just some of RVM's ideas could 
> be adapted for KiCad
>
> https://rvm.io/
>
>
> On 07/15/2018 09:52 AM, Adam Wolf wrote:
>
> I guess the fact that environment variables are tricky to set for graphical 
> applications for the Mac may be a blessing here :)
>
> Should we try to package a macOS version that installs to 
> /Applications/KiCad5 and /Library/Application Support/kicad?
>
> Adam
>
> On Sun, Jul 15, 2018, 2:41 AM Eeli Kaikkonen  wrote:
>>
>> There are some people in the user forum who have spent time with these 
>> v4->v5 problems, including me and Rene. The consensus about the environment 
>> variables seems to be what Rene already said, that they should not (without 
>> explicit user intervention) be set for the system, but from KiCad itself. 
>> Nick confirmed that the current v5 installer won't set them by default. They 
>> are still a problem if they have been set by v4 installer.
>>
>> su 15. heinäk. 2018 klo 5.04 Strontium (strnty...@gmail.com) kirjoitti:
>>>
>>> I honestly think each major revision of KiCad should be considered a NEW
>>> program, installs to a new place has its configuration and libraries all
>>> in a new location.  Only Incremental updates 5.0 -> 5.1 should be
>>> considered upgrades.
>>>
>>
>> I agree. It's probable that many users will want to continue with v4 for old 
>> projects but v5 for new, and in the future the same thing will be true for 
>> v5 vs. v6, because they break the file/project compatibility. But where the 
>> compatibility is kept it's more likely to be considered as just an upgrade.
>>
>>>
>>> Kicad configuration isn't complex or onerous so if a user wants to bring
>>> a Kicad4 config into Kicad5 or 6 or whatever, then they do that
>>> themselves, otherwise after install Kicad5 is a fresh blank sheet with
>>> no relationship to anything that happened on the users computer in
>>> Kicad4.  I am not familiar with the issues on Windows, but I would have
>>> thought now this is mostly a packaging issue only??
>>>
>>
>> I tried modifying the Windows installer, I only needed to replace some of 
>> "KiCad" strings with "KiCad5" and it can install v5 alongside v4 
>> independently. The only problem is the configuration and the environment 
>> variables set by v4. They can be handled with a startup script. See 
>> https://forum.kicad.info/t/does-v5-have-to-overwrite-on-install/11282 for 
>> some details.
>>
>>> I also agree if it can't work this way now on Windows, then its all a
>>> bit late for V5, but maybe V6 can consider itself a new program distinct
>>> from V5.  This would also help with testing, because users could use V5
>>> for daily work, but also easily install a V6 daily side by side.
>>
>>
>> All this could be done with the Windows installer, provided that a startup 
>> script would be offered.
>>
>> To make this all, at least the startup script, as simple as possible I would 
>> suggest one (or three) small changes to KiCad (for 5.1, or even 5.0.1?). Add 
>> command line options --config=/path/to/config and --ignore-env-vars. The 
>> former is obvious and would override KICAD_CONFIG_HOME system environment 
>> variable. The latter would make KiCad ignore all system environment 
>> variables and use the current internal logic and the path settings UI 
>> instead. That way the old variables could be left for v4 and the newer 
>> versions would be completely independent if the command line switches were 
>> used. The command line switch for the config path would be mostly for 
>> convenience. In Windows starting a program with custom environment variables 
>> is tedious and error prone to write (see the above mentioned thread). 
>> Command line switches are much easier.
>>
>> It could also be possible to make --ignore-env-vars=true by default. Sharing 
>> the environment variables would be a special case if the user wants that.
>>
>> The general problem with using system environment variables is that they are 
>> good for situations when there's only one version of a program on the 
>> system, and/or several processes share the same variable values. Neither of 
>> them is true for parallel installations of KiCad.
>>
>> Eeli Kaikkonen
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : 

Re: [Kicad-developers] 5.1 branch

[Nick Østergaard]

Can you edit anything on them? Can you provide a screenshot of the
preferences dialog?

søn. 15. jul. 2018 23.15 skrev Eeli Kaikkonen :

>
>
> su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:
>
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>>
>> Has anyone had a chance to try out the paged dialogs (Preferences and
>> Board Setup) on Windows or Linux?  They weren’t working for Nick (disabled
>> panels).
>>
>
> Works here in Ubuntu 17.10.
>
> Application: kicad
> Version: (5.0.0-rc3-dev-86-g2eeed8ee3-dirty), release build
> Libraries:
> wxWidgets 3.0.3
> libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
> (+libidn2/2.0.2) librtmp/2.3
> Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
> wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
> Boost: 1.62.0
> OpenCASCADE Community Edition: 6.8.0
> Curl: 7.55.1
> Compiler: GCC 7.2.0 with C++ ABI 1011
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> KICAD_SCRIPTING_ACTION_MENU=OFF
> BUILD_GITHUB_PLUGIN=ON
> KICAD_USE_OCE=ON
> KICAD_USE_OCC=OFF
> KICAD_SPICE=OFF
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1 tag

[Nick Østergaard]

I guess Jeff's reasoning is to stabilize it a bit before braching. We all
know that changing the dialogs often leads to cross platform issues. But
either way is fine for me.

lør. 14. jul. 2018 01.59 skrev Wayne Stambaugh :

> That would prevent us from adding new features such as the new schematic
> file formats and eeschema gal to development branch so I would prefer
> not to limit ourselves in the master branch.
>
> On 07/13/2018 06:45 PM, Jeff Young wrote:
> > Would it make more sense to keep 5.1 on master for a while, and then
> branch it so master can become 6.0?
> >
> > (Sent from the Denver airport, so any response may be delayed till I get
> back to Ireland.)
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Translation of dialog_bom_help.html

[Nick Østergaard]

FWIW The documentation does not use markdown syntax, but asciidoc.
Den fre. 13. jul. 2018 kl. 23.52 skrev Wayne Stambaugh :
>
> If the wxHtml widget would support markdown that would work but I don't
> think that is the case.  I prefer converting it to markdown and moving
> it into the Eeschema user documentation.  It's currently not in the
> documentation so that is an issue itself.  It's something we should
> definitely take a look at both in terms of the documentation and the
> lack of translation.
>
> On 07/12/2018 11:36 PM, David Godfrey wrote:
> > Hi Wayne,
> >
> > Out of interest, if formatted translated text is required in this
> > dialogue would  it be easier to change from html to markdown?
> >
> > At least markdown is fairly easy for a translator to work with, although
> > it doesn't provide all of the flexibility of html.
> >
> > Regards
> > David Godfrey
> > SB Tech Services
> > mb: +61 437 286 200 
> >
> > chat: with /dcg_mx/ at
> > #sbts:matrix.org  (Computer)
> > #sbts:matrix.org  (mobile Device)
> >
> >
> > On 12/07/18 22:15, Wayne Stambaugh wrote:
> >> On 7/12/2018 8:59 AM, Simon Richter wrote:
> >>> Hi,
> >>>
> >>> On 11.07.2018 21:51, Wayne Stambaugh wrote:
> >>>
>  This probably should have been done as a cpp string wrapped with the
>  translation macro _().  I'm not sure there is anything we can do to make
>  this translatable.  Anyone else have any ideas?
> >>> We could move the entire text to the user documentation, and make the
> >>> dialog point at it.
> >>>
> >>> If the dialog is unusable without the documentation, then that is a
> >>> separate problem, but I doubt it's that bad.
> >>>
> >>>Simon
> >> I completely missed the fact the html file is converted to a C string by
> >> Html2C.cmake.  It would be easy enough to modify Html2C.cmake to wrap
> >> the string with the _() macro.  The problem I see is the string (see
> >> generated file eeschema/dialogs/dialog_bom_help_html.h) has a lot of
> >> markup which I'm sure will make life miserable for translators.
> >>
> >> We could try Simon's suggestion of moving the html text to the eeschema
> >> user docs and provide a link using the help button.  We would have to
> >> add code to point the help url to the translated version if it exists
> >> but that shouldn't be too difficult (famous last words).  The contents
> >> of the BOM dialog html file do not appear to exist anywhere in the
> >> eeschema user doc.
> >>
> >> In the future we should refrain from doing this so that all source
> >> strings and documentation can be translated.
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Stable version 5 tagged.

[Nick Østergaard]

I don't think so, I guess we still want some time to give translators a chance.
Den fre. 13. jul. 2018 kl. 23.24 skrev Adam Wolf
:
>
> Resending from proper email address...
>
> On Fri, Jul 13, 2018, 4:23 PM Adam Wolf  wrote:
>>
>> Good work, Wayne, and good work, team!
>>
>> Are you thinking the release announcement will be before Monday?  Just 
>> trying to figure out if I have to carve time out this weekend.
>>
>> Adam
>>
>> On Fri, Jul 13, 2018, 3:15 PM Wayne Stambaugh  wrote:
>>>
>>> Queue up the Handel's "Hallelujah Chorus", the stable version 5 source
>>> has been tagged and the source archive uploaded to Launchpad.  I see a
>>> malted beverage in my immediate future.  Lets get the libraries, docs,
>>> and translations tagged so our builders can start created release
>>> packages.  Once most (all) of the packages are built, I will make the
>>> official release announcement on the KiCad blog and the user forum.
>>> Once again, I cannot thank all of you enough for your hard work and efforts.
>>>
>>> I will create the 5.0 and 5.1 branches shortly.  Please refrain from
>>> making any commits into the development branch until I create these
>>> branches.  Also, keep in mind that bug fixes will have to be
>>> cherry-picked from the development branch to the 5.0 and 5.1 branches so
>>> it will be a bit of extra work to keep everything synced up.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] 5.1 preview

[Nick Østergaard]

Hi Eeli,

The new commits do seem to build for me:

SUCCESS  * fcf38cb2d4  Rewrite Move And Swap Layers dialog.  
SUCCESS  * d7e294194e  Move search status messages to Find/Replace
dialog.  
SUCCESS  * 8f8c19200d  Simplify copy/paste of pad settings.  
SUCCESS  * 5acd129668  Add position to Eeschema's edit text dialogs.

SUCCESS  * 4aa0890020  Add Worksheet to Render Items for GerbView.  
SUCCESS  * d106e3b9a7  Make SMD terminology consistent.  
SUCCESS  * 9b0893f1eb  Fix focus issues with dialog previews.  
SUCCESS  * fdd909b454  Add Edit context menu item for EEschema graphic
lines.  
SUCCESS  * 076dc0eb05  Reduce verbosity in netlist updating messages.

SUCCESS  * e789169cb3  Allow for reduced nagging with wider use of
KIDIALOG.  
SUCCESS  * 4c8e48f35f  Turn on library filter when library is
selected.  
SUCCESS  * 0bf877f83a  (origin/6.0) Add grid and zone dropdowns to
GerbView frame.  

Are you sure you don't have some local changes and is in a merge state
such that you are not actually checked out to those commits.
Den fre. 13. jul. 2018 kl. 10.02 skrev Nick Østergaard :
>
> I guess some patches were just pushed which were not verified to
> build. In the mean time you can checkout any of  these commits if you
> want to test (take the bottom one).
>
> https://jenkins.simonrichter.eu:8443/job/windows-kicad-msys2-evaluate/54/artifact/build-report.txt
> Den fre. 13. jul. 2018 kl. 09.53 skrev Eeli Kaikkonen
> :
> >
> > I got a bunch of errors. Ubuntu 17.10. The official pre-5 code compiles 
> > fine. Is there something wrong with my setup? If someone else with Ubuntu 
> > has this working, I'll try again from scratch.
> >
> > Eeli Kaikkonen
> >
> > _
> >
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:66:5:
> >  error: no template named 'FIELDS_GRID_TABLE'
> > FIELDS_GRID_TABLE* m_fields;
> > ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:107:9:
> >  error: cannot initialize object parameter of type 'DIALOG_SHIM' with an 
> > expression of type 'DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB'
> > if( dlg.ShowQuasiModal() != wxID_OK )
> > ^~~
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:125:20:
> >  error: no template named 'FIELDS_GRID_TABLE'
> > m_fields = new FIELDS_GRID_TABLE( true, GetUserUnits(), 
> > m_libEntry );
> >^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:128:28:
> >  error: use of undeclared identifier 'FDC_VALUE'; did you mean 'FIND_VALUE'?
> > m_delayedFocusColumn = FDC_VALUE;
> >^
> >FIND_VALUE
> > /work/ohjelmointi/kicad/jeyjey/eeschema/./sch_edit_frame.h:108:5: note: 
> > 'FIND_VALUE' declared here
> > FIND_VALUE, ///< Find an item by it's value field.
> > ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:138:35:
> >  error: unknown type name 'FIELDS_GRID_TRICKS'
> > m_grid->PushEventHandler( new FIELDS_GRID_TRICKS( m_grid, this ) );
> >   ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:143:35:
> >  error: use of undeclared identifier 'small_plus_xpm'
> > m_bpAdd->SetBitmap( KiBitmap( small_plus_xpm ) );
> >   ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:144:38:
> >  error: use of undeclared identifier 'trash_xpm'
> > m_bpDelete->SetBitmap( KiBitmap( trash_xpm ) );
> >  ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:145:38:
> >  error: use of undeclared identifier 'small_up_xpm'
> > m_bpMoveUp->SetBitmap( KiBitmap( small_up_xpm ) );
> >  ^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:146:40:
> >  error: use of undeclared identifier 'small_down_xpm'
> > m_bpMoveDown->SetBitmap( KiBitmap( small_down_xpm ) );
> >^
> > /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:149:13:
> >  error: no matching member function for call to 'Connect'
> > m_grid->Connect( wxEVT_GRID_CELL_CHANGING, wxGridEventHandler( 
> > DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB::OnGridCellChanging ), NULL, this );
> > ^~~
> >

Re: [Kicad-developers] 5.1 preview

[Nick Østergaard]

I guess some patches were just pushed which were not verified to
build. In the mean time you can checkout any of  these commits if you
want to test (take the bottom one).

https://jenkins.simonrichter.eu:8443/job/windows-kicad-msys2-evaluate/54/artifact/build-report.txt
Den fre. 13. jul. 2018 kl. 09.53 skrev Eeli Kaikkonen
:
>
> I got a bunch of errors. Ubuntu 17.10. The official pre-5 code compiles fine. 
> Is there something wrong with my setup? If someone else with Ubuntu has this 
> working, I'll try again from scratch.
>
> Eeli Kaikkonen
>
> _
>
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:66:5:
>  error: no template named 'FIELDS_GRID_TABLE'
> FIELDS_GRID_TABLE* m_fields;
> ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:107:9:
>  error: cannot initialize object parameter of type 'DIALOG_SHIM' with an 
> expression of type 'DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB'
> if( dlg.ShowQuasiModal() != wxID_OK )
> ^~~
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:125:20:
>  error: no template named 'FIELDS_GRID_TABLE'
> m_fields = new FIELDS_GRID_TABLE( true, GetUserUnits(), 
> m_libEntry );
>^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:128:28:
>  error: use of undeclared identifier 'FDC_VALUE'; did you mean 'FIND_VALUE'?
> m_delayedFocusColumn = FDC_VALUE;
>^
>FIND_VALUE
> /work/ohjelmointi/kicad/jeyjey/eeschema/./sch_edit_frame.h:108:5: note: 
> 'FIND_VALUE' declared here
> FIND_VALUE, ///< Find an item by it's value field.
> ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:138:35:
>  error: unknown type name 'FIELDS_GRID_TRICKS'
> m_grid->PushEventHandler( new FIELDS_GRID_TRICKS( m_grid, this ) );
>   ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:143:35:
>  error: use of undeclared identifier 'small_plus_xpm'
> m_bpAdd->SetBitmap( KiBitmap( small_plus_xpm ) );
>   ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:144:38:
>  error: use of undeclared identifier 'trash_xpm'
> m_bpDelete->SetBitmap( KiBitmap( trash_xpm ) );
>  ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:145:38:
>  error: use of undeclared identifier 'small_up_xpm'
> m_bpMoveUp->SetBitmap( KiBitmap( small_up_xpm ) );
>  ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:146:40:
>  error: use of undeclared identifier 'small_down_xpm'
> m_bpMoveDown->SetBitmap( KiBitmap( small_down_xpm ) );
>^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:149:13:
>  error: no matching member function for call to 'Connect'
> m_grid->Connect( wxEVT_GRID_CELL_CHANGING, wxGridEventHandler( 
> DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB::OnGridCellChanging ), NULL, this );
> ^~~
> /usr/include/wx-3.0/wx/event.h:3490:10: note: candidate function not viable: 
> no known conversion from 'DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB *' to 
> 'wxEvtHandler *' for 4th argument
> void Connect(wxEventType eventType,
>  ^
> /usr/include/wx-3.0/wx/event.h:3469:10: note: candidate function not viable: 
> no known conversion from 'wxObjectEventFunction' (aka 'void 
> (wxEvtHandler::*)(wxEvent &)') to 'int' for 2nd argument
> void Connect(int winid,
>  ^
> /usr/include/wx-3.0/wx/event.h:3482:10: note: candidate function not viable: 
> no known conversion from 'wxObjectEventFunction' (aka 'void 
> (wxEvtHandler::*)(wxEvent &)') to 'wxEventType' (aka 'int') for 2nd argument
> void Connect(int winid,
>  ^
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:151:5:
>  error: cannot initialize object parameter of type 'DIALOG_SHIM' with an 
> expression of type 'DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB'
> FinishDialogSettings();
> ^~~~
> /work/ohjelmointi/kicad/jeyjey/eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp:162:13:
>  error: no matching member function for call to 'Disconnect'
> m_grid->Disconnect( wxEVT_GRID_CELL_CHANGING, wxGridEventHandler( 
> DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB::OnGridCellChanging ), NULL, this );
> ^~
> /usr/include/wx-3.0/wx/event.h:3515:10: note: candidate function not viable: 
> no known conversion from 'DIALOG_EDIT_LIBENTRY_FIELDS_IN_LIB *' to 
> 'wxEvtHandler *' for 4th argument
> bool Disconnect(wxEventType eventType,
>  ^
> 

Re: [Kicad-developers] Stable 5 release.

[Nick Østergaard]

For windows the installer should also be in good nick. No pun intended.

There are some minor things that I would like to do, but they are by
no means a blocker for a release.

Nick
Den ons. 11. jul. 2018 kl. 21.35 skrev Adam Wolf
:
>
> MacOS installer is ready.
>
> Adam
> On Wed, Jul 11, 2018 at 1:50 PM Wayne Stambaugh  wrote:
> >
> > Are there any critical bugs remaining to be fixed for the stable 5
> > release?  I didn't see any thing outstanding but I may have missed
> > something while I was on vacation.  I'm going to create a 5.0.0
> > milestone for the last few remaining bugs and shoot for a 7/20 tag date
> > unless there are any more critical bugs lurking about.  I will also
> > create 5.0 and 5.1 branches.  If I tag on 7/20, I would like to make the
> > release announcement on 7/27.  Does anyone see any issues with these dates
> >
> > How do stand with our installers?  I saw the macos installer was making
> > some nice progress.
> >
> > Are the doc devs, library devs, and translators (except for the recent
> > minor string changes) ready?
> >
> > Is there anything else I'm missing?  I really would like to make these
> > dates.  I have an Olimex TERES laptop kit that I've been dying to play
> > around with but I know once I start on that, everything else will get
> > pushed to the back burner so I'm not going to start until version 5 is
> > released. :)
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] [Kicad-doc-devs] User documentation build server.

[Nick Østergaard]

The docs are not hosted there  it is on
http://docs.kicad-pcb.org/master/

The dev docs are also still there.

ons. 11. jul. 2018 19.11 skrev Wayne Stambaugh :

> I just went to http://darine.hogyros.de:8080/job/any-kicad-doc-head/ and
> I cannot load the web page.  I wanted to take a look at my v4 to v5
> conversion doc to make sure everything looks correct.  Is anyone aware
> that the both the user and developer doc build servers appear to be down?
>
> In a related note, I'm assuming that we are currently building v4 of the
> user documentation for the KiCad website.  Is someone going to take care
> of this for the v5 release?
>
> --
> Mailing list: https://launchpad.net/~kicad-doc-devs
> Post to : kicad-doc-d...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-doc-devs
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH 0/4] Fixup various small spelling issues

[Nick Østergaard]

And another i18n change in common/tool/common_tools.cpp

Den søn. 8. jul. 2018 kl. 14.12 skrev :

> From: Carsten Schoenert 
>
> Hi,
>
> here again a small patch set for fixing up small grammar typos found by
> the Debian QS tool Lintian that should go into before the final release
> of 5.0.0.
>
> All fixes are within comments except one fix which is in a i18n string
> in pcbnew/dialogs/dialog_pns_settings_base.fbp.
>
> Regrads
> Carsten
>
> Carsten Schoenert (4):
>   fix misspelled 'Toogle' -> 'Toggle'
>   fix misspelled 'allows to' -> 'allows one to'
>   fix misspelled 'allow to' -> 'allow one to'
>   fix misspelled 'an other' -> 'another'
>
>  3d-viewer/3d_viewer/eda_3d_viewer.h |  2 +-
>  common/gal/opengl/gl_builtin_shaders.cpp| 28 ++---
>  common/tool/common_tools.cpp|  2 +-
>  eeschema/sch_edit_frame.h   |  6 ++---
>  eeschema/sch_sheet_path.h   |  2 +-
>  eeschema/sim/netlist_exporter_pspice_sim.h  |  2 +-
>  gerbview/tools/selection_tool.h | 12 +
>  include/basic_gal.h |  2 +-
>  include/plotter.h   | 12 -
>  include/tool/action_manager.h   |  4 +--
>  include/tool/context_menu.h |  4 +--
>  include/tool/tool_event.h   |  2 +-
>  include/view/view.h | 12 -
>  pcbnew/connectivity_data.h  |  4 +--
>  pcbnew/dialogs/dialog_pns_settings_base.fbp |  2 +-
>  pcbnew/editrack-part2.cpp   |  2 +-
>  pcbnew/menubar_pcb_editor.cpp   |  2 +-
>  pcbnew/netinfo.h|  2 +-
>  pcbnew/pcb_base_frame.cpp   |  4 +--
>  pcbnew/tools/drawing_tool.h |  4 +--
>  pcbnew/tools/edit_points.h  |  6 ++---
>  pcbnew/tools/point_editor.cpp   |  4 +--
>  pcbnew/tools/selection_tool.h   |  9 ---
>  23 files changed, 66 insertions(+), 63 deletions(-)
>
> --
> 2.18.0
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad version and install location

[Nick Østergaard]

I created a ticket on launchpad in
https://bugs.launchpad.net/kicad/+bug/1780601

I have target it to the 5.0.0 milestone such that we can make sure we
discuss this in time.

Den søn. 8. jul. 2018 kl. 06.19 skrev Adam Wolf <
adamw...@feelslikeburning.com>:

> Let's postpone this discussion maybe until the 10th when Wayne is back at
> it.
>
> On Sat, Jul 7, 2018, 10:33 PM Mark Roszko  wrote:
>
>> Hey guys,
>>
>> So with 5.0 approaching theres something of an annoying problem on
>> windows (that many are complaining about). The install location!
>> Currently, even though you can install kicad into separate folders if
>> you wanted to, kicad still tries to write to the same appdata folder!
>>
>> Why would you want both the new and old? Because if you want to tweak
>> a old design, you don't want to risk opening it in newer versions and
>> having unforseen bugs. New designs sure, you really want to use the
>> latest and greatest, but the old is a risk not worth taking,
>> especially in the commercial field ;)
>>
>> Also there is a settings conflicts between 4.0 and 5.0 sharing appdata.
>>
>> I've seen some kicad forum "workarounds" where they use launcher
>> scripts that set KICAD_CONFIG_HOME each time. While it works, its
>> completely against the windows way :3
>>
>>
>> What I propose, is we patch KiCad a little to:
>>
>> 1. Write to appdata in a versioned manner (just minor and maybe minor
>> version)
>> C:\Users\%USERNAME%\AppData\Local\kicad 4.0\
>> C:\Users\%USERNAME%\AppData\Local\kicad 5.0\
>> C:\Users\%USERNAME%\AppData\Local\kicad 6.0\
>>
>> 2. Potentially prompt the user on first-start to copy settings.
>> (Maybe? Might be too much work for the final 5.0)
>>
>> Then we patch the installer to follow the convention of:
>> C:\Program Files\KiCad 4.0\
>> C:\Program Files\KiCad 5.0\
>> C:\Program Files\KiCad 6.0\
>>
>> This would do what every other CAD and IDE does on Windows (versioned
>> installs).
>>
>> But what if people want to install in crazier ways ?!
>> Well then that should beyond the scope of the "standard" installs and
>> they are on their own. (Just like other tools)
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad windows file associations

[Nick Østergaard]

Thank you.

Den søn. 8. jul. 2018 kl. 05.54 skrev Mark Roszko :

> Rejoice, the windows installer now setups file associations, icons and
> friendly names for kicad files.
>
> https://i.imgur.com/EcgnKmz.png
>
> I hope .sch and .pro get renamed to .kicad_sch and .kicad_pro in v6
> To avoid conflicts with Eagle and others.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Tkinter doesn't working in Pcbnew

[Nick Østergaard]

I have tested this on windows. I don't know if it is any problem on other
platform, I would not expect it to be.

Den søn. 8. jul. 2018 kl. 06.18 skrev Константин Барановский <
baranovskiykonstan...@gmail.com>:

> The Tkinter module is the standard Python interface to the Tk GUI toolkit.
> Inside KiCad Tkinter doesn't work and gives next error:
>
> from Tkinter import *
>> root = Tk()
>> Traceback (most recent call last):
>>   File "", line 1, in 
>>   File "C:\Program Files\KiCad\lib\python2.7\lib-tk/Tkinter.py", line
>> 1814, in __init__
>> baseName = os.path.basename(sys.argv[0])
>> AttributeError: 'module' object has no attribute 'argv'
>
>
> Attached patch resolves this issue by transfering values of argc and argv
> variables to python environment.
>
> For more details see:
> https://github.com/KiCad/kicad-winbuilder/issues/60
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] qa_geometry tests

[Nick Østergaard]

Hi

I guess we could add it to the qa target somehow? What I don't
particularyly like with this patch is that executing "make test" does not
check for dependency changes.

Back to the status about qa_geometry... it did pass a long time ago, doing
a bit of git bisect points at this commit as the one breaking the test.

fbf10e941bdf26bb3618aba0a1b7c44fd0bafed2 is the first bad commit
commit fbf10e941bdf26bb3618aba0a1b7c44fd0bafed2
Author: Jeff Young
Date:   Thu Mar 22 18:02:45 2018 +

Switch zone fillets to absolute-error algorithm.

And some general cleanup to related constants, etc.

:04 04 8b6ad8d44a7b38e0355ce5c8897f823d6255f811
8d54d43a9bd6e5062d6b804890a779e785e430cc Mcommon
:04 04 5a90dc20fe7cb3f74ae1768a5b5024a902c9354d
a2be92ebd64fd46ad17427e8e3c12da7f10df699 Minclude
:04 04 af9f333c0f56dca3a90fb7b04f385dbf39425e8d
99b5f9757c78216a08220b7eb056f343658b961d Mpcbnew


Den tor. 5. jul. 2018 kl. 12.13 skrev John Beard :

> Hi,
>
> Are the qa_geometry test supposed to all work?
>
> When I run `qa_geometry`, I get 1160 errors like this:
>
> error: in "ChamferFillet/Fillet": check { chainPoints.begin(),
> chainPoints.end() } == { polyPoints.begin(), polyPoints.end() } has
> failed.
>
> Mismatch at position 0: [ 40 | 14 ] != [ 40 | 12 ]
> Mismatch at position 1: [ 40 | 15 ] != [ 40 | 13 ]
> Mismatch at position 2: [ 44 | 10 ] != [ 40 | 14 ]
> Mismatch at position 3: [ 44 | 18 ] != [ 40 | 15 ]
> Mismatch at position 4: [ 50 | 10 ] != [ 40 | 16 ]
> Mismatch at position 5: [ 51 | 14 ] != [ 40 | 17 ]
> Collections size mismatch: 6 != 25
>
> Attached is a patch that enabled CTest tests and adds qa_geometry as a
> test. Then you can run `make test` or `ctest` to run all tests. I
> think it would be good to have a single unambigous and easily
> understood command to be able to run unit tests?
>
> This patch explicitly excludes the "ChamferFillet/Fillet" tests as
> they are failing, but if those tests can be fixed, it would be good to
> run them too.
>
> Cheers,
>
> John
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc3

[Nick Østergaard]

It is now available on http://downloads.kicad-pcb.org/docs/

Den tor. 5. jul. 2018 kl. 03.52 skrev Adam Wolf <
adamw...@feelslikeburning.com>:

> Ah, I see.  I meant a tarball of the output of the 5.0.0-rc3 tag.
> Something like http://docs.kicad-pcb.org/ has.
>
> Adam Wolf
> On Wed, Jul 4, 2018 at 12:05 PM Mark Roszko  wrote:
> >
> > https://github.com/KiCad/kicad-doc/archive/5.0.0-rc3.tar.gz
> >
> > from https://github.com/KiCad/kicad-doc/releases
> > On Wed, Jul 4, 2018 at 12:19 PM Adam Wolf 
> wrote:
> > >
> > > Is there a tarball of the tagged docs somewhere?
> > >
> > > Adam
> > >
> > > On Wed, Jul 4, 2018, 7:14 AM Steven A. Falco 
> wrote:
> > >>
> > >> Perfect!  Thanks.
> > >>
> > >> Steve
> > >>
> > >> On 07/04/2018 04:33 AM, Nick Østergaard wrote:
> > >> > kicad-doc and kicad-i18n is also tagged
> > >> >
> > >> > søn. 1. jul. 2018 00.34 skrev Rene Pöschl  <mailto:poesc...@gmail.com>>:
> > >> >
> > >> > template repo is now tagged (sorry forgot about that one)
> > >> >
> > >> > On 30/06/18 23:56, Steven A. Falco wrote:
> > >> > > Thank you!
> > >> > >
> > >> > > There are three repos not yet tagged with rc3 on github - two
> are probably awaiting translation work: kicad-doc and kicad-i18n.  Also not
> tagged: kicad-templates.  Once everything catches up to rc3, I will push
> them to Fedora Rawhide.
> > >> > >
> > >> > >   Steve
> > >> > >
> > >> > > On 06/30/2018 08:50 AM, Wayne Stambaugh wrote:
> > >> > >> I will do this when I tag rc3.  I think I have done it for
> every release tag.
> > >> > >>
> > >> > >> On 06/30/2018 08:28 AM, Steven A. Falco wrote:
> > >> > >>> If possible, it would also be great if a tar file for -rc3
> could be uploaded to launchpad, analogous to what was done for -rc2.
> > >> > >>>
> > >> > >>> We do have an -rc2 build in the official Fedora Rawhide
> now, and I'm ready to step that up to -rc3 once available.
> > >> > >>>
> > >> > >>>  Thanks,
> > >> > >>>  Steve
> > >> > >>>
> > >> > >>> On 06/29/2018 10:15 PM, Adam Wolf wrote:
> > >> > >>>> Folks, enjoy your vacations.  We've all earned them! :)
> > >> > >>>>
> > >> > >>>> Wayne, if you could please announce on the list when you
> tag rc3, that
> > >> > >>>> would be awesome.
> > >> > >>>>
> > >> > >>>> Thanks!
> > >> > >>>>
> > >> > >>>> Adam
> > >> > >>>> On Fri, Jun 29, 2018 at 7:27 PM Rene Pöschl <
> poesc...@gmail.com <mailto:poesc...@gmail.com>> wrote:
> > >> > >>>>> What a coincidence. I will also be out of town for the
> next one and a
> > >> > >>>>> half weeks.
> > >> > >>>>> As i can not guarantee that i will have internet access
> during this time
> > >> > >>>>> it might be necessary that somebody else tags the final
> kicad 5 library
> > >> > >>>>> release.
> > >> > >>>>> (I should be back at June the 10th late at night CET.)
> > >> > >>>>>
> > >> > >>>>> So i would suggest you make an issue one or two days
> before the intended
> > >> > >>>>> release date to notify the library team. (I already made
> one to warn
> > >> > >>>>> them about this fact. See:
> > >> > >>>>> https://github.com/KiCad/kicad-symbols/issues/712)
> > >> > >>>>>
> > >> > >>>>> On 30/06/18 01:59, Wayne Stambaugh wrote:
> > >> > >>>>>> I think we are good to go with rc3.  I'm going to tag it
> tomorrow unless
> > >> > >>>>>> something comes up between now and then.  Once rc3 is
> tagged, I would
> > >> > >>>

Re: [Kicad-developers] rc3

[Nick Østergaard]

kicad-doc and kicad-i18n is also tagged

søn. 1. jul. 2018 00.34 skrev Rene Pöschl :

> template repo is now tagged (sorry forgot about that one)
>
> On 30/06/18 23:56, Steven A. Falco wrote:
> > Thank you!
> >
> > There are three repos not yet tagged with rc3 on github - two are
> probably awaiting translation work: kicad-doc and kicad-i18n.  Also not
> tagged: kicad-templates.  Once everything catches up to rc3, I will push
> them to Fedora Rawhide.
> >
> >   Steve
> >
> > On 06/30/2018 08:50 AM, Wayne Stambaugh wrote:
> >> I will do this when I tag rc3.  I think I have done it for every
> release tag.
> >>
> >> On 06/30/2018 08:28 AM, Steven A. Falco wrote:
> >>> If possible, it would also be great if a tar file for -rc3 could be
> uploaded to launchpad, analogous to what was done for -rc2.
> >>>
> >>> We do have an -rc2 build in the official Fedora Rawhide now, and I'm
> ready to step that up to -rc3 once available.
> >>>
> >>>  Thanks,
> >>>  Steve
> >>>
> >>> On 06/29/2018 10:15 PM, Adam Wolf wrote:
>  Folks, enjoy your vacations.  We've all earned them! :)
> 
>  Wayne, if you could please announce on the list when you tag rc3, that
>  would be awesome.
> 
>  Thanks!
> 
>  Adam
>  On Fri, Jun 29, 2018 at 7:27 PM Rene Pöschl 
> wrote:
> > What a coincidence. I will also be out of town for the next one and a
> > half weeks.
> > As i can not guarantee that i will have internet access during this
> time
> > it might be necessary that somebody else tags the final kicad 5
> library
> > release.
> > (I should be back at June the 10th late at night CET.)
> >
> > So i would suggest you make an issue one or two days before the
> intended
> > release date to notify the library team. (I already made one to warn
> > them about this fact. See:
> > https://github.com/KiCad/kicad-symbols/issues/712)
> >
> > On 30/06/18 01:59, Wayne Stambaugh wrote:
> >> I think we are good to go with rc3.  I'm going to tag it tomorrow
> unless
> >> something comes up between now and then.  Once rc3 is tagged, I
> would
> >> like to hold off on any commits that are not critical bug fixes.
> Since
> >> I will be out of the country all next week for vacation, this will
> give
> >> users time to test rc3 builds.  If no critical issues arise during
> this
> >> week, I will tag 5.0.0 when I get back.  If this is an issue for our
> >> doc, library, or translation devs, please let me know.  Once our
> 5.0.0
> >> builds are ready to go, I will make the stable release announcement
> and
> >> proceed directly to the pub to celebrate.  We are getting close.
> Thanks
> >> again for all of your hard work.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>  ___
>  Mailing list: https://launchpad.net/~kicad-developers
>  Post to : kicad-developers@lists.launchpad.net
>  Unsubscribe : https://launchpad.net/~kicad-developers
>  More help   : https://help.launchpad.net/ListHelp
> 
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : 

Re: [Kicad-developers] Jenkins e-mails?

[Nick Østergaard]

at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
> at com.sun.proxy.$Proxy88.execute(Unknown Source)
> at
> hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
> at hudson.scm.SCM.checkout(SCM.java:504)
> at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
> at
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
> at hudson.model.Run.execute(Run.java:1794)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at
> hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> ERROR: Error cloning remote repo 'origin'
> [WARNINGS] Skipping publisher since build result is FAILURE
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
> On 29. Jun 2018, at 08:02, Nick Østergaard  wrote:
>
> No, this has not been disabled on purpose. I noticed this too, but I have
> also noticed that I actually works, the mailing list is receiving it, but I
> go not see it in my gmail inbox either.
>
> https://lists.launchpad.net/kicad-developers/msg36340.html
>
> So because of this I stopped to look for issues in Jenkins and just assume
> it was affecting me and I havd some crazy filter setup that throws it away.
>
> Maybe launchpad is not relaying the message.
>
> Nick
>
> fre. 29. jun. 2018 05.38 skrev Seth Hillbrand :
>
>> ​Hi Nick-
>>
>> I notice that the dev list is not receiving notices of build failures
>> from Jenkins.  But the build logs (e.g.
>> http://ci.kicad-pcb.org/job/kicad-qa/4320/console) show that Jenkins is
>> trying to send e-mails.
>>
>> Was this disabled on purpose?  If so, is there a way to get specifically
>> added to the notifications?
>>
>> Thanks-
>> Seth​
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Jenkins e-mails?

[Nick Østergaard]

No, this has not been disabled on purpose. I noticed this too, but I have
also noticed that I actually works, the mailing list is receiving it, but I
go not see it in my gmail inbox either.

https://lists.launchpad.net/kicad-developers/msg36340.html

So because of this I stopped to look for issues in Jenkins and just assume
it was affecting me and I havd some crazy filter setup that throws it away.

Maybe launchpad is not relaying the message.

Nick

fre. 29. jun. 2018 05.38 skrev Seth Hillbrand :

> ​Hi Nick-
>
> I notice that the dev list is not receiving notices of build failures from
> Jenkins.  But the build logs (e.g.
> http://ci.kicad-pcb.org/job/kicad-qa/4320/console) show that Jenkins is
> trying to send e-mails.
>
> Was this disabled on purpose?  If so, is there a way to get specifically
> added to the notifications?
>
> Thanks-
> Seth​
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

[Nick Østergaard]

I have put the upated image live now, and it seems to work. I will try to
revert the removal of the macros.

Den tor. 28. jun. 2018 kl. 23.21 skrev Nick Østergaard :

> Hi Seth
>
> Ok, thank you for your investigation. I will update the docker image to
> bionic which uses 0.52 of po4a.
>
> Nick
>
> Den tor. 28. jun. 2018 kl. 23.05 skrev Seth Hillbrand <
> seth.hillbr...@gmail.com>:
>
>> ​Bother.  po4a fixed this back in 2016 (
>> https://github.com/mquinson/po4a/commit/86f79e5d341ffcb62da9812101304c3dbb420cc6).
>> It looks like our doc server is running 0.47 (the fix didn't get released
>> until 0.49)
>>
>> -S
>>
>>
>>
>> Am Do., 28. Juni 2018 um 12:39 Uhr schrieb Wayne Stambaugh <
>> stambau...@gmail.com>:
>>
>>> Hey Adam,
>>>
>>> It will eventually be in the Kicad documentation at
>>>
>>> http://docs.kicad-pcb.org/stable/en/kicad.html
>>>
>>> There were some github macros that hauptmech added that broke the
>>> documentation build.  Apparently asciidoc was choking on them which is
>>> unfortunate as they made the github adoc conversion and viewing much
>>> nicer than our vanilla adoc files.  The commit to fix this was made
>>> 14hrs ago so it should be built soon.  Once the website is updated, you
>>> should be able to grab the link.  If you don't see it within 24 hours,
>>> please let me know an I will see if I can get it resolved.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 6/28/2018 1:32 PM, Adam Wolf wrote:
>>> > Hi Wayne,
>>> >
>>> > Has it been decided where this documentation will live?  Is it some
>>> > place with a URL?
>>> >
>>> > Thanks!
>>> >
>>> > Adam
>>> > On Sun, Jun 24, 2018 at 11:24 AM Wayne Stambaugh 
>>> wrote:
>>> >>
>>> >> hauptmech,
>>> >>
>>> >> I merged your patch and pushed the changes upstream to the kicad doc
>>> >> repo.  Thank you for the help with the documentation.
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Wayne
>>> >>
>>> >> On 06/23/2018 08:54 PM, hauptmech wrote:
>>> >>>
>>> >>> Attached
>>> >>>
>>> >>> On 24/06/18 02:46, Wayne Stambaugh wrote:
>>> >>>> Hey hauptmech
>>> >>>>
>>> >>>> For the most part I'm fine with these changes.  I think that the
>>> first
>>> >>>> two paragraphs (sentences) in the "Schematic Symbol Libraries"
>>> section
>>> >>>> of the version upgrade document could be merged into a single
>>> paragraph
>>> >>>> since they are related.
>>> >>>>
>>> >>>> If no one else objects to these changes, please create a merge
>>> request
>>> >>>> and I'll merge them into my repo and push them upstream today or
>>> >>>> tomorrow.
>>> >>>>
>>> >>>> Thanks for the help.
>>> >>>>
>>> >>>> Cheers,
>>> >>>>
>>> >>>> Wayne
>>> >>>>
>>> >>>> On 06/23/2018 12:15 AM, hauptmech wrote:
>>> >>>>> Hi Wayne,
>>> >>>>>
>>> >>>>> Really awesome that you are creating this documentation!
>>> >>>>>
>>> >>>>> A couple thoughts:
>>> >>>>> * No one reads documentation unless they have to. Usually after
>>> stabbing
>>> >>>>> in the dark for a while.
>>> >>>>> * If one has to read documentation, one wants it short and to the
>>> point.
>>> >>>>> * Whatever basic knowledge you want the reader to have about how
>>> kicad
>>> >>>>> works, they won't have it.
>>> >>>>>
>>> >>>>> With that in mind I did a little example editing with the following
>>> >>>>> goals:
>>> >>>>>
>>> >>>>> * Link to any info that is a requirement for understanding this
>>> >>>>> document. If you can't find any existing documentation to link to,
>>> >>>>> that's a good clue that

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

[Nick Østergaard]

Hi Seth

Ok, thank you for your investigation. I will update the docker image to
bionic which uses 0.52 of po4a.

Nick

Den tor. 28. jun. 2018 kl. 23.05 skrev Seth Hillbrand <
seth.hillbr...@gmail.com>:

> ​Bother.  po4a fixed this back in 2016 (
> https://github.com/mquinson/po4a/commit/86f79e5d341ffcb62da9812101304c3dbb420cc6).
> It looks like our doc server is running 0.47 (the fix didn't get released
> until 0.49)
>
> -S
>
>
>
> Am Do., 28. Juni 2018 um 12:39 Uhr schrieb Wayne Stambaugh <
> stambau...@gmail.com>:
>
>> Hey Adam,
>>
>> It will eventually be in the Kicad documentation at
>>
>> http://docs.kicad-pcb.org/stable/en/kicad.html
>>
>> There were some github macros that hauptmech added that broke the
>> documentation build.  Apparently asciidoc was choking on them which is
>> unfortunate as they made the github adoc conversion and viewing much
>> nicer than our vanilla adoc files.  The commit to fix this was made
>> 14hrs ago so it should be built soon.  Once the website is updated, you
>> should be able to grab the link.  If you don't see it within 24 hours,
>> please let me know an I will see if I can get it resolved.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 6/28/2018 1:32 PM, Adam Wolf wrote:
>> > Hi Wayne,
>> >
>> > Has it been decided where this documentation will live?  Is it some
>> > place with a URL?
>> >
>> > Thanks!
>> >
>> > Adam
>> > On Sun, Jun 24, 2018 at 11:24 AM Wayne Stambaugh 
>> wrote:
>> >>
>> >> hauptmech,
>> >>
>> >> I merged your patch and pushed the changes upstream to the kicad doc
>> >> repo.  Thank you for the help with the documentation.
>> >>
>> >> Cheers,
>> >>
>> >> Wayne
>> >>
>> >> On 06/23/2018 08:54 PM, hauptmech wrote:
>> >>>
>> >>> Attached
>> >>>
>> >>> On 24/06/18 02:46, Wayne Stambaugh wrote:
>>  Hey hauptmech
>> 
>>  For the most part I'm fine with these changes.  I think that the
>> first
>>  two paragraphs (sentences) in the "Schematic Symbol Libraries"
>> section
>>  of the version upgrade document could be merged into a single
>> paragraph
>>  since they are related.
>> 
>>  If no one else objects to these changes, please create a merge
>> request
>>  and I'll merge them into my repo and push them upstream today or
>>  tomorrow.
>> 
>>  Thanks for the help.
>> 
>>  Cheers,
>> 
>>  Wayne
>> 
>>  On 06/23/2018 12:15 AM, hauptmech wrote:
>> > Hi Wayne,
>> >
>> > Really awesome that you are creating this documentation!
>> >
>> > A couple thoughts:
>> > * No one reads documentation unless they have to. Usually after
>> stabbing
>> > in the dark for a while.
>> > * If one has to read documentation, one wants it short and to the
>> point.
>> > * Whatever basic knowledge you want the reader to have about how
>> kicad
>> > works, they won't have it.
>> >
>> > With that in mind I did a little example editing with the following
>> > goals:
>> >
>> > * Link to any info that is a requirement for understanding this
>> > document. If you can't find any existing documentation to link to,
>> > that's a good clue that we need to fill in more info locally.
>> > * Leave out as many extra words as possible.
>> >
>> >
>> https://github.com/hauptmech/kicad-doc/blob/master/src/kicad/kicad_upgrading_from_v4_to_v5.adoc
>> >
>> >
>> >
>> https://github.com/hauptmech/kicad-doc/blob/master/src/eeschema/eeschema_symbol_library_table.adoc
>> >
>> >
>> >
>> > It's not formatted as a patch because I only edited a few
>> paragraphs,
>> > and in those I rewrote things completely as an example of the above.
>> >
>> >
>> >
>> >
>> > On 23/06/18 04:10, Wayne Stambaugh wrote:
>> >> I pushed the v5 upgrade document to my personal repo[1] on git
>> hub.  I
>> >> made it part of the KiCad documentation but I don't have a strong
>> >> opinion about where to add it.  This just seemed like the most
>> logic
>> >> place.  Please review it when you get a chance.  If you find any
>> issues
>> >> let me know, send me a patch, or submit a pull request against my
>> doc
>> >> repo.  Keep in mind that this document is only to detail the
>> changes
>> >> that will effect project compatibility with older versions of
>> kicad and
>> >> the perils of symbol remapping.  Thanks in advance for the help.
>> >>
>> >> Cheers,
>> >>
>> >> Wayne
>> >>
>> >> [1]:
>> >>
>> https://github.com/stambaughw/kicad-doc/blob/master/src/kicad/kicad_upgrading_from_v4_to_v5.adoc
>> >>
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>> > 

Re: [Kicad-developers] Bug Tracker Milestone

[Nick Østergaard]

Hello Seth

I have created the following milestone names:

5.1.0
This is for fixes that are backportable from master, it could be string
fixes and minor features.


5.0.1
Post release fixes that does not involve string changes.


Att. Wayne, I would like you to say this is ok, or if we should use some
other names.

Nick

2018-06-21 18:10 GMT+02:00 Seth Hillbrand :

> ​Hi Devs-
>
> Can we get a v5.1 milestone on the bug tracker?  I'd like to start
> separating the items we are planning for the point release from the the v6
> release.  That way we can begin to discuss which belong where.
>
> It would probably be useful to also have a 5.0.1 milestone that we can
> assign post-release bugs to that don't involve string changes.
>
> ​Thanks-
> S​
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Add logo to documentation

[Nick Østergaard]

Mmm, I think I would prefer the Ki logo

man. 18. jun. 2018 10.11 skrev John Beard :

> In that case, here is the patch with the 48px app logo in the top left.
> Doxygen recommends 55px max height, so 48px seems a handy size.
>
> Screenshot for reference.
>
> Cheers,
>
> John
>
> On Sun, Jun 17, 2018 at 5:58 PM, Wayne Stambaugh 
> wrote:
>
>> I'm OK with the short logo image.  This would probably look better than
>> the redundant KiCad.
>>
>> On 06/17/2018 08:53 AM, John Beard wrote:
>> > Sadly I don't think there is a way to set the logo alt text in doxygen
>> > (so it would still read "KiCad" when the image is not displayed, for
>> > screen readers, when copy-pasted and it when search engines index it).
>> >
>> > Alternatively, use the square icon rather than the text logo and keep
>> > the title as it is?
>> >
>> > Cheers,
>> >
>> > John
>> >
>> > On Wed, Jun 13, 2018 at 11:18 PM, Wayne Stambaugh > > <mailto:stambau...@gmail.com>> wrote:
>> >
>> > I agree.  The double KiCad does look a bit odd but I do like the
>> > KiCad logo embedded in the docs.
>> >
>> > On 06/13/2018 06:00 PM, Nick Østergaard wrote:
>> >
>> > Maybe we need to remove the word KiCad from the title, as  it
>> > essentially reads  "[KiCad] KiCad Pcbnew Python Scripting"
>> >
>> >
>> > 2018-06-13 21:12 GMT+02:00 John Beard > > <mailto:john.j.be...@gmail.com> <mailto:john.j.be...@gmail.com
>> > <mailto:john.j.be...@gmail.com>>>:
>> >
>> > Sorry, I had a line commented in a local commit to avoid a
>> > costly
>> > re-build of the docstrings when I didn't need them to be
>> > (the doc
>> > dependencies aren't managed by CMake, it just always runs
>> the
>> > targets, which is fine for CI).
>> >
>> > The attached should be better (difference is a lack of a "#
>> > " before
>> > DEPENDS xml-to-docstrings)
>> >
>> > Cheers,
>> >
>> > John
>> >
>> > On Wed, Jun 13, 2018 at 8:04 PM, Wayne Stambaugh
>> > mailto:stambau...@gmail.com>
>> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
>> wrote:
>> >
>> > John,
>> >
>> > I am getting the following error when I try to apply
>> > your patch:
>> >
>> > $ git am --ignore-whitespace <
>> >
>> >
>>  
>> /c/Users/wstambaugh/Documents/Archive/temp/kicad/patches/0001-Documentation-add-logo-to-Doxygen-pages.patch
>> > Applying: Documentation: add logo to Doxygen pages
>> > error: patch failed: pcbnew/CMakeLists.txt:533
>> > error: pcbnew/CMakeLists.txt: patch does not apply
>> > Patch failed at 0001 Documentation: add logo to Doxygen
>> > pages
>> > Use 'git am --show-current-patch' to see the failed
>> patch
>> > When you have resolved this problem, run "git am
>> > --continue".
>> > If you prefer to skip this patch, run "git am --skip"
>> > instead.
>> > To restore the original branch and stop patching, run
>> > "git am
>> > --abort".
>> >
>> > It appears to be choking on the pcbnew/CMakeFile.txt.
>> Is it
>> > possible
>> > that you have other changes to this file that are not
>> in the
>> > master branch?
>> >
>> > Cheers,
>> >
>> > Wayne
>> >
>> > On 6/13/2018 1:50 PM, John Beard wrote:
>> >  > Hi,
>> >  >
>> >  > This patch adds a small KiCad logo to the three
>> doxygen
>> > documentation
>> >  > targets (C++, dev docs and Python docs) for a little
>> > bit more
>> > flair.
>> >  >
>> >  > The image itself is p

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

[Nick Østergaard]

Thank you that is good news.

Do you know if it also resolves the issues mentioned on
https://bugzilla.redhat.com/show_bug.cgi?id=1440904#c3

I was made aware of this from
https://github.com/KiCad/fedora-packaging/issues/7#issuecomment-397015599


2018-06-12 22:44 GMT+02:00 Holger Vogt :

> 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 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 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 free and
>> unfree software in Debian etc.).
>>
>> A power device model VDMOS is available
>>
>> pkg-config is generated
>>
>>
>> I have made some successful tests with recent KiCad nightly on Windows
>> using the demos delivered by KiCad.
>>
>>
>> Holger
>>
>>
>> ngspice maintainer
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Nick Østergaard]

Ok.

2018-06-14 9:37 GMT+02:00 Bernhard Stegmaier :

> I didn’t test this patch, but… something like a install prefix path is not
> valid for a bundle.
> A bundle is a self-contained entity and has no fixed location. You can put
> it wherever you want.
> So, everything has to be relative to main binary or bundle location.
>
>
> Regards,
> Bernhard
>
>
> On 14. Jun 2018, at 08:51, Nick Østergaard  wrote:
>
> It seems a bit strange to be that relative paths like that has to be used,
> can't some cmake install prefix path be used wheni is a bundle? Is this
> also how it is done for other parts of kicad?
>
> 2018-06-13 4:39 GMT+02:00 Adam Wolf :
>
>> 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
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Nick Østergaard]

It seems a bit strange to be that relative paths like that has to be used,
can't some cmake install prefix path be used wheni is a bundle? Is this
also how it is done for other parts of kicad?

2018-06-13 4:39 GMT+02:00 Adam Wolf :

> 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
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad doc build process

[Nick Østergaard]

The normal build job is up again.

2018-06-12 16:54 GMT+02:00 Marco Ciampa :

> 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:
> > >
> > > - who is in charge to run the machines that build the docs
> > >
> >
> > Ajo, but I primarely maintain it.
> >
> > - what is the frequency of the build process
> >
> > Every commit
> >
> > - where I can find the links to these machines (in the site)
> >
> > You browse Jenkins at ci.kicad-pcb.org
> >
> > The specific job is at http://ci.kicad-pcb.org/job/any-kicad-doc-head/
> >
> > It has been failing since
> > https://github.com/KiCad/kicad-doc/commit/f7e9226902156d79459ad63b1a9a39
> 3a3b5da829
> >
> > I guess that there are some new dependencies that needs to be installed
> as
> > of https://github.com/KiCad/kicad-doc/issues/588
>
> Ok will someone please make this working again?
>
> Every day it does not work I miss revisions from users...
>
> I can help if someone explains me how to or give me access to the system...
>
> TIA
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> 
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> 
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Add logo to documentation

[Nick Østergaard]

Maybe we need to remove the word KiCad from the title, as  it essentially
reads  "[KiCad] KiCad Pcbnew Python Scripting"


2018-06-13 21:12 GMT+02:00 John Beard :

> Sorry, I had a line commented in a local commit to avoid a costly re-build
> of the docstrings when I didn't need them to be (the doc dependencies
> aren't managed by CMake, it just always runs the targets, which is fine for
> CI).
>
> The attached should be better (difference is a lack of a "# " before
> DEPENDS xml-to-docstrings)
>
> Cheers,
>
> John
>
> On Wed, Jun 13, 2018 at 8:04 PM, Wayne Stambaugh 
> wrote:
>
>> John,
>>
>> I am getting the following error when I try to apply your patch:
>>
>> $ git am --ignore-whitespace <
>> /c/Users/wstambaugh/Documents/Archive/temp/kicad/patches/000
>> 1-Documentation-add-logo-to-Doxygen-pages.patch
>> Applying: Documentation: add logo to Doxygen pages
>> error: patch failed: pcbnew/CMakeLists.txt:533
>> error: pcbnew/CMakeLists.txt: patch does not apply
>> Patch failed at 0001 Documentation: add logo to Doxygen pages
>> Use 'git am --show-current-patch' to see the failed patch
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort".
>>
>> It appears to be choking on the pcbnew/CMakeFile.txt.  Is it possible
>> that you have other changes to this file that are not in the master
>> branch?
>>
>> Cheers,
>>
>> Wayne
>>
>> On 6/13/2018 1:50 PM, John Beard wrote:
>> > Hi,
>> >
>> > This patch adds a small KiCad logo to the three doxygen documentation
>> > targets (C++, dev docs and Python docs) for a little bit more flair.
>> >
>> > The image itself is put in the /Documentation dir, but it's not really
>> > important to the process where it goes.
>> >
>> > Cheers,
>> >
>> > John
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Nick Østergaard]

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, 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
> functionality. Thus the user is still vulnerable to Pcbnew internal API
> changes (and as Python is not a compiled language, they won't find out
> until it all explodes at runtime!). It's better than calling on the Pcbnew
> API directly (as there's only one place of breakage), but it's not a
> panacea, and was never really designed to be.
>
> However, these helpers also add some stuff that isn't just an API
> translation layer, it adds stuff like a transform stack and helpers for
> shapes like boxes and so on that would otherwise be repetitive in plugin
> code. All this can (and should) be transplanted onto a new "stable" Python
> interface in future.
>
> Cheers,
>
> John
>
> On Tue, Jun 12, 2018 at 2:47 PM, 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
>> https://github.com/kicad/kicad-python
>>
>> But the most recent work is on
>> https://github.com/pointhi/kicad-python
>>
>> Which is different from the initial work. I don't really know the state
>> of that work.
>>
>> I would like to see a supported API, but I guess this could be blocked
>> slightly because of the wxpython phoenix story.
>>
>>
>>
>> 2018-06-12 15:34 GMT+02:00 John Beard :
>>
>>> 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
>>> that's an acceptable way to present it.
>>>
>>> Cheers,
>>>
>>> John
>>>
>>> On Tue, Jun 12, 2018 at 2:11 PM, Nick Østergaard 
>>> wrote:
>>>
>>>> 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 GMT+02:00 Wayne Stambaugh :
>>>>
>>>>> 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 from the c++ source documentation.  I can commit your patch
>>>>> as is and you can make the doxygen changes in a later patch or I can
>>>>> wait for you to create a new patch with all of the changes.  I'm fine
>>>>> either way.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Wayne
>>>>>
>>>>> On 6/4/2018 7:33 AM, John Beard wrote:
>>>>> > Hi,
>>>>> >
>>>>> > Here is a simple patch sequence for the Python Footprint Wizard
>>>>> helpers:
>>>>> >
>>>>> > 1) Minor spelling and formatting tidy-up
>>>>> > 2) Add docstrings for the wizard base. As this is intended to be used
>>>>> > by writers of new plugins, having the functions documented is
>>>>> probably
>>>>> > a Good Idea (TM)
>>>>> > 3) Add rounded rectangle and chamfered rectangle helpers. Useful for
>>>>> > some footprints or even board outlines.
>>>>> >
>>>>> > I used Doxygen-style docstrings, 

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

[Nick Østergaard]

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 is on
https://github.com/pointhi/kicad-python

Which is different from the initial work. I don't really know the state of
that work.

I would like to see a supported API, but I guess this could be blocked
slightly because of the wxpython phoenix story.



2018-06-12 15:34 GMT+02:00 John Beard :

> 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
> that's an acceptable way to present it.
>
> Cheers,
>
> John
>
> On Tue, Jun 12, 2018 at 2:11 PM, Nick Østergaard 
> wrote:
>
>> 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 GMT+02:00 Wayne Stambaugh :
>>
>>> 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 from the c++ source documentation.  I can commit your patch
>>> as is and you can make the doxygen changes in a later patch or I can
>>> wait for you to create a new patch with all of the changes.  I'm fine
>>> either way.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 6/4/2018 7:33 AM, John Beard wrote:
>>> > Hi,
>>> >
>>> > Here is a simple patch sequence for the Python Footprint Wizard
>>> helpers:
>>> >
>>> > 1) Minor spelling and formatting tidy-up
>>> > 2) Add docstrings for the wizard base. As this is intended to be used
>>> > by writers of new plugins, having the functions documented is probably
>>> > a Good Idea (TM)
>>> > 3) Add rounded rectangle and chamfered rectangle helpers. Useful for
>>> > some footprints or even board outlines.
>>> >
>>> > I used Doxygen-style docstrings, but I haven't actually done anything
>>> > about building actual output docs with it. Any thoughts of if that
>>> > should be done, and if so, where to put it?
>>> >
>>> > There shouldn't be anything here that will break existing plugins, the
>>> > only API changes are additions.
>>> >
>>> > Cheers,
>>> >
>>> > John
>>> >
>>> >
>>> >
>>> > ___
>>> > Mailing list: https://launchpad.net/~kicad-developers
>>> > Post to : kicad-developers@lists.launchpad.net
>>> > Unsubscribe : https://launchpad.net/~kicad-developers
>>> > More help   : https://help.launchpad.net/ListHelp
>>> >
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Nick Østergaard]

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 GMT+02:00 Wayne Stambaugh :

> 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 from the c++ source documentation.  I can commit your patch
> as is and you can make the doxygen changes in a later patch or I can
> wait for you to create a new patch with all of the changes.  I'm fine
> either way.
>
> Cheers,
>
> Wayne
>
> On 6/4/2018 7:33 AM, John Beard wrote:
> > Hi,
> >
> > Here is a simple patch sequence for the Python Footprint Wizard helpers:
> >
> > 1) Minor spelling and formatting tidy-up
> > 2) Add docstrings for the wizard base. As this is intended to be used
> > by writers of new plugins, having the functions documented is probably
> > a Good Idea (TM)
> > 3) Add rounded rectangle and chamfered rectangle helpers. Useful for
> > some footprints or even board outlines.
> >
> > I used Doxygen-style docstrings, but I haven't actually done anything
> > about building actual output docs with it. Any thoughts of if that
> > should be done, and if so, where to put it?
> >
> > There shouldn't be anything here that will break existing plugins, the
> > only API changes are additions.
> >
> > Cheers,
> >
> > John
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Untranslated strings

[Nick Østergaard]

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 a couple of strings that are
> wxT() instead of _()​.  Example: cvpcb/display_footprints_frame.cpp:435.
>
> I have a preference for converting these to _(), even at this stage as
> worst-case is that they remain untranslated as they are now.  Does anyone
> object to this plan?  Is there a good reason to stay with wxT until after
> v5?
>
> -Seth
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad doc build process

[Nick Østergaard]

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 primarely maimtain it.

- what is the frequency of the build process
>

Every commit

- where I can find the links to these machines (in the site)
>

You browse Jenkins at ci.kicad-pcb.org

The specific job is at http://ci.kicad-pcb.org/job/any-kicad-doc-head/

It has been failing since
https://github.com/KiCad/kicad-doc/commit/f7e9226902156d79459ad63b1a9a39
3a3b5da829

I guess that there are some new dependencies that needs to be installed as
of https://github.com/KiCad/kicad-doc/issues/588

- how it works (for better undestanding of the whole process)
>   and how to check if, for instance, I did something wrong...
>

Check the build jon on Jenkins.

- where is (if there is) some docs for this whole process
>
>
It just does cmke amd make. no magic involved.

I think that if all this in not documented, why not document it?
>
>
There is no magic to document as such.

For my (very little) experience document processes is one of the best
> way to improve them...
>

I guess the best improvement we could wish for for the docs is faster build
times.  Historically we talked about comparing the build times and out with
asciidoctor vs asciidoc. I don't think we ever managed to get this done.


> TIA
>
> Best Regards,
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> 
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> 
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] eeschema GAL renderer (with old tools)

[Nick Østergaard]

It looks like loose text strings in symbols are not transformed correctly
in the tom-eeschema-gal branch I just tested. See attached image.

2018-06-04 22:55 GMT+02:00 Nick Østergaard :

> Ok, sorry, I see Eeli also saw that and you intend to fix it later. I will
> stay with make eeschema.
>
> 2018-06-04 22:53 GMT+02:00 Nick Østergaard :
>
>> Hi Tomasz,
>>
>> the build failed for me with:
>> [ 54%] Linking CXX shared module _cvpcb.kiface
>> ../common/libcommon.a(block_commande.cpp.o): In function
>> `BLOCK_SELECTOR::InitData(DRAW_PANEL_BASE*, wxPoint const&)':
>> /home/nickoe/kicad-source-mirror/common/block_commande.cpp:150:
>> undefined reference to `DrawAndSizingBlockOutlines(DRAW_PANEL_BASE*,
>> wxDC*, wxPoint const&, bool)'
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [cvpcb/CMakeFiles/cvpcb_kiface.dir/build.make:508:
>> cvpcb/_cvpcb.kiface] Error 1
>> make[1]: *** [CMakeFiles/Makefile2:818: 
>> cvpcb/CMakeFiles/cvpcb_kiface.dir/all]
>> Error 2
>> make: *** [Makefile:152: all] Error 2
>>
>> I also tried a make clean and then rebuild, but same issue.
>>
>> On commit "Added missing files" with SHA1:
>> 793d1db9612363be22eedc302c0f3974dbb65164
>>
>> 2018-06-04 21:40 GMT+02:00 Tomasz Wlostowski :
>>
>>> On 04/06/18 21:14, Seth Hillbrand wrote:
>>> > ​Hi Tom-
>>> >
>>> > Would you like feedback on any of this?  If so, what's most useful for
>>> > you?  Github issue tracker?  Merge requests?  Or just posts to the dev
>>> list?
>>>
>>> Hi Seth,
>>>
>>> Patches & posts to the devlists are my favourite :)
>>>
>>> Cheers,
>>> Tom
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] eeschema GAL renderer (with old tools)

[Nick Østergaard]

Ok, sorry, I see Eeli also saw that and you intend to fix it later. I will
stay with make eeschema.

2018-06-04 22:53 GMT+02:00 Nick Østergaard :

> Hi Tomasz,
>
> the build failed for me with:
> [ 54%] Linking CXX shared module _cvpcb.kiface
> ../common/libcommon.a(block_commande.cpp.o): In function
> `BLOCK_SELECTOR::InitData(DRAW_PANEL_BASE*, wxPoint const&)':
> /home/nickoe/kicad-source-mirror/common/block_commande.cpp:150: undefined
> reference to `DrawAndSizingBlockOutlines(DRAW_PANEL_BASE*, wxDC*, wxPoint
> const&, bool)'
> collect2: error: ld returned 1 exit status
> make[2]: *** [cvpcb/CMakeFiles/cvpcb_kiface.dir/build.make:508:
> cvpcb/_cvpcb.kiface] Error 1
> make[1]: *** [CMakeFiles/Makefile2:818: cvpcb/CMakeFiles/cvpcb_kiface.dir/all]
> Error 2
> make: *** [Makefile:152: all] Error 2
>
> I also tried a make clean and then rebuild, but same issue.
>
> On commit "Added missing files" with SHA1:
> 793d1db9612363be22eedc302c0f3974dbb65164
>
> 2018-06-04 21:40 GMT+02:00 Tomasz Wlostowski :
>
>> On 04/06/18 21:14, Seth Hillbrand wrote:
>> > ​Hi Tom-
>> >
>> > Would you like feedback on any of this?  If so, what's most useful for
>> > you?  Github issue tracker?  Merge requests?  Or just posts to the dev
>> list?
>>
>> Hi Seth,
>>
>> Patches & posts to the devlists are my favourite :)
>>
>> Cheers,
>> Tom
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] eeschema GAL renderer (with old tools)

[Nick Østergaard]

Hi Tomasz,

the build failed for me with:
[ 54%] Linking CXX shared module _cvpcb.kiface
../common/libcommon.a(block_commande.cpp.o): In function
`BLOCK_SELECTOR::InitData(DRAW_PANEL_BASE*, wxPoint const&)':
/home/nickoe/kicad-source-mirror/common/block_commande.cpp:150: undefined
reference to `DrawAndSizingBlockOutlines(DRAW_PANEL_BASE*, wxDC*, wxPoint
const&, bool)'
collect2: error: ld returned 1 exit status
make[2]: *** [cvpcb/CMakeFiles/cvpcb_kiface.dir/build.make:508:
cvpcb/_cvpcb.kiface] Error 1
make[1]: *** [CMakeFiles/Makefile2:818:
cvpcb/CMakeFiles/cvpcb_kiface.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

I also tried a make clean and then rebuild, but same issue.

On commit "Added missing files" with SHA1:
793d1db9612363be22eedc302c0f3974dbb65164

2018-06-04 21:40 GMT+02:00 Tomasz Wlostowski :

> On 04/06/18 21:14, Seth Hillbrand wrote:
> > ​Hi Tom-
> >
> > Would you like feedback on any of this?  If so, what's most useful for
> > you?  Github issue tracker?  Merge requests?  Or just posts to the dev
> list?
>
> Hi Seth,
>
> Patches & posts to the devlists are my favourite :)
>
> Cheers,
> Tom
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KICAD_CACHE_HOME environment variable

[Nick Østergaard]

It looks like it works as intended, but I don't think the naming is that
good. Maybe it might be better to call it KICAD_RUNTIME_DIR analogous to
XDG terminology used elsewhere and nearby...

If it is called KICAD_CACHE_HOME one would think that this would control
the location of the 3d cache too, which is really inside the config dir.

So if is renamed to KICAD_RUNTIME_DIR might be better. But it is a bit
strange that XDG_CACHE_HOME is caught in the lockfile management too.

2018-05-14 23:39 GMT+02:00 Mike Wodarczyk :

> On 08.05.2018 02:57, Mike Wodarczyk wrote:
>
>> Attached is a patch to use a new KICAD_CACHE_HOME environment variable to
>> set a custom path for the lockfiles on all platforms. It's tested under
>> Windows and works as expected.
>>
>> Oops attached the wrong file. This is the compiling patch. Sorry for the
> inconvience :-)
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] V5 tag in bug tracker?

[Nick Østergaard]

I figured I just made it since no 5.0.0 was made.

I agree with Simon that we are likely to have an rc3. We can just rename
the milestone if we change our mind. Afterall it does not cost us anything.

2018-05-28 14:25 GMT+02:00 Wayne Stambaugh :

> On 05/26/2018 04:13 PM, Simon Richter wrote:
>
>> Hi,
>>
>> On 26.05.2018 16:40, Wayne Stambaugh wrote:
>>
>> Do we really need an rc3?  I was going to make 5.0.0 the next milestone.
>>>   I think (hope) most of the bug fixes will be polishing at this point.
>>>
>>
>> If we're not going to release rc2 as it is, then it makes sense to make
>> an rc3, test it, and retag it as the release if we decide to not change
>> anything anymore.
>>
>
> Seems a bit redundant but OK.
>
>
>
>> Simon
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] V5 tag in bug tracker?

[Nick Østergaard]

I created a 5.0.0-rc3 milestone.

2018-05-26 1:30 GMT+02:00 Seth Hillbrand :

> Now that RC2 is released, can we get a new target in the bug tracker for
> things that should be fixed prior to v5 release?  Currently, we only have
> v6 as a target
>
> Thanks-
> Seth
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Footprint Library Wizard removal

[Nick Østergaard]

Is this the one from the Browse Libraries... from the fp-lib-table dialog?

2018-05-25 11:10 GMT+02:00 Maciej Sumiński :

> Thank you for the feedback. I have fixed the reported issues (disabled
> "Show Hidden", made the dialog resizable and ${KIRPRJMOD} substitution)
> and pushed the changes.
>
> Cheers,
> Orson
>
> On 05/25/2018 09:20 AM, jp charras wrote:
> > Le 24/05/2018 à 19:49, jp charras a écrit :
> >> Le 24/05/2018 à 10:19, Maciej Sumiński a écrit :
> >>> Attached a revised patch set, as the previous one looked ugly on
> Windows
> >>> (and fine on Linux).
> >>
> >> Thanks Orson.
> >>
> >> The look of this dialog is much better now.
> >>
> >> Just two remarks about the dialog itself: the dialog is not re-sizable,
> and should be derived from
> >> our DIALOG_SHIM base class.
> >>
> >
> > Hi Orson,
> >
> > I noticed an other issue (a regression):
> >
> > When a library is added, if it is in the project folder, its path is
> stored as an absolute path, and
> > the ${KIPRJMOD} env var is not used to build the path.
> >
> >>
> >>>
> >>> Cheers,
> >>> Orson
> >>>
> >>> On 05/23/2018 12:17 PM, Maciej Sumiński wrote:
>  As it has been reported [1], the Footprint Library Wizard is
> restricted
>  to the old Github repositories (one repo per library vs current single
>  repo for all libraries). I propose to replace it with a common file
>  browser, similar to the one in the Symbol Library Table dialog. In the
>  future we may develop a separate dialog to update the local libraries,
>  using a genuine git client letting us any repository (not only
> Github),
>  perhaps traverse through commits and display logs.
> 
>  I could not use the standard file dialog, as wxWidgets does not
> provide
>  one to select both files *and* directories, but it is necessary to
>  handle both .pretty libraries (directories) and foreign formats (e.g.
>  Eagle .lbr files) with a single dialog.
> 
>  Github plugin is still available, but has to be selected manually in
> the
>  Footprint Library Table dialog. I think it is reasonable not to expose
>  it, as it brings troubles to inexperienced users.
> 
>  AFAICT, the attached patch introduces one new string ("Show Hidden" in
>  the selector dialog), breaking the string freeze rule. The string is
> not
>  crucial, so it might be removed for the time being.
> 
>  Cheers,
>  Orson
> >>
> >>
> >
> >
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Call for Translators?

[Nick Østergaard]

I think 80% is too high. Actually I think we should just ship the
translations that has had any contribution within the string freeze period.
It could be an incitement for a random contributor to see that some strings
are actually translated. And then hopefully most of the work they may do
can be included in the next minor release. In reality we just tag it and
let the packager decide if they want to package the language.

I don't like hiding peoples work.

2018-05-22 9:56 GMT+02:00 Marco Ciampa :

> On Mon, May 21, 2018 at 04:07:31PM -0700, Seth Hillbrand wrote:
> > Hi Devs-
> >
> > Now that Wayne has declared rc2 and strings are frozen, does anyone have
> > objections to my posting a call for translators to the user forum?  I
> just
> > checked the open items and it looks like there are a few languages that
> > haven't been touched in a number of years, so I thought we might ask for
> > some input, especially for ones like sl, ko, sv, hu, etc...
> >
> > The post would direct people to the translation GitHub [1] and give some
> > basics on how to be a considerate contributor.
> >
> > Thoughts?
>
> Just one: consider a percentage limit, say 80%, under which a translation
> should be discarded. I don't mind (and it is difficult to check) bad
> translations, but a program half translated and half not is not
> acceptable, IMHO.
>
> This could be an issue for packagers though, accepting just fairly
> complete translations to include in the packages, and leaving the
> translated strings untouched in the source.
>
> Comments?
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> 
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> 
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Call for Translators?

[Nick Østergaard]

Hi Seth,

I have sometimes sent out an email directly to some of the "usual" and
recent translators for languages that were missing updates. I have been
playing with the thought of using something like transifex for the
translations, but I decided not to use that because I can not see how it
can integrate with having people submit pull request in github and keep the
translations in sync without loosing strings in a nightly workflow.

As we are in string freeze we could try to upload for languages that are
not very up to date from submitters via github. This could lower the
barrier to entry for some people for some languages. I am mostly thinking
about the GUI translations and not the documentation.

Nick

2018-05-22 1:21 GMT+02:00 Wayne Stambaugh :

> Seth,
>
> On 05/21/2018 07:07 PM, Seth Hillbrand wrote:
> > ​Hi Devs-
> >
> > Now that Wayne has declared rc2 and strings are frozen, does anyone have
> > objections to my posting a call for translators to the user forum?  I
> > just checked the open items and it looks like there are a few languages
> > that haven't been touched in a number of years, so I thought we might
> > ask for some input, especially for ones like sl, ko, sv, hu, etc...
> >
> > The post would direct people to the translation GitHub [1] and give some
> > basics on how to be a considerate contributor.
> >
> > Thoughts?
> > -Seth
> >
> > [1] https://github.com/KiCad/kicad-i18n
>
> I'm fine with this.  Maybe we can find a ringer or two to help out with
> the translations.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0 RC2 / release status

[Nick Østergaard]

A bug related to some recent changes is
https://bugs.launchpad.net/kicad/+bug/1769143

It sounds simple, but I don't know if it is.

2018-05-19 9:24 GMT+02:00 Andrey Kuznetsov :

> What about this bug for MacOS that makes it too frustrating to use
> eeschema?
>
> Basically, I cannot navigate by zooming around in eeschema because the
> mouse scroll triggers on fine steps of the scroll wheel instead of the
> larger ratchet steps, it's not just that this is a granularity issue it's a
> consistency of navigation issue because when the scroll wheel springs back
> to the ratchet position of the original zoom, the actual zoom level is
> different and I have to play with the scroll wheel until the zoom level
> looks OK. Coupled with a HiDPI display which slows down Eeschema and GOOD
> BYE KiCAD on MacOS, it's too frustrating.
>
> https://bugs.launchpad.net/kicad/+bug/1753054
>
> On Fri, May 18, 2018 at 2:45 PM, Wayne Stambaugh 
> wrote:
>
>> Hi Rene,
>>
>> On 05/18/2018 11:53 AM, Rene Pöschl wrote:
>> > On 18/05/18 16:44, Wayne Stambaugh wrote:
>> >> If any of our doc and library devs are on this mailing list, please
>> >> forward this information so we aren't making major changes to the docs
>> >> and libraries at the last minute.
>> >>
>> >
>> > We have one important pull request open that i will fix up my self
>> > tomorrow if the contributor does not fix the remaining issues him self.
>> > (Removing duplicate power pins from symbols as this can be quite
>> > dangerous if the user connects them multiple times.)
>> >
>> > After this is merged i will tag the library with "5.0.0-rc2" (Tomorrow
>> > evening)
>> >
>> > After this tag is set we will no longer allow renaming of libs until v6
>> > development. (Adding new libs will still be allowed.)
>>
>> I'm OK with this.
>>
>> >
>> > I will also create a kicad 4 compatibility backport for this lib. (The
>> > intention is to allow users to use the new library structure for new
>> > projects even if they can not update to a nightly build. This should
>> > reduce their work when they then switch over to kicad 5)
>> >
>> > This backport will contain a reduced number of footprints as footprints
>> > with custom or roundrect pads are not supported by kicad 4. I will also
>> > backport the symbol libs. The 3d lib does not need any work in this
>> > regard but i will still ad a separate release tag to make it easier for
>> > users. Not sure if i will make a backport of the templates.
>> > Creating this backport will take some time but i hope to have it done
>> > one week after the rc2 tag is set.
>>
>> Awesome!  I'm sure our v4 users will appreciate this.
>>
>> >
>> >
>> > Regarding the issue about footprint connection you reported in [1]:
>> > All symbols that have a valid symbol in the footprint lib are now
>> > correctly connected. Sadly a lot of symbols still need footprints to be
>> > generated. (Symbols where in the lib that never had a valid footprint)
>> > Some of this will be fixed after the rc2 release. This will not impact
>> > the library structure so i assume we can include these changes in the
>> > final v5 release. (It will simply add more footprints.)
>>
>> That fine by me.  If we are going add new symbol libraries during v5, I
>> don't see any reason not to add new footprints and footprint libraries.
>> We should try to avoid wholesale renaming and/or moving of libraries and
>> their contents to avoid headaches for users.  If we have any major
>> library reorganizations, we can always create a v5 branch as we do for
>> the KiCad source.
>>
>> Thank you for all of your hard work on the libraries.  They really have
>> come a long way since v4 was released.
>>
>> Cheers,
>>
>> Wayne
>>
>> >
>> > [1]: https://github.com/KiCad/kicad-symbols/issues/520
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Remember The Past, Live The Present, Change The Future
> Those who look only to the past or the present are certain to miss the
> future [JFK]
>
> kandre...@gmail.com
> Live Long and Prosper,
> Andrey
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : 

Re: [Kicad-developers] Initial rc6 development.

[Nick Østergaard]

As far ad I understand it SWIG and SIP are not compatible, so sonethung is
needed to transition to SIP, but given wxpython is pushing phoenix thay is
what we need to do, and with that we also gain gtk3 support.

fre. 18. maj 2018 18.13 skrev Wayne Stambaugh <stambau...@gmail.com>:

> On 05/18/2018 12:02 PM, Nick Østergaard wrote:
> > For wxpython, we "just" need to upgrade to phoenix, which supports gtk3.
>
> Has this been verified on all platforms?  I thought there were issues
> with our use of swig and the use of sip by the phoenix project.  If it's
> a drop in, all the better.
>
> >
> > 2018-05-18 18:01 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>>:
> >
> > Hi Tom,
> >
> >
> > On 05/18/2018 11:51 AM, Tomasz Wlostowski wrote:
> >
> > On 18/05/18 17:38, Wayne Stambaugh wrote:
> >
> > As we approach the v5 stable release, I want to discuss a
> > something we
> > should seriously consider before we open the flood gates for
> > new feature
> > merges after the v5 branch.  We are currently in an awkward
> > position
> > with regards to gtk3 builds on Linux.  Given that most
> > distros are now
> > building wx against gtk3, we really should work towards
> > fixing this at
> > the beginning of v6 and back porting it as soon as possible
> > so that we
> > can better support the current Linux distros.  Fortunately,
> > most distros
> > have thankfully provided a gtk2 build version of wx in order
> > to build
> > kicad.  However, they have not done the same thing for
> > wxpython so for
> > most new distro releases, we have to build kicad without
> > wxpython
> > support.  I propose we spend some time immediately after the
> > v5 release
> > and fix the gtk3 issues before we start making major changes
> > to the code
> > base so that it is not difficult to back port.  Anyone else
> > have any
> > thoughts on this?
> >
> >
> > Wayne,
> >
> > I would put most of the effort on developing the GAL version of
> > eeschema. It's not our fault that Linux distros change the APIs
> of
> > essential system libraries every 2 years. As a short term
> > solution, I
> > would propose distributing a distro-agnostic binary Kicad
> > package that
> > includes all dependencies, including wx and gtk2 libraries. In
> the
> > longer run, GALified schematic editor is IMHO the way to go.
> >
> > Best,
> > Tom
> >
> >
> > This still doesn't address the wxpython issue or the fact that v5
> > will always have to support gtk2.  Given our current stable release
> > turnover, it could (will?) be a few years before v6 is released.  It
> > also doesn't address the fact that the legacy canvas in eeschema
> > which will be part of v6 will require gtk2.  While a agree that this
> > is going to be a PITA, I just don't see how we can avoid it.
> >
> >
> >
> >
> >
> > Cheers,
> >
> > Wayne
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> >
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Initial rc6 development.

[Nick Østergaard]

For wxpython, we "just" need to upgrade to phoenix, which supports gtk3.

2018-05-18 18:01 GMT+02:00 Wayne Stambaugh :

> Hi Tom,
>
>
> On 05/18/2018 11:51 AM, Tomasz Wlostowski wrote:
>
>> On 18/05/18 17:38, Wayne Stambaugh wrote:
>>
>>> As we approach the v5 stable release, I want to discuss a something we
>>> should seriously consider before we open the flood gates for new feature
>>> merges after the v5 branch.  We are currently in an awkward position
>>> with regards to gtk3 builds on Linux.  Given that most distros are now
>>> building wx against gtk3, we really should work towards fixing this at
>>> the beginning of v6 and back porting it as soon as possible so that we
>>> can better support the current Linux distros.  Fortunately, most distros
>>> have thankfully provided a gtk2 build version of wx in order to build
>>> kicad.  However, they have not done the same thing for wxpython so for
>>> most new distro releases, we have to build kicad without wxpython
>>> support.  I propose we spend some time immediately after the v5 release
>>> and fix the gtk3 issues before we start making major changes to the code
>>> base so that it is not difficult to back port.  Anyone else have any
>>> thoughts on this?
>>>
>>>
>> Wayne,
>>
>> I would put most of the effort on developing the GAL version of
>> eeschema. It's not our fault that Linux distros change the APIs of
>> essential system libraries every 2 years. As a short term solution, I
>> would propose distributing a distro-agnostic binary Kicad package that
>> includes all dependencies, including wx and gtk2 libraries. In the
>> longer run, GALified schematic editor is IMHO the way to go.
>>
>> Best,
>> Tom
>>
>
> This still doesn't address the wxpython issue or the fact that v5 will
> always have to support gtk2.  Given our current stable release turnover, it
> could (will?) be a few years before v6 is released.  It also doesn't
> address the fact that the legacy canvas in eeschema which will be part of
> v6 will require gtk2.  While a agree that this is going to be a PITA, I
> just don't see how we can avoid it.
>
>
>
>>
>>
>> Cheers,
>>>
>>> Wayne
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

[Nick Østergaard]

The occ patch makes the build fail on macos when enabling oce. I don't
understanf why the error message suggest the occ path instead of the occ
one. Also I don't understand why the defualt would not work as before.

http://ci.kicad-pcb.org/job/osx-kicad-adam-head/659/console


tir. 20. mar. 2018 00.50 skrev Seth Hillbrand <seth.hillbr...@gmail.com>:

> Nick, as always, thanks for the detailed helpful comments.  To specify the
> installation, we will need to set -DOCC_LIBRARY_DIR and -DOCC_INCLUDE_DIR.
> That works on my machine and the docker file.
>
> I'll implement your suggestions and give people another few days to test
> if they're interested in this topic before merging.
>
> Best-
> Seth
>
> 2018-03-18 15:57 GMT-07:00 Nick Østergaard <oe.n...@gmail.com>:
>
>> Hi Seth,
>>
>> I tried to test your patch. It bascially works. Some observations follows:
>>
>> I think the message printed from cmake
>> "from /opt/oce/lib/libTKernel.so I found /opt/oce/lib"
>> should be removed from the output, it looks liek a debug message to me. I
>> guess the same information is available in the CMakeCache.txt if needed
>> later on.
>>
>> It defaults to OCE as expected, builds, and runs.
>>
>> If I remove OCE it will find my normal opencascade installation, builds
>> and runs.
>>
>> I think it also did use OCC if I set KICAD_USE_OCC=ON, where it built and
>> ran fine. But when this happens I still see KICAD_USE_OCE=ON in the cache.
>> This might be ok, but could be confusing.
>>
>> I canẗ make it use an alterntive install location of OCC, I tried to set
>> OCC_INCLUDE_DIR=/opt/opencascade7/inc. This fails. What variable do I need
>> to set to select another version of opencascade?
>>
>> I tested this on archlinux. I think it could be improved to be less
>> errorprone, but could possibly be comitted as is if that debug log is
>> removed. It seems to work fine if you are not switching between OCE and OCC
>> in the same build dir, that is, a clean config.
>>
>> Nick
>>
>>
>> 2018-03-17 0:51 GMT+01:00 Nick Østergaard <oe.n...@gmail.com>:
>>
>>> Thank you very much, I will try to remember it after the weekend.
>>>
>>> 2018-03-17 <20%2018%2003%2017> 0:46 GMT+01:00 Seth Hillbrand <
>>> seth.hillbr...@gmail.com>:
>>>
>>>> Hi Nick-
>>>>
>>>> I finally found a moment to figure out Docker and get this up and
>>>> running in your build configuration.
>>>>
>>>> Please take a look when you have a chance and let me know if you have
>>>> any issues with this patch.
>>>>
>>>> Best-
>>>> Seth
>>>>
>>>> 2018-02-10 <20%2018%2002%2010> 7:12 GMT-08:00 Seth Hillbrand <
>>>> seth.hillbr...@gmail.com>:
>>>>
>>>>> Nick was having an unknown issue but I haven't heard back from him on
>>>>> whether the issue was resolved by doing a clean cmake.  If it isn't then
>>>>> I'll need to address that.
>>>>>
>>>>> Nick did you have a chance to test that?
>>>>>
>>>>> -S
>>>>>
>>>>> 2018-02-10 <20%2018%2002%2010> 6:18 GMT-08:00 Wayne Stambaugh <
>>>>> stambau...@gmail.com>:
>>>>>
>>>>>> Seth,
>>>>>>
>>>>>> What is the current status of this patch?  I would like to get it
>>>>>> merged
>>>>>> before rc1 so the package devs can test it.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Wayne
>>>>>>
>>>>>> On 01/30/2018 02:12 PM, Seth Hillbrand wrote:
>>>>>> > Nick-
>>>>>> >
>>>>>> > Thanks for the test.  I'm attaching revised patch that allows
>>>>>> multiple
>>>>>> > OpenCASCADE installations on a single machine.
>>>>>> >
>>>>>> > I've tested with a few different OpenCASCADE versions down to 6.8
>>>>>> with
>>>>>> > no issues installed alongside OCE 0.17.  You can choose which you
>>>>>> want
>>>>>> > to link by using either "-DKICAD_USE_OCE" or "-DKICAD_USE_OCC".  If
>>>>>> both
>>>>>> > are specified, "-DKICAD_USE_OCC" will override.
>>>>>> >
>>>>>> > I corrected the cma

Re: [Kicad-developers] [PATCH] Add python apis: GetLogicalLibs, FootprintsInLib and FootprintInfo

[Nick Østergaard]

See the unittests in the qa folder. Thay are executed by the build job also.

ons. 9. maj 2018 15.25 skrev miles mccoo :

> Thank you, Jeff, for taking the time to look at my patch.
>
> attached is a new version of the patch. I've changed a couple things:
>
>- fixed the curly brace issue
>- added blanks before each of the if statements
>- I added a short test python function to the checkin comments[1]. It
>exercises the new functionality[2]
>- I added an additional function to instantiate a footprint. The only
>other such function I'm aware of wants a full path to a library. This one
>just takes the name of the lib
>
>
> I've also posted the patch here:
> http://mmccoo.com/random/0001-Add-the-python-apis-GetLogicalLibs-FootprintsInLib-I.patch
>
>
> Miles
>
> [1] There's a thread on the developer list complaining about the poor
> comments. That thread focuses on the symbol or footprint libraries. I'd
> like to take this opportunity to comment that check comment and comments in
> general in the kicad project they kinda suck. The code itself contains
> very little in the way of explanation. The checkin comments are terse. I
> haven't found any kind of design documents or discussion on the mail list.
>
> Hopefully someone will correct me.
>
>
> [2] does kicad have anything in the way of a regression? It would be nice
> to have some python code to be periodically executed. Compile errors is one
> thing, but a couple APIs have disappeared in the last year. Such scripting
> might have caught that.
>
>
>
> On Tue, May 8, 2018 at 5:36 PM, Jeff Young  wrote:
>
>> Hi Miles,
>>
>> The only coding style issue I saw was that there should be blank lines
>> above “if” statements.
>>
>> Oh, and there’s still a K brace.  Search for "if ( footprint )
>> {“.  (The brace should be down on its own line.)
>>
>> I didn’t correct these and merge your patch as I can’t get scripting to
>> build on my Mac so there’s no way for me to do a quick sanity test.
>>
>> Cheers,
>> Jeff.
>>
>>
>> On 4 May 2018, at 09:17, miles mccoo  wrote:
>>
>>
>>
>> I submitted this patch before, but it fell through the cracks.
>>
>> This patch makes it possible to query pcbnew for a list of footprint
>> libraries, and the footprints contained therein. (without reading fp-lib
>> myself)
>>
>>
>> my previous attempt:
>> https://lists.launchpad.net/kicad-developers/msg35236.html
>> It has some implementation notes that may be of interest.
>>
>>
>> I believe I have followed the coding guidelines which I have read several
>> times. If I missed something, please indicate more than "follow the
>> guidelines". At least a theme. (trailing space, curlies,...)
>>
>>
>> Since attachments don't seem to make it to the launchpad site, I've also
>> made the patch file available here:
>>
>> http://mmccoo.com/random/0001-Add-the-python-apis-GetLogicalLibs-FootprintsInLib-a.patch
>>
>>
>> Miles
>> <0001-Add-the-python-apis-GetLogicalLibs-FootprintsInLib-a.patch>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] XDG_CONFIG_HOME environment variable.

[Nick Østergaard]

I vote for accepting XDG_CONFIG_HOME on all platforms for consistency.
After all this is an advanced configuration feature and should not be
touched by the normal user.

I don't know why the patch was made so complex initially.

2018-05-07 15:54 GMT+02:00 Adam Wolf :

> I do not think it will cause an issue on macOS.
>
> Adam
>
> On Mon, May 7, 2018 at 8:50 AM, Wayne Stambaugh 
> wrote:
> > I am in the process of fixing a minor bug in the code that fetches the
> > KiCad user configuration path.  We currently only check for the
> > XDG_CONFIG_HOME environment variable on non-windows and non-macos
> > platforms.  Is there any reason not to just go ahead and check for
> > XDG_CONFIG_HOME on all platforms?  I know in the past someone requested
> > that we allow it on windows to create a portable windows version of
> > KiCad.  Is there anything on macos where using this could trip us up?
> > If not, it will eliminate an ugly #if/#endif section in this code.
> >
> > Thanks,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Fwd: Re: [PATCH] Adjust Menubar of 3D Viewer to common style

[Nick Østergaard]

Remember that a ascii freindly version can be used in the source and then
we can use the  unicode char in the translations. This is the reason there
is also a po file for english.

2018-05-04 17:59 GMT+02:00 jp charras :

>
>  Message transféré 
> Sujet : Re: [Kicad-developers] Fwd: Re: [PATCH] Adjust Menubar of 3D
> Viewer to common style
> Date : Thu, 3 May 2018 20:14:21 +0100
> De : Ruth Ivimey-Cook 
> Pour : jp charras 
>
> JP
>
> On 03/05/2018 18:45, jp charras wrote:
> > No.
> > Because only ASCII7 chars are allowed in strings to translate, because,
> AFAIK, I18N tools only
> > accept ASCII7 chars, not unicode char set.
> >
>
> I'm not quite sure if I've missed something, but it seems from:
>
> http://docs.wxwidgets.org/3.0.4/overview_unicode.html#
> overview_unicode_support_default
>
> that the ASCII7 limitation refers only to the compiled text file when
> using standard strings; and it
> seems the use of character escapes or L"" (wide) strings is supported.
>
> They give the examples:
>
> wxMessageBox(L"Salut \u00E0 toi!"); // U+00E0 is "Latin Small Letter a
> with Grave"
>
> wxMessageBox(wxString::FromUTF8("Salut \xC3\xA0 toi!"));
> // in UTF8 the character U+00E0 is encoded as 0xC3A0
>
> I cannot see any indication that a wxString passed to 
> wxTranslations::GetTranslatedString()
> is
> limited further than this.
>
> HTH
>
> Ruth
>
>
> The limitation is not in wxWidgets.
> It is in tools used to manage translations, that expect for input texts a
> ASCII7 string (poedit,
> gettext ...).
> Of course the output manage unicode strings.
>
> One can create strings with unicode chars, but there is no good way to do
> that:
> for instance
> use wxString::Format( _("Salut %c toi!"), 0x00E0)
>  (the string to translate is "Salut %c toi!")
> or
> wxString msg; msg << (_"Salut ") << wxChar(0x00E0) << _( " toi!");
>  (2 strings to translate _"Salut " and " toi!")
>
> the first is translatable, but not very readable in code
>
> the second is very bad because it is not really translatable, and not very
> readable in code.
> it is not really translatable because the order of words is fixed, and
> cannot be acceptable is other
> languages.
> Unfortunately it is sometimes used (even in Kicad code)
>
> --
> Jean-Pierre CHARRAS
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Don't reference CMAKE_INSTALL_PREFIX in installation paths

[Nick Østergaard]

Hi Simon,

without testing it, but just reading the documentation for gnuinstalldirs,
it seems that the CMAKE_INSTALL_ variables contains the relative path,
while the CMAKE_INSTALL_FULL_ should contain a full path, hence it
should work here as it will be share again.

Nick

2018-04-30 17:02 GMT+02:00 Simon Richter <simon.rich...@hogyros.de>:

> Hi Nick,
>
> On 30.04.2018 16:35, Nick Østergaard wrote:
>
> > @Simon, does MAKE_INSTALL_DATADIR work for gnu stow? If so, I guess it
> > is safer to use that variable, as we do elsewhere.
>
> The problem I'm addressing with my patch is configure time vs. install
> time path resolution -- if you explicitly use the variable there, you
> generate an absolute path at configure time, and it remains absolute
> during installation, while a relative path has a variable reference
> implicitly prepended to it which is resolved at install time.
>
> So using CMAKE_INSTALL_DATADIR wouldn't work, what is needed is some way
> to say "relative to whatever the variable is set to during installation".
>
> The traditional way to install with stow is to configure for a prefix of
> /usr/local, then override that as /usr/local/DIR/kicad for installation
> and symlink the files into the /usr/local tree -- that way, if you have
> compiled-in paths, they will use the /usr/local prefix, so the software
> will only be a tiny bit confused if it expects its data files not to be
> symlinks).
>
> This is very close to what we do with DESTDIR (which is what most
> distros use), but works without an extra renaming step.
>
>Simon
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Don't reference CMAKE_INSTALL_PREFIX in installation paths

[Nick Østergaard]

@Wayne, what do you mean by forging GNUInstallDirs? We already sue
GNUInstallDirs for some parts of our cmakelists, sepcifically for the
libdir thing. I am not sure if we do in other locations.

Using GNUInstallDir variables let the user / packager be able to override
some install paths instead of using the hardcoded values.

@Simon, does MAKE_INSTALL_DATADIR work for gnu stow? If so, I guess it is
safer to use that variable, as we do elsewhere.

2018-04-30 15:57 GMT+02:00 Simon Richter :

> Hi,
>
> On 30.04.2018 15:45, Wayne Stambaugh wrote:
>
> > I'm not sure GNUInstallDir wont break all other platform installs so I'm
> > a bit reluctant to use it this close to v5 release.  We certainly take a
> > look at it for v6.  Is there some way to force GNUInstallDirs at config
> > time on the cmake command line?
>
> Is the original patch okay (it's a no-op unless you override things
> during installation)?
>
>Simon
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Track & via clearances only in Legacy...

[Nick Østergaard]

I didn't test this, as I have been busy and just trying to keep up with the
bug and mails.

Den ons. 25. apr. 2018 11.02 skrev Jeff Young <j...@rokeby.ie>:

> @Orson & @Nick,
>
> Do you see the clearances /while/ routing?  The “always” setting does work
> on Mac, it’s just the 3 middle ones for “during routing” and “during
> routing and editing” that don’t on a Mac GAL canvas.
>
>
> On 25 Apr 2018, at 07:43, Nick Østergaard <oe.n...@gmail.com> wrote:
>
> Just a wild guess here; maybe it has something to do with a hidpi screen
> which I assume Jeff is using and the line thickness used for the drawing?
>
> 2018-04-25 8:32 GMT+02:00 Maciej Sumiński <maciej.sumin...@cern.ch>:
>
>> Hi Jeff,
>>
>> Are these options broken on macOS? I see clearance lines displayed for
>> all items (pads, tracks, vias) in GAL.
>>
>> example: https://imgur.com/a/LtFtWgR
>>
>> Cheers,
>> Orson
>>
>> On 04/24/2018 08:50 PM, Jeff Young wrote:
>> > I just discovered that “Show track clearances” and “Show track
>> clearances with via area” settings only work in the Legacy router.  We have
>> a Legacy Router Options area in the general preferences dialog where the
>> options could be moved to (they’re currently in Display Options).
>> >
>> > Personally, I’d let this sleeping dog lie for 5.0, but I thought I’d
>> bring it to peoples' attention.  (I’m happy to make the changes if people
>> think we should for 5.0.)
>> >
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Track & via clearances only in Legacy...

[Nick Østergaard]

Just a wild guess here; maybe it has something to do with a hidpi screen
which I assume Jeff is using and the line thickness used for the drawing?

2018-04-25 8:32 GMT+02:00 Maciej Sumiński :

> Hi Jeff,
>
> Are these options broken on macOS? I see clearance lines displayed for
> all items (pads, tracks, vias) in GAL.
>
> example: https://imgur.com/a/LtFtWgR
>
> Cheers,
> Orson
>
> On 04/24/2018 08:50 PM, Jeff Young wrote:
> > I just discovered that “Show track clearances” and “Show track
> clearances with via area” settings only work in the Legacy router.  We have
> a Legacy Router Options area in the general preferences dialog where the
> options could be moved to (they’re currently in Display Options).
> >
> > Personally, I’d let this sleeping dog lie for 5.0, but I thought I’d
> bring it to peoples' attention.  (I’m happy to make the changes if people
> think we should for 5.0.)
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] XDG_CONFIG_HOME on all platforms

[Nick Østergaard]

Den tir. 24. apr. 2018 00.23 skrev Eeli Kaikkonen :

>
>
> 2018-04-24 1:12 GMT+03:00 Seth Hillbrand :
>
>> I'm a bit late to this conversation so forgive the basic question.
>>
>> Won't this break things for users that explicitly set XDG_CONFIG_HOME for
>> other reasons?
>>
>>
> No, unless you set it so that it's used everywhere. On Linux (or *nix) you
> can set it for one program instance only, just type in the bash shell:
>
> XDG_CONFIG_HOME="/my/dir" kicad
>
> and kicad will be run once with this env variable. You can for example ($
> is the prompt):
>
> $ XDG_CONFIG_HOME="/my/dir" kicad &
> $ kicad
>
> and two instances with two different XDG_CONFIG_HOME values are started. I
> presume it works similarly on Windows. After some googling I found this:
> https://netlicensing.io/blog/2012/06/15/set-environment-variables-in-windows-shortcut/,
> which might be useful for more permanent and less hassle-free style to
> start a program with customized variable. I have to test it on Windows
> later.
>

How is this any different for what Ibsaid earlier?



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

Re: [Kicad-developers] XDG_CONFIG_HOME on all platforms

[Nick Østergaard]

Just open a terminal and "set" it as you you do on linux, where you would
"export" it.

Den man. 23. apr. 2018 23.27 skrev Eeli Kaikkonen :

>
>
> 2018-04-23 20:10 GMT+03:00 Wayne Stambaugh :
>
>> Attached is a patch that allows users to have multiple configuration
>> paths using the XDG_CONFIG_HOME environment variable on all platforms.
>>
>
>  This will be appreciated amongst the users.
>
> It seems to work on Ubuntu. I applied the patch, compiled and installed. I
> made a new dir, set the variable and started kicad with it. It opened as
> for the first time and populated the new dir with some conf files and dirs.
> Started again without the variable it opened with the old config.
>
> There's still one question: how to use it on Windows? I think many Windows
> users don't know how to use env variables, and I don't know how I would
> easily set one for only one application instance. It's useless if added
> globally, right? Can someone give instructions? I would give them to the
> forum readers, there have been much need for this.
>
> Eeli Kaikkonen
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Mac packaging update

[Nick Østergaard]

 It is built nightly as mentioned in earlier threads at
http://downloads.kicad-pcb.org/osx/testing/. It builds nightly, but it
seems the latest change broke the build for me. :/

So users are already able to test it. I have not applied the BU patch.

2018-04-23 20:23 GMT+02:00 Adam Wolf :

> Soon.  Today?  I'll see if I can set up the scripts to apply the attached
> patch.
>
> I rebuilt from a clean setup using all the old infrastructure, and I
> do not see any new issues, and the output DMGs appear to be the same.
> Let me know if there are any objections to this change.
>
> Adam
>
> On Mon, Apr 23, 2018 at 1:11 PM, Wayne Stambaugh 
> wrote:
> > Hi Adam,
> >
> > When do you think you will be able to begin providing nightly builds
> > with this so users can test it?  It would be nice to have a few weeks of
> > testing with Python bundled on macos to shake out any bugs before the
> > stable release.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 4/23/2018 10:46 AM, Adam Wolf wrote:
> >> Hi folks!
> >>
> >> Over the weekend, I made a culminating breakthrough on some Python
> >> work I've been working on since at least March 2017
> >> (https://cmake.org/pipermail/cmake/2017-March/065140.html).  I now
> >> have a Python Framework embedded inside KiCad, scripting console and
> >> all, which fixes many issues we've had for years.  For instance, I can
> >> no longer reproduce the longstanding "Mac KiCad stops working if you
> >> have wxmac or wxpython installed".  !!!
> >>
> >> My changes require *one* change inside KiCad, setting
> >> BU_COPY_FULL_FRAMEWORK_CONTENTS to ON (see
> >> https://cmake.org/cmake/help/v3.0/module/BundleUtilities.html) so that
> >> it copies the complied full custom Python Framework into the bundle.
> >>
> >> I am going to prepare a patch, and see if the last-generation
> >> packaging scripts still work.  I expect they should--I don't actually
> >> suspect any change for anyone else, because the Python framework is
> >> usually a system framework, and those are filtered out by
> >> BundleUtilities.  Doing a clean build from the old scripts to test it
> >> will take a good chunk of today.  (I am not 100% sure it won't cause
> >> problems for other folks, so I am prepared to set this behind a CMake
> >> flag so people can turn it off.)
> >>
> >> That'll take me a day, and I know we're running into a deadline, so I
> >> just wanted to pipeline any necessary discussion :)
> >>
> >> Adam Wolf
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] What's the different between Remap Symbols and Rescue Symbols?

[Nick Østergaard]

Your email body is empty...

I think the Rescue is about backing up symbols only found in the cache lib
while remapping is about using the new symbol table stuff, so it will
attempt to find the symbol in the configured libs instead of rescuing them
if possible.

2018-04-20 14:09 GMT+02:00 Jeff Young :

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

Re: [Kicad-developers] Odd board

[Nick Østergaard]

Is it not possible for you to obfuscate the board to illustrate the
problem? Just delete 99% of the stuff on it to just show a board edge and
the hole?

2018-04-16 22:35 GMT+02:00 Michael McCormack :

> This might not be quite the right place to post this, but, I've found
> something that is a slightly problematic with Kicad and board file.  I have
> a PCB that has a NPH hole located off the board, I can't see it or select
> it inside PCBNew, however, it gets a hole in the gerbers and I can find it
> in the kicad_pcb file if I open the file with a text editor.
>
> As it is my employer's board, I can't see them being OK with me creating a
> bug report and posting the board file for just anyone to see; but, as I
> have used Kicad myself probably a decade I'd send it to someone to evaluate
> if it would help the project.
>
> Is anyone interested?
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

[Nick Østergaard]

Den tor. 12. apr. 2018 17.18 skrev Reece R. Pollack :

> On 04/12/18 09:58, Carsten Schoenert wrote:
>
> Hi,
>
> Am 12.04.2018 um 15:47 schrieb Reece R. Pollack:
>
> I'm a relative newbie to KiCad, but I've been a software engineer since
> the early 1980. I'd prefer to see KiCad installed in a self-contained
> manner, meaning all installed files end up under one directory hierarchy
> rather than being spread all over the filesystem.
>
> well, KiCad isn't installing "some there" and "all over" the various
> systems. If you think so you have a impression that is different from
> the reality.
>
>
> The KiCad 4.0.7 Debian Linux package installs files in these directories:
>
> /etc/profile.d
> /usr/bin
> /usr/lib/kicad
> /usr/lib/python2.7/dist-packages
> /usr/share/applications
> /usr/share/doc
> /usr/share/icons
> /usr/share/kicad
> /usr/share/menu
> /usr/share/mime
> /usr/share/mimelnk
>
> That's "spread all over the file system" in contrast to my preference of
> having all installed files under one directory.
>

No, it is not, that i simply the unix/linux way or hatver the correct term
is. You can just set the cmake install prefix or destdir when installing to
/opt/kicad-foo and you get the same behaivour as with the xilinx tools. But
this is not the topic of this thread, we should focus on the user config
here.


> But as I said, putting everything under one directory hierarchy (for
> example, "/opt/kicad5") would be a significant change in behavior. A
> reasonable alternative is to install using file and directory names which
> include the major version number. Thus
>
> /usr/bin/kicad4
> /usr/bin/kicad5
>
> and
>
> /usr/lib/kicad4/plugins/
> /usr/lib/kicad5/plugins/
>
> I could even accept keeping the V4 file and directory names as they are
> and merely appending a 5 to the new files and directories.
>
> This is how Xilinx
> ISE, Eagle, and many other packages are installed, and it makes it very
> easy to keep multiple versions. This would be a major change in
> strategy, though.
>
> If all software projects would follow the common rules on the various
> platform it would be easier for all. But especially Windows based
> software follows often some "own" rules as it's simply possible.
>
>
> I know many Windows programs install in self-contained directory
> hierarchies now, as the previous behavior of overwriting DLLs in shared
> directories caused major headaches. I do not develop for Windows, though,
> so I'll leave that to those who are more familiar with that environment.
>
>
>
> Regardless, I agree that file names or paths should include the major
> version number. The executable file "kicad" should be renamed "kicad5"
> for V5. The directory under /usr/lib and /usr/share should be renamed
> from "kicad" to "kicad5". And so on. Under Linux (or at least the
> Debian-derived distros) the "update-alternatives" utility can be used to
> select which version is run using the "kicad", "pcbnew", and "eeschema"
> commands.
>
> updates-alternatives has a different approach as you think. It's not
> designated for this solution you think off.
> http://williamdemeo.github.io/linux/update-alternatives.html
>
>
> I'm well aware of the purpose of update-alternatives; I'm quite familiar
> with both its use and its implementation.
>
> Allow me to quote from the first paragraph of the link you provide:
>
> Here are some notes on update-alternatives and some examples
> demonstrating its use. The purpose of the update-alternatives utility
> program is to manage, on a single machine, serveral versions of programs
> that all provide the same functionality.
>
> That is exactly what we're doing here: managing several versions of
> programs that all provide the same functionality. Nothing in either the
> implementation nor the intent of update-alternatives requires that the
> different versions behave identically.
>
> A common case in the life of a developer is to have multiple versions of
> the Gnu C/C++ compiler installed. Perhaps new development is done with the
> GCC-5 compiler so it is the default on a system, but when producing an
> update for older systems the GCC-4.8 version is used. The
> update-alternatives allows the system manager to configure the system so
> the "cc" command invokes the latest-and-greatest, but the older versions
> are accessible by using the full file name.
>
> Here's the path the system follows to find the proper program to run for
> the "cc" command on my system:
>
> /usr/bin/cc -> /etc/alternatives/cc
> /etc/alternatives/cc -> /usr/bin/gcc
> /usr/bin/gcc -> gcc-5
> /usr/bin/gcc-5
>
> Using update-alternatives properly would require renaming the V4 files to
> include the major version number, as well as naming the V5 file properly.
> Perhaps there could be a 4.0.8 release that does this for coexistence.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : 

Re: [Kicad-developers] wxPython-gtk3 woes

[Nick Østergaard]

So many distros have wxwidgets with gtk2 and gtk3, but now most upgrade
wxpython to gtk3.

2018-04-10 15:36 GMT+02:00 Nick Østergaard <oe.n...@gmail.com>:

> This is because of the wxversion.py. It will then be provided by multiple
> packages and I don't think it distinguishes different toolkit versions,
> only multiple wxpython versions.
>
> https://wiki.wxpython.org/MultiVersionInstalls
>
>
> 2018-04-10 14:56 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com>:
>
>> I wonder why they couldn't make a gtk2 version of wxPython.  It seems
>> plausible since they created a gtk2 version of wxWidgets.  Looks like
>> the work load just got increased during v6 development.  Maybe we should
>> attack that first and backport the gtk3 fixes to v5 so distros wont have
>> to support gtk2 builds of wx.
>>
>> On 4/10/2018 8:48 AM, Maciej Suminski wrote:
>> > In the bug reported for Ubuntu bionic (lp:#1762432) there are three
>> > packages installed:
>> >
>> > - libwxgtk3.0-0v5:amd64   (wxWidgets/GTK2)
>> > - libwxgtk3.0-gtk3-0v5 (wxWidgets/GTK3)
>> > - python-wxgtk3.0 (wxPython/GTK3)
>> >
>> > My guess is that some applications may depend on wxWidgets/GTK2, and
>> > wxWidgets/GTK3 is simply installed as a dependency of wxPython/GTK3.
>> >
>> > On 04/10/2018 02:36 PM, Wayne Stambaugh wrote:
>> >> For our v5 release, I guess we are going to have to disable wxPython on
>> >> the platforms who insist on building wxPython with gtk3.  We can start
>> >> looking at the transition to gtk3 and wxPhoenix during v6 development.
>> >>
>> >> Are distros actually shipping with wxWidgets built with gtk2 and
>> >> wxPython built with gtk3?  This seems to be the case if I'm reading
>> this
>> >> correctly.  If they are, the question is why?
>> >>
>> >> On 4/10/2018 7:35 AM, Maciej Sumiński wrote:
>> >>> It seems the easy solution to me too. I just wonder how many people
>> rely
>> >>> on the Python shell or GUIs done with wxPython.
>> >>>
>> >>> On 04/10/2018 01:32 PM, Jeff Young wrote:
>> >>>> I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t
>> say I’ve missed it.
>> >>>>
>> >>>>> On 10 Apr 2018, at 12:26, Maciej Sumiński <maciej.sumin...@cern.ch>
>> wrote:
>> >>>>>
>> >>>>> Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only
>> an
>> >>>>> Arch issue anymore, as the upcoming Ubuntu release (bionic) also
>> >>>>> provides wxPython package built against gtk3 [package: 2, bug
>> report: 3].
>> >>>>>
>> >>>>> There are two things we can do to fix the problem for v5:
>> >>>>> - Backport python-wxgtk3.0 package built against gtk2. This way
>> >>>>> everything works as it used to be, but only for the nightlies. For
>> the
>> >>>>> official release the users would be forced to add a PPA providing
>> the
>> >>>>> backported package and it sounds troublesome.
>> >>>>>
>> >>>>> - Disable KICAD_SCRIPTING_WXPYTHON, as there is still available
>> >>>>> libwxgtk3.0 package [4] build against gtk2. The drawbacks are that
>> the
>> >>>>> Python shell in pcbnew and scripts taking advantage of wxPython to
>> >>>>> display a GUI will not work anymore.
>> >>>>>
>> >>>>> In other news: Ubuntu bionic also ships wxPhoenix [5].
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Orson
>> >>>>>
>> >>>>> 1. https://bugs.launchpad.net/kicad/+bug/1747677
>> >>>>> 2. https://packages.ubuntu.com/bionic/python-wxgtk3.0
>> >>>>> 3. https://bugs.launchpad.net/kicad/+bug/1762432
>> >>>>> 4. https://packages.ubuntu.com/bionic/libwxgtk3.0-0v5
>> >>>>> 5. https://packages.ubuntu.com/bionic/python3-wxgtk4.0
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> ___
>> >>>>> Mailing list: https://launchpad.net/~kicad-developers
>> >>>>> Post to : kicad-developers@lists.launchpad.net
>> >>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>> >>>>> More help   : h

Re: [Kicad-developers] wxPython-gtk3 woes

[Nick Østergaard]

This is because of the wxversion.py. It will then be provided by multiple
packages and I don't think it distinguishes different toolkit versions,
only multiple wxpython versions.

https://wiki.wxpython.org/MultiVersionInstalls


2018-04-10 14:56 GMT+02:00 Wayne Stambaugh :

> I wonder why they couldn't make a gtk2 version of wxPython.  It seems
> plausible since they created a gtk2 version of wxWidgets.  Looks like
> the work load just got increased during v6 development.  Maybe we should
> attack that first and backport the gtk3 fixes to v5 so distros wont have
> to support gtk2 builds of wx.
>
> On 4/10/2018 8:48 AM, Maciej Suminski wrote:
> > In the bug reported for Ubuntu bionic (lp:#1762432) there are three
> > packages installed:
> >
> > - libwxgtk3.0-0v5:amd64   (wxWidgets/GTK2)
> > - libwxgtk3.0-gtk3-0v5 (wxWidgets/GTK3)
> > - python-wxgtk3.0 (wxPython/GTK3)
> >
> > My guess is that some applications may depend on wxWidgets/GTK2, and
> > wxWidgets/GTK3 is simply installed as a dependency of wxPython/GTK3.
> >
> > On 04/10/2018 02:36 PM, Wayne Stambaugh wrote:
> >> For our v5 release, I guess we are going to have to disable wxPython on
> >> the platforms who insist on building wxPython with gtk3.  We can start
> >> looking at the transition to gtk3 and wxPhoenix during v6 development.
> >>
> >> Are distros actually shipping with wxWidgets built with gtk2 and
> >> wxPython built with gtk3?  This seems to be the case if I'm reading this
> >> correctly.  If they are, the question is why?
> >>
> >> On 4/10/2018 7:35 AM, Maciej Sumiński wrote:
> >>> It seems the easy solution to me too. I just wonder how many people
> rely
> >>> on the Python shell or GUIs done with wxPython.
> >>>
> >>> On 04/10/2018 01:32 PM, Jeff Young wrote:
>  I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t
> say I’ve missed it.
> 
> > On 10 Apr 2018, at 12:26, Maciej Sumiński 
> wrote:
> >
> > Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an
> > Arch issue anymore, as the upcoming Ubuntu release (bionic) also
> > provides wxPython package built against gtk3 [package: 2, bug
> report: 3].
> >
> > There are two things we can do to fix the problem for v5:
> > - Backport python-wxgtk3.0 package built against gtk2. This way
> > everything works as it used to be, but only for the nightlies. For
> the
> > official release the users would be forced to add a PPA providing the
> > backported package and it sounds troublesome.
> >
> > - Disable KICAD_SCRIPTING_WXPYTHON, as there is still available
> > libwxgtk3.0 package [4] build against gtk2. The drawbacks are that
> the
> > Python shell in pcbnew and scripts taking advantage of wxPython to
> > display a GUI will not work anymore.
> >
> > In other news: Ubuntu bionic also ships wxPhoenix [5].
> >
> > Cheers,
> > Orson
> >
> > 1. https://bugs.launchpad.net/kicad/+bug/1747677
> > 2. https://packages.ubuntu.com/bionic/python-wxgtk3.0
> > 3. https://bugs.launchpad.net/kicad/+bug/1762432
> > 4. https://packages.ubuntu.com/bionic/libwxgtk3.0-0v5
> > 5. https://packages.ubuntu.com/bionic/python3-wxgtk4.0
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> 
> 
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : 

Re: [Kicad-developers] wxPython-gtk3 woes

[Nick Østergaard]

FYI, it has been a problem on fedora for years. So it was not an issue on
arch first.

I guess there are multiple approaches to address this issue.
1. Platforms can disable the wxpython scripting option which will get rid
of the footprint wizards and the python console.
2. Hack wxpython with gtk2 to be  co-installable with a wxpython with gtk3
on major platforms that have upgrade to gtk3 as default. The issue here
being wxversion.py.
3. Move to wxpython phoenix which should be able to be co-installed with
different build configurations. This is a big task because of the move from
SWIG to SIP and no one really got it working right yet, as far as I
understand.

Nick

2018-04-10 13:35 GMT+02:00 Maciej Sumiński :

> It seems the easy solution to me too. I just wonder how many people rely
> on the Python shell or GUIs done with wxPython.
>
> On 04/10/2018 01:32 PM, Jeff Young wrote:
> > I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t say
> I’ve missed it.
> >
> >> On 10 Apr 2018, at 12:26, Maciej Sumiński 
> wrote:
> >>
> >> Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an
> >> Arch issue anymore, as the upcoming Ubuntu release (bionic) also
> >> provides wxPython package built against gtk3 [package: 2, bug report:
> 3].
> >>
> >> There are two things we can do to fix the problem for v5:
> >> - Backport python-wxgtk3.0 package built against gtk2. This way
> >> everything works as it used to be, but only for the nightlies. For the
> >> official release the users would be forced to add a PPA providing the
> >> backported package and it sounds troublesome.
> >>
> >> - Disable KICAD_SCRIPTING_WXPYTHON, as there is still available
> >> libwxgtk3.0 package [4] build against gtk2. The drawbacks are that the
> >> Python shell in pcbnew and scripts taking advantage of wxPython to
> >> display a GUI will not work anymore.
> >>
> >> In other news: Ubuntu bionic also ships wxPhoenix [5].
> >>
> >> Cheers,
> >> Orson
> >>
> >> 1. https://bugs.launchpad.net/kicad/+bug/1747677
> >> 2. https://packages.ubuntu.com/bionic/python-wxgtk3.0
> >> 3. https://bugs.launchpad.net/kicad/+bug/1762432
> >> 4. https://packages.ubuntu.com/bionic/libwxgtk3.0-0v5
> >> 5. https://packages.ubuntu.com/bionic/python3-wxgtk4.0
> >>
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

[Nick Østergaard]

This is a complicated topic. But I guess we can clutter the config dir as
much as we want with version folders. Usually the user should not have the
need to look here. I guess you are correct, that most of the "non-issue" is
because the fp-lib-table was only introduced in v4 and has not had a new
syntax introduced that is not read by a previous stable.

2018-04-05 18:25 GMT+02:00 Seth Hillbrand :

> If we are going to support multiple versions, on the developer side, we
> should add a preference versioning to the user configuration directory.
> Otherwise, fp-lib-table will being either pointing to v4 or v5 footprints.
> Likewise, there are a few preferences that only exist in v5 and will be
> lost when v4 saves the preference file.
>
> To avoid cluttering the config directory, we could place the v5
> configurations in a v5 sub directory.  Configurations would be
> preferentially loaded from the v5 directory with a fall-back to the v4
> items if v5 items were not found.  Configurations would only be saved to
> the v5 subdir.
>
> If we want to support this, we should insert this code before rc2.
> Thoughts?
>
> -S
>
> 2018-04-04 22:24 GMT-07:00 Strontium :
>
>> On 04/04/18 18:52, Jean-Samuel Reynaud wrote:
>>
>>> So my questions are:
>>> - Is it usefull ?
>>>
>>
>> Having both versions be able to be installed side by side is immensely
>> valuable for an end user, and the development of kicad, in my opinion.
>>
>> The users can "USE" the stable version for their work.  They can also
>> test the Nightly and not worry about it messing with their work.  It should
>> mean that general users have a better chance to test the new version as it
>> evolves, and they will feel more involved, even if that involvement is only
>> posting bugs.  They don't have to choose between being on the bleeding
>> edge, and being productive.
>>
>> It would be equally useful (maybe even more useful) to have kicad V4 and
>> V5 installed simultaneously as well.
>>
>> Steven
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

[Nick Østergaard]

You can just set a different XDG_CONFIG_HOME. I think this should be left
for the user to define. Usually I have seen no significant problems running
with the same config dir. This may of course not aleays be true.

Alternatively the nightly package can provide a wrapper script that sets
this to something else. Then the user can use this, or make their own, or
not use it at all depending on what the user is testing.

Den ons. 4. apr. 2018 14.27 skrev Eeli Kaikkonen :

> I can confirm that many users would appreciate the possibility to run
> several precompiled versions. It has come up in the user forums. Using a
> virtual machine for that purpose has been suggested as a solution, but it's
> not very convenient.
>
> One possible problem is the configuration compatibility. It might be a
> good idea to have a command line switch to use a different configuration
> files/directories so that the installations could be completely
> independent. Also the env variables may be a problem. Maybe they could be
> overriden with command line switches, too?
>
> Eeli Kaikkonen
>
>
> 2018-04-04 13:52 GMT+03:00 Jean-Samuel Reynaud :
>
>> Dear All,
>>
>>
>> Since I provide PPA (daily build for Ubuntu) for KiCad, I receive some
>> requests about installing daily build packages in parallel with stable
>> version.
>> With next version (V5) I think it can be useful...
>> FreeCad provide this kind of feature and you are able to run both
>> version in parallel.
>>
>> For testing that I had created a dedicated PPA:
>> ppa:js-reynaud/kicad-dev-daily
>> (to add with sudo add-apt-repository ppa:js-reynaud/kicad-dev-daily)
>>
>> Once added, you are able to install a new package "kicad-daily" that
>> won't conflict with existing "kicad" packages.
>> All files are installed on a separate folder and commands became
>> "something-daily". For example kicad-daily or pcbnew-daily...
>>
>> So my questions are:
>> - Is it usefull ?
>> - Is it a bad idea/stupid :( ?
>> - If you test it, are you able to find some limitations/bugs ?
>> - Perhaps to have is plainly functional some modifications are needed.
>> What modifications ?
>>
>>
>> For the moment, you can't run in same time two versions (or there are
>> some error messages...) anyway both are installed and easily "runnable"...
>>
>>
>> Please give your comments, feedbacks...
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

[Nick Østergaard]

2018-04-04 12:52 GMT+02:00 Jean-Samuel Reynaud :

> Dear All,
>
>
> Since I provide PPA (daily build for Ubuntu) for KiCad, I receive some
> requests about installing daily build packages in parallel with stable
> version.
> With next version (V5) I think it can be useful...
> FreeCad provide this kind of feature and you are able to run both
> version in parallel.
>
> For testing that I had created a dedicated PPA:
> ppa:js-reynaud/kicad-dev-daily
> (to add with sudo add-apt-repository ppa:js-reynaud/kicad-dev-daily)
>
> Once added, you are able to install a new package "kicad-daily" that
> won't conflict with existing "kicad" packages.
> All files are installed on a separate folder and commands became
> "something-daily". For example kicad-daily or pcbnew-daily...
>
> So my questions are:
> - Is it usefull ?
>

Yes.


> - Is it a bad idea/stupid :( ?
>

No, but I may personally prefer the term nightly over daily to be
consistent with the terminology we have been using for quite some time.


> - If you test it, are you able to find some limitations/bugs ?
>

I am not sure how you implemented this. I assume you have scripting enabled
in both builds. You need to make sure that you are using the correct pcbnew
python module that matches the version of kicad that you like to run such
that it won't explode.


> - Perhaps to have is plainly functional some modifications are needed.
> What modifications ?
>
>
> For the moment, you can't run in same time two versions (or there are
> some error messages...) anyway both are installed and easily "runnable"...
>
>
What error message? The generic, you are already running another instance
of kicad or whatever it says? I think that can be ignored safely.


>
> Please give your comments, feedbacks...
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Resistor 2512 footprint [Kicad 4.07]

[Nick Østergaard]

The kicad-developers list is not really for detailed library discussions
like this. You may have better luck reporting the issue directly on
https://github.com/kicad/kicad-footprints/issues

I am not sure what the plan is, but I don't think the Librarians will
update the old footprints, all activity are done in the new repos.

http://kicad-pcb.org/post/kicad-official-libraries/

2018-04-03 23:33 GMT+02:00 Augusto Fraga Giachero :

>
> Hi!
>
> I've had a an unpleasant surprise with a 2512 (imperial) smd resistor
> footprint (Resistors_SMD:R_2512_HandSoldering) available in the Kicad's
> official library (shame on me for not checking the dimensions before
> sending the gerbers). When our boards arrived we verified that the pads
> of this footprint are too further apart, up to the point that the
> resistor barely touches the pads.
>
> I've looked on some datasheets and other sources and confirmed that this
> footprint is out of the recommended dimensions
> (http://www.resistorguide.com/resistor-sizes-and-packages/).
>
> I've attached an image showing the dimensions from the website
> above. The recommended dimensions for 2512 are a = 3.5mm, b = 1.6mm and
> c = 3.8mm, while in the footprint available on Kicad a = 3.2mm, b =
> 2.7mm (no problems with this been wider as it is a hand soldering
> variant) and c = 5.2mm.
>
> Dim(mm) Average Kicad
> a   3.5 3.2
> b   1.6 2.7 (ok, hand soldering)
> c   3.8 5.2 (too further apart)
>
> I don't known if it is fixed in the new Kicad 5 libraries, but it would
> be nice to be fixed in the legacy libraries as well. I can make the fix
> if nobody have already made.
>
> Thanks,
> Augusto Fraga Giachero.
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Nick Østergaard]

2018-04-03 13:12 GMT+02:00 jp charras :

> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
> > Things have quieted down quit a bit so we should be close to an rc2
> > release.  I saw a 3D viewer crash report but it looks like it might be a
> > video driver issue.  Are there any other outstanding issues we need to
> > fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
> > freeze so no UI string changes other than spelling errors after rc2.  If
> > you have any UI string changes, now is the time.  Thanks again everyone
> > for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
> > lot of critical bugs and we can roll out v5 by the end of April.
> >
> > Cheers,
> >
> > Wayne
>
> I know 2 non critical bugs, but annoying bugs, in Pcbnew:
> 1 - In GAL mode, when selecting a zone outline (for instance to edit this
> zone parameters), and
> deselecting it, it is always refilled, even if no change is made.
> 2 - The Footprint Wizard Library allows downloading and using libraries on
> Github.
> It works only for V4 libraries.
> Is is no longer compatible with the V5 footprint libraries on Github.
> It can create serious mistakes for users.
> (Perhaps the easy way is just to disable the Github library management)
>
>
> I think we should not disable the github plugin, but we may need to remove
it from the wizard in a way that does not emphasize that this is the way to
go. Maybe it is ok to remove it completely from the wizard, but just let
the plugin in the fp-lib-table still work.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Alternative presentation of Symbol properties

[Nick Østergaard]

Are you not missing a lot of properties from that dialog with your
screenshot, like the orientation? Or is this only to replace the "Fields"
frame of the dialog?

2018-03-01 17:26 GMT+01:00 Jeff Young :

> Technically yes, but even the existing dialog only lets you edit both.
>
> > On 1 Mar 2018, at 16:23, Andy Peters  wrote:
> >
> >
> >
> >> On Mar 1, 2018, at 5:29 AM, Jeff Young  wrote:
> >>
> >> What do you guys think of this for displaying / editing symbol fields:
> >>
> >> 
> >
> > Don’t the text items have thickness and width attributes, not just one
> “size?”
> >
> > -a
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] What is the purpose of multiple 3D models?

[Nick Østergaard]

Den lør. 31. mar. 2018 00.02 skrev Jeff Young :

> A footprint can have several 3D models associated with it (confusingly
> named 3D Shape Names in the dialog, but never mind that).
>
> What is the purpose of this?
>
> Is it so that library devs can add different formats and the renderer will
> choose the first it has a plugin for?
>

No

If so, we need to say that in the UI.  Right now if you add two models,
> selecting between them has no effect.  (That makes sense if the above is
> true and you as a user have figured that out, but is confusing as all heck
> otherwise.)
>
> But that also means you might want to order them (so that a preferred one
> will be selected over a fall-back if both plugins are available), no?
>
> Or is it for some other reason entirely?
>

Sometimes you would like to add myltiple models to a footprint.

There is a subtle but important feature. It will render a wrl model over a
step file, because users with wrl models use them for more control over
surface properties, but will still be able to export a step assembly if the
model exists with the same name as the wrl, but just with the stp
extension. See Maurices freecad script tool.

On that, I don't really think we need to do much in the GUI other that what
is done now.

One feature that is a bit wonky is the preview when browsing for a model.
It is not a standard opem file dialog because it was not possible to add
the preview pane in wx on all platforms to the native file selector. It was
decided to have the one we have now for cross platform consistency.


> Thanks,
> Jeff.
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Oversight in pcbnew footprint properties dialog

[Nick Østergaard]

If you think this is important, it is better to report a bug on the bug
tracker to make sure this is not lost in the noise.

2018-02-28 7:38 GMT+01:00 Russell Oliver :

> Hmm what about displaying that info in the dialog title?
>
> Also might be useful to show if the footprint can be found on disk (as
> opposed from cache) and if so the path to its file.
>
>
> On 28 Feb 2018 17:33, "Andy Peters"  wrote:
>
> Nowhere in the pcbnew footprint properties dialog does it say the name
> (and source library) of the footprint whose properties are being displayed!
> This is a weird oversight.
>
> This little bit of info is useful! For example, my DRC check complained
> about “footprint C7 has malformed courtyard.” OK, I look at the footprint’s
> properties to see what it’s called (because who can remember) and it’s not
> in that dialog.
>
> To be fair, when a footprint is selected, its relevant details are shown
> in the status bar on the bottom of the screen, and that includes the
> footprint name. But still …
>
> This is with a current nightly build.
>
> -a
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0 RC2 release

[Nick Østergaard]

Yes.

The macos packing is https://github.com/wayneandlayne/kicad-mac-builder


2018-03-26 17:33 GMT+02:00 Jon Evans <j...@craftyjon.com>:

> Could the people working on the MacOS and Windows packaging stuff use more
> help?
> I can help with testing for sure, and could also take on some tasks if
> there is a list of things to do.
>
> -Jon
>
> On Mon, Mar 26, 2018 at 4:55 AM, Nick Østergaard <oe.n...@gmail.com>
> wrote:
>
>> I mainly didn't push for announce rc1 because the new macos packaging
>> scripts are not done, and there are some refactoring needed in the windows
>> installer which has not been completed yet.
>>
>> 2018-03-25 18:32 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com>:
>>
>>> On 03/25/2018 11:16 AM, Jon Evans wrote:
>>>
>>>> It seems like we are pretty close.
>>>>
>>>> Which of these are critical to get done for RC2 / which could be
>>>> delayed?
>>>> https://launchpad.net/kicad/+milestone/5.0.0-rc2
>>>>
>>>
>>> I think we are pretty close to rc2.  I have a few action items which I
>>> should be able to knock out this week.  We should shoot for next weekend
>>> unless something unexpected comes up.
>>>
>>>
>>>> Are there things that need to be done that aren't on the milestone yet?
>>>>
>>>
>>> I'm not aware of anything.  If anyone else has anything to do, please
>>> tag it for rc2.  rc2 will be a string freeze release so our translators
>>> have time be v5 stable is released so please make any ui string changes
>>> before then.
>>>
>>>
>>>> Should we publicize this release a bit more than RC1 when it is ready?
>>>>
>>>
>>> If by publicize you mean add to the kicad website blog, then yes we
>>> should do that.  I meant to make an rc1 announcement but I just dropped the
>>> ball on that one.
>>>
>>> Wayne
>>>
>>>
>>>
>>>> -Jon
>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>> Post to : kicad-developers@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.0 RC2 release

[Nick Østergaard]

I mainly didn't push for announce rc1 because the new macos packaging
scripts are not done, and there are some refactoring needed in the windows
installer which has not been completed yet.

2018-03-25 18:32 GMT+02:00 Wayne Stambaugh :

> On 03/25/2018 11:16 AM, Jon Evans wrote:
>
>> It seems like we are pretty close.
>>
>> Which of these are critical to get done for RC2 / which could be delayed?
>> https://launchpad.net/kicad/+milestone/5.0.0-rc2
>>
>
> I think we are pretty close to rc2.  I have a few action items which I
> should be able to knock out this week.  We should shoot for next weekend
> unless something unexpected comes up.
>
>
>> Are there things that need to be done that aren't on the milestone yet?
>>
>
> I'm not aware of anything.  If anyone else has anything to do, please tag
> it for rc2.  rc2 will be a string freeze release so our translators have
> time be v5 stable is released so please make any ui string changes before
> then.
>
>
>> Should we publicize this release a bit more than RC1 when it is ready?
>>
>
> If by publicize you mean add to the kicad website blog, then yes we should
> do that.  I meant to make an rc1 announcement but I just dropped the ball
> on that one.
>
> Wayne
>
>
>
>> -Jon
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Build failure

[Nick Østergaard]

Do you have Seth's opencascade patch in your tree? Or what is different
from the usual? The build flag you are specifying shoulnd be correct IIRC.

2018-03-22 23:56 GMT+01:00 Jeff Young :

> What does this mean:
>
> By not providing "FindOCE.cmake" in CMAKE_MODULE_PATH this project has
> asked CMake to find a package configuration file provided by "OCE", but
> CMake did not find one.
>
> Could not find a package configuration file provided by "OCE" (requested
> version 0.16) with any of the following names:
>
> OCEConfig.cmake
> oce-config.cmake
>
> Add the installation prefix of "OCE" to CMAKE_PREFIX_PATH or set "OCE_DIR"
> to a directory containing one of the above files. If "OCE" provides a
> separate development package or SDK, be sure it has been installed.
>
>
> I thought I had avoided this stuff by specifying:
>
> -DKICAD_USE_OCE=OFF \
>
> but it seems to be back.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] small contrib to the website

[Nick Østergaard]

Changes to the website are preferably made as pull requests on
https://github.com/KiCad/kicad-website

It makes it easier to handle when I am not at my dev host.

2018-03-21 13:45 GMT+01:00 Marco Ciampa :

> Hello devs!
> here is a small contrib to the website...
>
> Is it ok to send it as a patch or do you prefer a pull request on
> git-hub?
>
> TIA
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> 
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> 
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

[Nick Østergaard]

Hi Seth,

I tried to test your patch. It bascially works. Some observations follows:

I think the message printed from cmake
"from /opt/oce/lib/libTKernel.so I found /opt/oce/lib"
should be removed from the output, it looks liek a debug message to me. I
guess the same information is available in the CMakeCache.txt if needed
later on.

It defaults to OCE as expected, builds, and runs.

If I remove OCE it will find my normal opencascade installation, builds and
runs.

I think it also did use OCC if I set KICAD_USE_OCC=ON, where it built and
ran fine. But when this happens I still see KICAD_USE_OCE=ON in the cache.
This might be ok, but could be confusing.

I canẗ make it use an alterntive install location of OCC, I tried to set
OCC_INCLUDE_DIR=/opt/opencascade7/inc. This fails. What variable do I need
to set to select another version of opencascade?

I tested this on archlinux. I think it could be improved to be less
errorprone, but could possibly be comitted as is if that debug log is
removed. It seems to work fine if you are not switching between OCE and OCC
in the same build dir, that is, a clean config.

Nick

2018-03-17 0:51 GMT+01:00 Nick Østergaard <oe.n...@gmail.com>:

> Thank you very much, I will try to remember it after the weekend.
>
> 2018-03-17 <20%2018%2003%2017> 0:46 GMT+01:00 Seth Hillbrand <
> seth.hillbr...@gmail.com>:
>
>> Hi Nick-
>>
>> I finally found a moment to figure out Docker and get this up and running
>> in your build configuration.
>>
>> Please take a look when you have a chance and let me know if you have any
>> issues with this patch.
>>
>> Best-
>> Seth
>>
>> 2018-02-10 <20%2018%2002%2010> 7:12 GMT-08:00 Seth Hillbrand <
>> seth.hillbr...@gmail.com>:
>>
>>> Nick was having an unknown issue but I haven't heard back from him on
>>> whether the issue was resolved by doing a clean cmake.  If it isn't then
>>> I'll need to address that.
>>>
>>> Nick did you have a chance to test that?
>>>
>>> -S
>>>
>>> 2018-02-10 <20%2018%2002%2010> 6:18 GMT-08:00 Wayne Stambaugh <
>>> stambau...@gmail.com>:
>>>
>>>> Seth,
>>>>
>>>> What is the current status of this patch?  I would like to get it merged
>>>> before rc1 so the package devs can test it.
>>>>
>>>> Cheers,
>>>>
>>>> Wayne
>>>>
>>>> On 01/30/2018 02:12 PM, Seth Hillbrand wrote:
>>>> > Nick-
>>>> >
>>>> > Thanks for the test.  I'm attaching revised patch that allows multiple
>>>> > OpenCASCADE installations on a single machine.
>>>> >
>>>> > I've tested with a few different OpenCASCADE versions down to 6.8 with
>>>> > no issues installed alongside OCE 0.17.  You can choose which you want
>>>> > to link by using either "-DKICAD_USE_OCE" or "-DKICAD_USE_OCC".  If
>>>> both
>>>> > are specified, "-DKICAD_USE_OCC" will override.
>>>> >
>>>> > I corrected the cmake message display to be less doubled and correctly
>>>> > show the library location.
>>>> >
>>>> > I've also added the OCC version and type to the about window version
>>>> info.
>>>> >
>>>> > The "Based on" line was taken from
>>>> > (https://github.com/FreeCAD/FreeCAD/blob/master/src/FCConfig.h) when
>>>> > trying to determine how FreeCAD likes to refer to themselves.  The
>>>> > actual FindOpenCascade.cmake file did not have a copyright header
>>>> > attached but falls under the license from
>>>> > (https://github.com/FreeCAD/FreeCAD/blob/master/COPYING).  I note
>>>> that I
>>>> > had it written as "FreeCAD CADx development system".  I've corrected
>>>> > this to read "FreeCAD CAx development system".
>>>> >
>>>> > I'm not sure to what the "CheckSymbolExists" line is referring.  I
>>>> don't
>>>> > see it on my machine.
>>>> >
>>>> > -Seth
>>>> >
>>>> > 2018-01-29 14:30 GMT-08:00 Nick Østergaard <oe.n...@gmail.com
>>>> > <mailto:oe.n...@gmail.com>>:
>>>> >
>>>> > Hi Seth,
>>>> >
>>>> > I just took the patch for a testrun and will state some comments
>>>> below.
>>>> >
>>>> > This looks a bit strange:
>>

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

[Nick Østergaard]

Thank you very much, I will try to remember it after the weekend.

2018-03-17 0:46 GMT+01:00 Seth Hillbrand <seth.hillbr...@gmail.com>:

> Hi Nick-
>
> I finally found a moment to figure out Docker and get this up and running
> in your build configuration.
>
> Please take a look when you have a chance and let me know if you have any
> issues with this patch.
>
> Best-
> Seth
>
> 2018-02-10 <20%2018%2002%2010> 7:12 GMT-08:00 Seth Hillbrand <
> seth.hillbr...@gmail.com>:
>
>> Nick was having an unknown issue but I haven't heard back from him on
>> whether the issue was resolved by doing a clean cmake.  If it isn't then
>> I'll need to address that.
>>
>> Nick did you have a chance to test that?
>>
>> -S
>>
>> 2018-02-10 <20%2018%2002%2010> 6:18 GMT-08:00 Wayne Stambaugh <
>> stambau...@gmail.com>:
>>
>>> Seth,
>>>
>>> What is the current status of this patch?  I would like to get it merged
>>> before rc1 so the package devs can test it.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 01/30/2018 02:12 PM, Seth Hillbrand wrote:
>>> > Nick-
>>> >
>>> > Thanks for the test.  I'm attaching revised patch that allows multiple
>>> > OpenCASCADE installations on a single machine.
>>> >
>>> > I've tested with a few different OpenCASCADE versions down to 6.8 with
>>> > no issues installed alongside OCE 0.17.  You can choose which you want
>>> > to link by using either "-DKICAD_USE_OCE" or "-DKICAD_USE_OCC".  If
>>> both
>>> > are specified, "-DKICAD_USE_OCC" will override.
>>> >
>>> > I corrected the cmake message display to be less doubled and correctly
>>> > show the library location.
>>> >
>>> > I've also added the OCC version and type to the about window version
>>> info.
>>> >
>>> > The "Based on" line was taken from
>>> > (https://github.com/FreeCAD/FreeCAD/blob/master/src/FCConfig.h) when
>>> > trying to determine how FreeCAD likes to refer to themselves.  The
>>> > actual FindOpenCascade.cmake file did not have a copyright header
>>> > attached but falls under the license from
>>> > (https://github.com/FreeCAD/FreeCAD/blob/master/COPYING).  I note
>>> that I
>>> > had it written as "FreeCAD CADx development system".  I've corrected
>>> > this to read "FreeCAD CAx development system".
>>> >
>>> > I'm not sure to what the "CheckSymbolExists" line is referring.  I
>>> don't
>>> > see it on my machine.
>>> >
>>> > -Seth
>>> >
>>> > 2018-01-29 14:30 GMT-08:00 Nick Østergaard <oe.n...@gmail.com
>>> > <mailto:oe.n...@gmail.com>>:
>>> >
>>> > Hi Seth,
>>> >
>>> > I just took the patch for a testrun and will state some comments
>>> below.
>>> >
>>> > This looks a bit strange:
>>> >
>>> > -- Boost version: 1.66.0
>>> > -- -- OpenCASCADE Community Edition has been found.
>>> > -- -- Found OCE/OpenCASCADE version: 6.8.0
>>> > -- -- OCE/OpenCASCADE include directory:
>>> > /opt/oce/lib/oce-0.17/../../include/oce
>>> > -- -- OCE/OpenCASCADE shared libraries directory:
>>> > -- Check for installed Python Interpreter -- found
>>> >
>>> > The messages are with double -- and the shared libs.
>>> >
>>> > But an improvement with your patch over what is currently in kicad
>>> > is that it found OCE on my system without explicitly specifind
>>> > OCE_DIR. But how do I make it use OCCT when I also have OCE
>>> installed?
>>> >
>>> > What does CADx mean in that header?
>>> >
>>> > What is this about?
>>> > -- Looking for
>>> > /home/amazingdude/kicad-source-mirror/build_seths_occt_patc
>>> h_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
>>> > -- Looking for
>>> > /home/amazingdude/kicad-source-mirror/build_seths_occt_patc
>>> h_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
>>> > - not found
>>> >
>>> > I tried to test it with removing oce and just have occt installed
>>> > and got something like this:
>>> > -- F

Re: [Kicad-developers] [PATCH 0/8] fixing various small spelling issues

[Nick Østergaard]

For reference, this patch series have been merged.

2018-02-25 13:17 GMT+01:00 :

> From: Carsten Schoenert 
>
> While working on the packaging of KiCad 5 for Debian the lintian QS tool
> found some spelling error which I fixed mostly by this series.
> The patches are made against the tag 5.0.0-rc1.
>
> I made small but a lot of patches which fixing only one specific
> spelling issue. If you agree on the fixes feel free to merge all commits
> into one before applying.
>
> If you disagree with some fixes just drop the patch.
>
> Regards
> Carsten
>
> Carsten Schoenert (8):
>   fix misspelled 'accesing' -> 'accessing'
>   fix misspelled 'Appearence' -> 'Appearance'
>   fix misspelled 'Modifed' -> 'Modified'
>   fix misspelled 'neeeded' -> 'needed'
>   fix misspelled 'Occassionally' -> 'Occasionally'
>   fix misspelled 'occured' -> 'occurred'
>   fix misspelled 'streching' -> stretching
>   fix misspelled 'Unkown' -> 'Unknown'
>
>  common/gal/opengl/gl_builtin_shaders.cpp |  4 ++--
>  eeschema/drc_erc_item.cpp|  2 +-
>  eeschema/sch_eagle_plugin.cpp| 16
> 
>  include/tool/tool_manager.h  |  2 +-
>  pcbnew/board_netlist_updater.cpp |  2 +-
>  pcbnew/dialogs/dialog_freeroute_exchange_help.html   |  2 +-
>  pcbnew/dialogs/dialog_keepout_area_properties_base.fbp   |  2 +-
>  .../dialogs/dialog_non_copper_zones_properties_base.fbp  |  2 +-
>  pcbnew/dimension.cpp |  2 +-
>  pcbnew/pcbnew_config.cpp |  2 +-
>  10 files changed, 18 insertions(+), 18 deletions(-)
>
> --
> 2.16.1
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

[Nick Østergaard]

Just the other day a user on IRC showed us this image of a hexagonal fill
he hacked into his board by using bitmap2componet. Sort of a hack^3.

1) export gerbers and convert to PNG with gerbV
2) custom Python Imaging Library (PIL) script
3) bitmap2component

https://i.imgur.com/ThqIz5Y.png

Having native support in kicad is nicer. :) I don't imply we necessarely
need hexagonal fill pattern, this was just an example as inspiration.

In relation to the patch, is it not better to prefix the keyword token with
fill instead of grid?

Just a few comments on how it works in the copper zone properties. I know
you probably didn't invest too much time in this, but I will note it in
case you want some feedback to that. It looks like the combobox for the
fill style is empty when I try to open a zone. This is on an already
existing zone. It errors with a popup that the size and thickness does not
have the proper ratio. Maybe some defaults are needed here for usability.

2018-03-13 21:27 GMT+01:00 Jon Evans :

> OK, Makes sense.
>
> On Tue, Mar 13, 2018 at 4:25 PM, jp charras  wrote:
>
>> Le 13/03/2018 à 20:47, Jon Evans a écrit :
>> > I wonder if it might be a faster algorithm to calculate the perimeter
>> (and holes) of zones, offset
>> > it in by the zone thickness as a polygon, and then draw in the grid as
>> line segments rather than as
>> > more holes in the polygon?
>>
>> This is the first thing I tested. I abandoned this approach:
>> * It is not compatible with the current zone connectivity algo and the
>> current algo to remove
>> insulated islands.
>> * It can be very costly in drawing time because line segments can be very
>> numerous if the zone min
>> thickness is very small (because line segments must be set to this value
>> to be able to "fill" the
>> zone), much more the full polygon approach.
>> (try to fill a zone with a very small min thickness with segments)
>>
>> The zone as polygon is the best way for me.
>>
>> Removing holes in filled areas is not time consuming.
>> Removing not connected copper islands and the connectivity calculation is
>> more time consuming just
>> because there are more vertices.
>> This is also true when using 32 segments instead of 16 segments by circle.
>>
>> >
>> > On Tue, Mar 13, 2018 at 3:44 PM, jp charras > >
>> > wrote:
>> >
>> > Le 13/03/2018 à 20:38, Jon Evans a écrit :
>> > > For the last point, you could use the approach I put in GerbView
>> of start measuring the time, and
>> > > then throw up a progress window if the time exceeds N seconds
>> (with a button to cancel the operation)
>> > > That way you don't even see the window on small boards, but you
>> get the feedback and can cancel the
>> > > operation on large boards.
>> >
>> > Hi Jon,
>> > Filling zones has already this progress window.
>> > Grid pattern just can modify the calculation time due to more
>> vertices in zone outlines.
>> >
>> > >
>> > > On Tue, Mar 13, 2018 at 3:28 PM, jp charras <
>> jp.char...@wanadoo.fr
>> >  > >>
>> > > wrote:
>> > >
>> > > Le 13/03/2018 à 18:24, Seth Hillbrand a écrit :
>> > > > Hi JP-
>> > > >
>> > > > I gave it a spin and definitely like it!  I have been using
>> custom footprints for capacitive
>> > > > sensors, but this is much better.  A couple thoughts:
>> > > >
>> > > > 1) I'd prefer to have the angle saved as a parameter in the
>> file rather than a fixed list of options.
>> > >
>> > > Yes, good idea.
>> > >
>> > > > 2) We'll definitely need to address the polygon issue.  I
>> created a 10cmx10cm board and filled it
>> > > > with 45° at the minimum width/50% fill and my computer
>> froze for 2 minutes while it thought about
>> > > > it.  Strangely, when I checked it was only using one core,
>> so I'm not sure why the wm froze during
>> > > > the calculation.  Maybe some interaction with the graphics
>> card.
>> > > >
>> > >
>> > > Strange.
>> > > What is the zone setup?
>> > >
>> > > For basic boards, the fill zone calculation time is not
>> noticeable on my computer.
>> > > Noticeable calculation time (a few seconds) happens only for
>> *large* boards.
>> > >
>> > >
>> > > > If we can't fix the polygons before this, we should
>> probably have a dummy-check pop-up warning of
>> > > > long compute times.  The polygons get calculated twice on
>> closing the zone edit window.  Once with
>> > > > the cursor showing busy and then again with no indication
>> of work.  This happens again when
>> > > > highlighting.
>> > > >
>> > > > Best-
>> > > > Seth
>> > >
>> > > Trying to guess if the calculation time is 

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

[Nick Østergaard]

I think it would have been better if the commit after 5.0.0-rc1 was not
tagged 5.0.0-rc2-dev. Then the git describe would make more sense. It would
indicate that it was based on the 5.0.0-rc1 with additional commits and its
hash.

The g stands for git according to the man page.
https://git-scm.com/docs/git-describe (search for "-g").

2018-03-12 15:48 GMT+01:00 Wayne Stambaugh :

> On 3/12/2018 10:40 AM, Steven A. Falco wrote:
> > On 03/12/2018 10:23 AM, Jon Evans wrote:
> >> I have seen multiple users who run nightlies think they have RC2
> because they read "5.0.0-rc2" and stop reading after that :-)
> >> Maybe we should switch the tag back to "5.0-dev" between RC releases?
> >> I think all of us developers are going to look up the git hash anyway
> to know exactly when a given version was built, so the "rc2-dev"
> information isn't super necessary for me at least.
> >>
> >> By the way, it's probably annoying to change this because I imagine
> there are scripts that depend on it, but I wish the git hash didn't have a
> "g" in front of it, since if I just double-click that portion of the
> version string I have to manually remove the "g" before pasting it
> elsewhere to look up the hash.
> >
> > I agree that the -rc2 could be confusing.  As to the "g" prefix, that is
> not present in the Fedora nightlies.  They report more like:
> >
> > 5.0.0-rc2-dev-unknown-r12328-8fcbb64a
>
> My bad.  I forgot that -unknown is append to the end of the version
> string when building from a source archive or no git.  Every think
> appended after that is done by the build script.
>
> >
> > where the r12328 is a sequential number representing the number of
> commits to date and the 8fcbb64a is the short SHA of the head commit.
> >
> >   Steve
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Building with visual studio? looking for a tutorial.

[Nick Østergaard]

I can't make cmake find wxwidgets from vcpkg. I think Thomas Figueroa also
uses vcpkg, but he built wxwidgets himself to overcome this. So I think
something is missing for wxwidgets in vcpkg, or something else is not quite
right in that corner.

2018-03-12 23:36 GMT+01:00 Mark Roszko :

> Wayne,
>
> Long term there is good news, VCPKG exists. https://github.com/Mic
> rosoft/vcpkg  right now its separate but eventually it'll be part of VS.
> (But it works now).
>
> It's like msysbut for MSVC and it builds packages locally and puts
> them in a central store. I think most of  Kicad's depedencies are there, I
> actually started to work on seeing if Kicad would compile with it but
> didn't get far before being distracted.
>
>
> On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh 
> wrote:
>
>> Tom,
>>
>> I would prefer KiCad not be in the business of providing dependency
>> binaries.  I can't stop anyone from providing them but I would rather
>> developers focus on kicad development rather than our dependencies as
>> much as possible.  The whole point of removing all of the dependency
>> build code from v4 was specifically for this reason.  The amount of time
>> we were spending supporting this was significant.  I would prefer that
>> the projects provide their own binary installers or we do a better job
>> of choosing dependencies.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
>> > On 12/03/18 19:10, Wayne Stambaugh wrote:
>> >>  The context switching build
>> >> issue will most likely have to be fixed yet again if we choose to go
>> >> down this path.
>> >
>> > Wayne,
>> >
>> > One of the things that Windows does remarkably well is binary
>> > compatibility. We can just provide pre-built libcontext binaries (as
>> > well as binaries of every other dependency for Kicad), say, once a year,
>> > and with a very high probability they will work on every Windows box out
>> > there. I wouldn't worry much about libcontext, I'm more worried about
>> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
>> > newer MSVC versions have fixed such interoperability issues, so I hope
>> > things will go smoothly. Simon has been running MSVC builds for a while,
>> > so he's likely more up-to-date than me in MSVC compatibility.
>> >
>> > Tom
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Mark
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Volunteer

[Nick Østergaard]

If you have a hard time to find a bug worth looking at, you could probably
have a look at https://launchpad.net/kicad/+milestone/5.0.0-rc2  and pick
one where no one is assigned.

2018-03-12 23:38 GMT+01:00 Jeff Young :

> I threw one your way, but it would also be handy to know what platform
> you’re on, as some of them are platform-specific.
>
> Cheers,
> Jeff.
>
>
> > On 12 Mar 2018, at 22:07, hauptmech  wrote:
> >
> > I'm able to do some work on v5-rc bugs. I'm reasonably familiar with all
> corners of the code. Bugs where the desired results are clear from the bug
> discussion are probably best. Just assign them to me on launchpad and I'll
> get to work.
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Git noob question

[Nick Østergaard]

2018-03-12 21:02 GMT+01:00 Kevin Cozens <ke...@ve3syb.ca>:

> On 2018-03-11 11:52 AM, Nick Østergaard wrote:
>
>> That sounds a bit risky. Using the stash and popping can make you lose
>> your local changes if you decide to abort a potential merge conflict. IIRC.
>> Commiting changes are generally safer. Or you could use git stash apply
>> instead.
>>
>
> The risk of lose comes from how you try to resolve the merge conflict that
> arises from trying to apply the stashed changes whether you use pop or
> apply. When applying stashed changes triggers a merge conflict the stashed
> changes stay stashed. If you try to abort a merge git will say there is no
> merge in progress. If you tell git to reset the source tree it will tell
> you that there is a merge in progress so it won't reset the tree.
>

Yes, this is why I say it is not safe for noobs.

>
> You then have code in a Heisenberg box situation. The code is
> simultaneously in the middle of a merge and not in the middle of a merge.
> The only really safe way to protect against potential merge conflict when
> you go to apply the stashed changes is to save the output of a "git diff"
> before you stash changes not yet commited.
>

You could just commit it, if you get lost and need to reset you can just
find the patch my the commit has with reflog.


>
> Subversion was much better about dealing with conflicts. It would tell you
> there is a conflict but apply changes to files so you could see the before
> and after. You then had to manually fix the conflicts. No loss of changes
> and no being unable to access what the changes were. I've had no success
> trying to save stashed changes as a file so I could manually fix a merge
> conflict.
>

IMHO it is different, not better. :)

>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/|"Nerds make the shiny things that
> distract
> https://patreon.html/KevinCozens | the mouth-breathers, and that's why
> we're
>  | powerful"
> Owner of Elecraft K2 #2172   |
> #include   | --Chris Hardwick
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Pushed change

[Nick Østergaard]

It looks like it just passed the build here,
http://ci.kicad-pcb.org/job/linux-kicad-full-gcc-head/3072/

2018-03-12 22:03 GMT+01:00 Jeff Young :

> Well, my build is still running so I can’t confirm the fixes yet, but
> since I already broke the build for some I went ahead and pushed “fixes”.
>
> We’ll see if they actually are shortly. ;)
>
>
> > On 12 Mar 2018, at 20:33, Kevin Cozens  wrote:
> >
> > On 2018-03-12 03:19 PM, Jeff Young wrote:
> >> I just pushed a change which removes a bunch of unnecessary boilerplate.
> >> But it occurs to me that maybe it’s necessary with pickier
> compilers?  Anyway, if someone could try it on Windows and/or Unix that
> would be great.
> > Oops. Something broke. I'm using g++ (Ubuntu 5.4.0-6ubuntu1~16.04.9)
> 5.4.0 20160609 under Linux Mint 18.3
> >
> >
> > /home/user/Projects/Kicad/kicad/cvpcb/cvpcb_mainframe.cpp: In member
> function ‘void CVPCB_MAINFRAME::UpdateTitle()’:
> > /home/user/Projects/Kicad/kicad/cvpcb/cvpcb_mainframe.cpp:740:43:
> error: operands to ?: have different types ‘const wxChar* {aka const
> wchar_t*}’ and ‘const wxString’
> >   fn.IsFileWritable() ? wxEmptyString : _( " [Read
> Only]" ) );
> >   ^
> > /home/user/Projects/Kicad/kicad/cvpcb/cvpcb_mainframe.cpp:740:43: note:
> and each type can be converted to the other
> > cvpcb/CMakeFiles/cvpcb_kiface.dir/build.make:326: recipe for target
> 'cvpcb/CMakeFiles/cvpcb_kiface.dir/cvpcb_mainframe.cpp.o' failed
> > make[2]: *** [cvpcb/CMakeFiles/cvpcb_kiface.dir/cvpcb_mainframe.cpp.o]
> Error 1
> > CMakeFiles/Makefile2:817: recipe for target 
> > 'cvpcb/CMakeFiles/cvpcb_kiface.dir/all'
> failed
> > make[1]: *** [cvpcb/CMakeFiles/cvpcb_kiface.dir/all] Error 2
> > Makefile:149: recipe for target 'all' failed
> > make: *** [all] Error 2
> >
> >
> > --
> > Cheers!
> >
> > Kevin.
> >
> > http://www.ve3syb.ca/| "Nerds make the shiny things that
> > https://www.patreon.html/KevinCozens | distract the mouth-breathers, and
> > | that's why we're powerful"
> > Owner of Elecraft K2 #2172   |
> > #include   | --Chris Hardwick
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] pcbnew alignment bugfixes

[Nick Østergaard]

It looks like this has been merged.

2018-03-01 5:00 GMT+01:00 Seth Hillbrand :

> Oops! Noticed that 1+2 should have been in the same patch (fixing my own
> bug there)
>
> I've squashed them down to three patches.
>
> -S
>
> 2018-02-28 16:52 GMT-08:00 Seth Hillbrand :
>
>> ​Attached are 4 patches for various alignment issues.
>>
>> The first fixes https://bugs.launchpad.net/kicad/+bug/1751352 where pads
>> are moved despite being locked.
>>
>> The second is a bugfix where aligning in the X direction moved things in
>> the Y direction.
>>
>> The third is a bugfix for when you select both a pad and the pad's parent
>> module before aligning.
>>
>> The fourth is not a bugfix and, as such should be considered highly
>> optional at this point.  But it fixes an annoyance when aligning a group of
>> things to their centers.  I can never tell which item will be chosen for
>> the center as currently it chooses the "centermost" item.  If you have
>> 10-20 mostly-aligned items, it's very hard to tell which will be the
>> center.  You need to move about half to one side and about half to the
>> other before aligning.  Or align, check the value and do a second move.
>> Instead, this chooses the left-most for X-center and top-most for
>> Y-center.  You can then move one item into place and align the others to
>> it.  Delaying this has no affect of the other patches, so I'm happy to hold
>> it for post-5.​
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Dynamic text in schematic and board.

[Nick Østergaard]

Den 8. mar. 2018 22.39 skrev "Russell Oliver" :

As a follow up to the road map discussion I saw a forum post asking if it
was possible to display the net name of a pad on the silkscreen or other
layers much like the value or reference fields.


Why is this useful? Could you explain the exact use case?


While a simple implementation would be to create a text item directly
linked to each pad that could be enabled, and shows the link to the
relevant pad,  I think a more generic approach would be great to have.

I propose that either or both of these options for version 7.

a) standalone text items are processed as a template.  A domain specific
language would be designed to allow for references to items as direct text
substitutions. The implementation, scope and style of this DSL will need to
be workshopped and would like your comments on.

b) linked text (annotations) showing a graphical link (like the blue line
of values and reference ) A text item is created as a link to another item,
for which the text is derived from a list of properties of that item. This
would include such things as values, references, custom symbol and
footprint fields, sizes, positions, net names, net codes.

I'm almost certain this would require the updated Schematic object in
eeschema, but might already be achievable in pcbnew given its current
architecture, but that's more of a guess than anything.

Any thoughts, guidance or critiques would be appreciated.

Kind Regards
Russell


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

Re: [Kicad-developers] Git noob question

[Nick Østergaard]

Den 10. mar. 2018 23.36 skrev "Kevin Cozens" :

On 2018-03-03 03:50 PM, Maciej Suminski wrote:

> If we are speaking about git tips - I think 'git pull --rebase' is even
> simpler in this case.
>

I have a script I call "gitpull" that does that but it also does a "git
stash" before the pull and a "git stash pop" after the pull.


That sounds a bit risky. Using the stash and popping can make you lose your
local changes if you decide to abort a potential merge conflict. IIRC.
Commiting changes are generally safer. Or you could use git stash apply
instead.



-- 
Cheers!

Kevin.

http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
| powerful!"
#include  | --Chris Hardwick

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

Re: [Kicad-developers] Building with visual studio? looking for a tutorial.

[Nick Østergaard]

https://git.launchpad.net/~sjr/kicad/log/?h=msvc

2018-03-09 16:41 GMT+01:00 Nick Østergaard <oe.n...@gmail.com>:

> You need to base it on Simon Richters branch.
>
> 2018-03-09 16:05 GMT+01:00 Tomasz Wlostowski <tomasz.wlostow...@cern.ch>:
>
>> On 09/03/18 15:55, Jon Evans wrote:
>> > One other thing that might be worth trying is to use Qt Creator to
>> > build/debug.  It can be used as a frontend for GCC/GDB and might get
>> > around your Ctrl-C issue.
>>
>> Looks like a good idea, will give it a try!
>>
>> Tom
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp