Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hi Miles, I use archlinux and used this AUR package to install phoenix, https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-wxpython-phoenix Then I applied your patch and added that header file to kicad as shown on https://github.com/nickoe/kicad-source-mirror/compare/master...nickoe:di

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

So I'd like to help out and take a look, but getting wxphoenix with gtk2 is proving a bit challenging. I did manage to install something (albeit the wrong one) in the past. Nick, what command did you use to install? Miles I have a fresh virtual ubuntu 16.04 install. I think I ran my normal pk

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hello Wayne, as Nick has written about a different part in this thread ... Am 24.11.17 um 14:00 schrieb Wayne Stambaugh: > I'm surprised there is no RFP for phoenix yet given that it will (has) > become the replacement for wxpython. wxpython is a dead code base as > far as I know. I certainly c

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hello Miles, Since it seems that Phoenix has now been released I just tried to test against it with your patch. But I get a build error related to sip. [ 75%] Building CXX object pcbnew/CMakeFiles/pcbnew_kiface.dir/pcbnew.cpp.o In file included from /home/nickoe/kicad-source-mirror/pcbnew/swig/py

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

wxwidgets does not work well (at all?) when build with gtk3. If your custom build of phoenix and/or wxwidgets was built against gtk3, you are going to issues. Until the wx project resolves it's gtk3 issues, kicad must be built with wx built with gtk2. On 11/24/2017 04:19 AM, miles mccoo wrote: >

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hi Miles, On 11/24/2017 10:19 AM, miles mccoo wrote: > in reply to Wayne's request to run the footprint wizard > > I run the footprint wizard; it seems to run fine. > when I press the 3D view button, I get a popup complaining about not > finding the wx gtk2 library > "10:14:11: libwx_gtk2u_core

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

On 11/23/2017 03:44 PM, Carsten Schoenert wrote: > Am 23.11.2017 um 17:28 schrieb Wayne Stambaugh: > ... >>> The short version: Kicad will probably want to wait to move to the >>> Phoenix version of wxPython. >> >> Not until they are package in Debian stable. This is my litmus test for >> availabi

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

in reply to Wayne's request to run the footprint wizard I run the footprint wizard; it seems to run fine. when I press the 3D view button, I get a popup complaining about not finding the wx gtk2 library "10:14:11: libwx_gtk2u_core-3.0.so.0: cannot open shared object file: No such file or directo

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

On 11/23/2017 03:32 PM, miles mccoo wrote: > Thanks all, for the replies > > Thank you for merging my patch. > > I'm pleased to read that the Kicad takes the python interface seriously. > > Abstraction layer. I've considered writing one or at least submitting > patches to move in that direction[

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

I guess this is the same idea as with https://github.com/KiCad/kicad-python 2017-11-23 19:28 GMT+01:00 Greg Smith : > "I was simply afraid that we > may spent a lot of time petting the SWIG interface, which we will nuke > it and start from scratch because of inevitable switch to Phoenix." > > I a

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

On 11/23/2017 12:04 PM, Maciej Sumiński wrote: > Hi Miles, > > On 11/23/2017 04:17 PM, miles mccoo wrote: >> In a recent thread >> on this list, >> it was mentioned that kicad may need to drop support for SWIG/Python due to >> wx and wxP

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Am 23.11.2017 um 17:28 schrieb Wayne Stambaugh: ... >> The short version: Kicad will probably want to wait to move to the >> Phoenix version of wxPython. > > Not until they are package in Debian stable. This is my litmus test for > availability of new dependencies. I do not want kicad to be in t

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Thanks all, for the replies Thank you for merging my patch. I'm pleased to read that the Kicad takes the python interface seriously. Abstraction layer. I've considered writing one or at least submitting patches to move in that direction[1] but I got sidetracked trying to document what's already

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

"I was simply afraid that we may spent a lot of time petting the SWIG interface, which we will nuke it and start from scratch because of inevitable switch to Phoenix." I agree. I would suggest that the Python API is not quite stable enough to freeze the API. If we desire a stable interface/API, o

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hi Miles, On 11/23/2017 04:17 PM, miles mccoo wrote: > In a recent thread > on this list, > it was mentioned that kicad may need to drop support for SWIG/Python due to > wx and wxPython limitations. > > Perhaps I misinterpreted what was

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

On 23/11/17 16:17, miles mccoo wrote: > > PS - AFAIK, the patch that triggered mention of dumping python due to > wxPython still hasn't been denied or merged. :-) > https://lists.launchpad.net/kicad-developers/msg31700.html > > Hi Miles, I just committed your patch. Thanks for your contribution

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

On 11/23/2017 10:17 AM, miles mccoo wrote: > > In a recent thread > on this > list, it was mentioned that kicad may need to drop support for > SWIG/Python due to wx and wxPython limitations. > > Perhaps I misinterpreted what was said. >

[Kicad-developers] Getting kicad to work with wxPython Phoenix

In a recent thread on this list, it was mentioned that kicad may need to drop support for SWIG/Python due to wx and wxPython limitations. Perhaps I misinterpreted what was said. It's my perception that the kicad team doesn't see the valu