Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-11 Thread Wayne Stambaugh
On 4/11/2018 1:52 PM, Bernhard Stegmaier wrote:
> 
>> On 11. Apr 2018, at 19:18, Wayne Stambaugh  wrote:
>>
>> On 4/11/2018 11:02 AM, Bernhard Stegmaier wrote:
>>>
>>>
 On 11. Apr 2018, at 16:40, Wayne Stambaugh > wrote:

>
> Last point: Is there a list of issue detected with GTK3 ? Some bugs are
> tagged with that ?

 Not that I am aware of.  Some of the related bug reports may be tagged
 with gtk3 but I'm not sure.  If not, that would be a good thing so we
 can start correcting some of them during the v6 development cycle.
>>>
>>> AFAIK gtk3 also doesn’t support XOR-drawing?
>>> So, legacy canvases will probably be as bad or even worse than on macOS…
>>> at least, regarding performance.
>>
>> I believe (although I could be wrong) all that happened with regard to
>> gtk3 is that wxDC == wxGCDC which draws on the advanced
>> wxGraphicsContext object which AFAIK supports transparency so XOR
>> drawing should not be an issue.  The perform issue can probably solved
>> by drawing to a wxMemoryDC first and blitting it to the display.
> 
> The thing is how the wxGCDC is implemented on top of gtk? or other stuff.
> 
> macOS also uses the wxGCDC but although defined in wxGCDC in the 
> backend/macOS-specific implementation the XOR is just not implemented (but 
> mapped to some other function) because macOS doesn’t support it (it does 
> support a XOR blending mode, but that is different from the logical XOR meant 
> here).
> 
> I thought that I read somewhere (long time ago, when I tried to understand 
> why it doesn’t work on macOS) that gtk3 also will not have a logical XOR, but 
> maybe I just got that wrong or things have changed. I didn’t follow up on 
> that.
> 
> As far as I can remember Orson made some changes not long ago to redraw 
> everything every time in case of gtk3 (I tested the patch and it was bad for 
> performance on macOS)… this shouldn’t be needed if XOR would work?

Drawing directly to the device context is the problem unless there is
some type of memory double buffering working at the os level.  wxWidgets
provides abstractions for wxMemoryDC so you don't call a drawing
primitive directly for each object drawn.  This is what kills
performance on gtk+ and I'm guessing macos since it seems to suffer from
the same issue.

> 
> 
> Regards,
> Bernhard
> 

___
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] wxPython-gtk3 woes

2018-04-11 Thread Bernhard Stegmaier

> On 11. Apr 2018, at 19:18, Wayne Stambaugh  wrote:
> 
> On 4/11/2018 11:02 AM, Bernhard Stegmaier wrote:
>> 
>> 
>>> On 11. Apr 2018, at 16:40, Wayne Stambaugh >> > wrote:
>>> 
 
 Last point: Is there a list of issue detected with GTK3 ? Some bugs are
 tagged with that ?
>>> 
>>> Not that I am aware of.  Some of the related bug reports may be tagged
>>> with gtk3 but I'm not sure.  If not, that would be a good thing so we
>>> can start correcting some of them during the v6 development cycle.
>> 
>> AFAIK gtk3 also doesn’t support XOR-drawing?
>> So, legacy canvases will probably be as bad or even worse than on macOS…
>> at least, regarding performance.
> 
> I believe (although I could be wrong) all that happened with regard to
> gtk3 is that wxDC == wxGCDC which draws on the advanced
> wxGraphicsContext object which AFAIK supports transparency so XOR
> drawing should not be an issue.  The perform issue can probably solved
> by drawing to a wxMemoryDC first and blitting it to the display.

The thing is how the wxGCDC is implemented on top of gtk? or other stuff.

macOS also uses the wxGCDC but although defined in wxGCDC in the 
backend/macOS-specific implementation the XOR is just not implemented (but 
mapped to some other function) because macOS doesn’t support it (it does 
support a XOR blending mode, but that is different from the logical XOR meant 
here).

I thought that I read somewhere (long time ago, when I tried to understand why 
it doesn’t work on macOS) that gtk3 also will not have a logical XOR, but maybe 
I just got that wrong or things have changed. I didn’t follow up on that.

As far as I can remember Orson made some changes not long ago to redraw 
everything every time in case of gtk3 (I tested the patch and it was bad for 
performance on macOS)… this shouldn’t be needed if XOR would work?


Regards,
Bernhard
___
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] wxPython-gtk3 woes

2018-04-11 Thread Wayne Stambaugh
On 4/11/2018 11:02 AM, Bernhard Stegmaier wrote:
> 
> 
>> On 11. Apr 2018, at 16:40, Wayne Stambaugh > > wrote:
>>
>>>
>>> Last point: Is there a list of issue detected with GTK3 ? Some bugs are
>>> tagged with that ?
>>
>> Not that I am aware of.  Some of the related bug reports may be tagged
>> with gtk3 but I'm not sure.  If not, that would be a good thing so we
>> can start correcting some of them during the v6 development cycle.
> 
> AFAIK gtk3 also doesn’t support XOR-drawing?
> So, legacy canvases will probably be as bad or even worse than on macOS…
> at least, regarding performance.

I believe (although I could be wrong) all that happened with regard to
gtk3 is that wxDC == wxGCDC which draws on the advanced
wxGraphicsContext object which AFAIK supports transparency so XOR
drawing should not be an issue.  The perform issue can probably solved
by drawing to a wxMemoryDC first and blitting it to the display.

> 
> 
> Regards
> Bernhard
> 

___
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] wxPython-gtk3 woes

2018-04-11 Thread Bernhard Stegmaier


> On 11. Apr 2018, at 16:40, Wayne Stambaugh  wrote:
> 
>> 
>> Last point: Is there a list of issue detected with GTK3 ? Some bugs are
>> tagged with that ?
> 
> Not that I am aware of.  Some of the related bug reports may be tagged
> with gtk3 but I'm not sure.  If not, that would be a good thing so we
> can start correcting some of them during the v6 development cycle.

AFAIK gtk3 also doesn’t support XOR-drawing?
So, legacy canvases will probably be as bad or even worse than on macOS… at 
least, regarding performance.


Regards
Bernhard

___
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] wxPython-gtk3 woes

2018-04-11 Thread Wayne Stambaugh
On 4/11/2018 9:12 AM, Jean-Samuel Reynaud wrote:
> Hi all,
> 
> First: for PPA, I disable for the moment WXPYTHON when needed (for
> bionis...). So it fixing temporary this issue
> (https://bugs.launchpad.net/kicad/+bug/1762432)

Thank you for fixing this.

> 
> Second: I'm one of the user(s ?) who use wxpython for GUI in plugins.
> I'm sure is not a major feature (yet). Anyway the possibility to create
> plugins to KiCad in python with a minimal UI (simple dialog boxes...) is
> really useful to add features that require input parameters...

This is going to a maintenance issue util KiCad, wxPython (or
wxPhoenix), and gtk3 all play nice together.  We may have to live
without wxPython support on linux for a while.

> 
> Last point: Is there a list of issue detected with GTK3 ? Some bugs are
> tagged with that ?

Not that I am aware of.  Some of the related bug reports may be tagged
with gtk3 but I'm not sure.  If not, that would be a good thing so we
can start correcting some of them during the v6 development cycle.

> 
> Regards,
> Le 10/04/2018 à 13:35, Maciej Sumiński a écrit :
>> 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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-11 Thread Wayne Stambaugh
According to this documentation, wxPython versions can be defined by:

wx-VERSION [-PORT-CHARTYPE [-FLAVOUR]]

VERSION: By default this will be just the first two components of the
VersionNumbers, (or the first three in an "unstable" release series) but
the version selection code will support using all four components of the
version number if you would like to manage it that way on your own.

PORT: This represents the wxWidgets port that was used to build
wxPython. For Windows and Mac you can ignore this as there is only one
port each that is currently supported for those platforms. Currently on
unix systems there are two possible values, "gtk" and "gtk2".

CHARTYPE: This will either be "ansi" or "unicode" depending on how
wxWidgets and wxPyton were built. In the unicode build then all strings
passed to wx functions and methods will first be converted to unicode
objects using the default encoding, and all string values returned from
wx functions and methods will actually be unicode objects. See
UnicodeBuild for more info.

FLAVOUR: This is an arbitrary tag that can be used in wxWidgets builds
to further distinguish custom builds from stock ones. wxPython supports
it as well but doesn't use it by default.

Here are some possible directory names:

wx-2.5.3
wx-2.5.3-gtk2-unicode
wx-2.5.3.0-gtk2-unicode

This seems like a viable solution.  We could use cmake to add the
wxPython import version to an automatically generated header file that
the developer could override during build config.  Obviously the distro
packagers would have to build multiple versions of wxPython which is
probably a more difficult issue to resolve.

On 4/10/2018 9:36 AM, Nick Østergaard wrote:
> 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].
> >
> 

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-11 Thread Jean-Samuel Reynaud
Hi all,

First: for PPA, I disable for the moment WXPYTHON when needed (for
bionis...). So it fixing temporary this issue
(https://bugs.launchpad.net/kicad/+bug/1762432)

Second: I'm one of the user(s ?) who use wxpython for GUI in plugins.
I'm sure is not a major feature (yet). Anyway the possibility to create
plugins to KiCad in python with a minimal UI (simple dialog boxes...) is
really useful to add features that require input parameters...

Last point: Is there a list of issue detected with GTK3 ? Some bugs are
tagged with that ?

Regards,
Le 10/04/2018 à 13:35, Maciej Sumiński a écrit :
> 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
> 




signature.asc
Description: OpenPGP digital signature
___
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] wxPython-gtk3 woes

2018-04-10 Thread 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 :

> 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 : 

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread 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

2018-04-10 Thread Maciej Suminski
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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Jeff Young
+1

> On 10 Apr 2018, at 14:14, Wayne Stambaugh  wrote:
> 
> I'm fine with that given that there is a reasonable probability that
> wxPython support will be disabled for some platforms until we resolve
> the gtk3 issues.
> 
> On 4/10/2018 9:14 AM, Adam Wolf wrote:
>> Right now, one of the last blockers for the Mac v5 packaging efforts
>> is wxpython.  If it's having issues on other platforms, I may actually
>> table that for a few days and see if we can get everything else going,
>> and then we can have a good* (minus wxpython) rc2 for testing, and
>> then tackle wxpython as the last remaining thing.
>> 
>> Does that seem reasonable?
>> 
>> Adam
>> 
>> On Tue, Apr 10, 2018 at 7:56 AM, Wayne Stambaugh  
>> wrote:
>>> 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 : 

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Wayne Stambaugh
I'm fine with that given that there is a reasonable probability that
wxPython support will be disabled for some platforms until we resolve
the gtk3 issues.

On 4/10/2018 9:14 AM, Adam Wolf wrote:
> Right now, one of the last blockers for the Mac v5 packaging efforts
> is wxpython.  If it's having issues on other platforms, I may actually
> table that for a few days and see if we can get everything else going,
> and then we can have a good* (minus wxpython) rc2 for testing, and
> then tackle wxpython as the last remaining thing.
> 
> Does that seem reasonable?
> 
> Adam
> 
> On Tue, Apr 10, 2018 at 7:56 AM, Wayne Stambaugh  wrote:
>> 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: 

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Adam Wolf
Right now, one of the last blockers for the Mac v5 packaging efforts
is wxpython.  If it's having issues on other platforms, I may actually
table that for a few days and see if we can get everything else going,
and then we can have a good* (minus wxpython) rc2 for testing, and
then tackle wxpython as the last remaining thing.

Does that seem reasonable?

Adam

On Tue, Apr 10, 2018 at 7:56 AM, Wayne Stambaugh  wrote:
> 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

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Wayne Stambaugh
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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread 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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread jp charras
Le 10/04/2018 à 13:54, Nick Østergaard a écrit :
> 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

footprint wizards do not need wxPython.

I am usually building kicad on W7 with wxPython support off, and I do not have 
issues with wizards
and external plugins.

Only plugins that use a wxPython graphic resources can have issues, and I do 
not know if they exist.
So for most of users, wxPython support is not mandatory.

Phoenix is for tomorrow, not for today.

It was not buildable on msys2 when I tried to build it.
I hope Phoenix will use one day cmake (wxWidgets 3.1.1 can be built using cmake 
now).

-- 
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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Mitja Nemec
Miles Mccoo might have some new info regarding Phoenix 
(https://lists.launchpad.net/kicad-developers/msg31889.html) 

On Tuesday, 10 April 2018, 13:55, Nick Østergaard  wrote:
 

 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


   ___
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] wxPython-gtk3 woes

2018-04-10 Thread Mitja Nemec
I'd hate to loose this feature primarily as an user of action plugins and as an 
author of them. 

On Tuesday, 10 April 2018, 13:36, 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


Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread 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] wxPython-gtk3 woes

2018-04-10 Thread 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
> 
> 




signature.asc
Description: OpenPGP digital signature
___
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] wxPython-gtk3 woes

2018-04-10 Thread Jeff Young
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