not really quite ontopic, (because it is more wxwindows related) but
I
followed the instructions
on building wxpython on ubuntu after the wiki page
When trying to compile wxWidgets (configure) it said:
configure: error: OpenGL libraries not available
I tried to install several gstreamer packages and libstream(xx), but
no
success.
What package do I need?
···
--
I left out the --enable-mediactrl, and compilation suceeded
Then I wanted to build wxpython, but at once at the beginning, there
were several errors.
Is that trunk branch not compatible with wxwidgets one?
/usr/bin/install -c -d /home/franz/src/wxWidgets_2_9_0/mydest/lib
/usr/bin/install -c -m 644 /home/franz/src/wxWidgets_2_9_0/mydest/lib/
libwx_gtk2ud-2.9.so /home/franz/src/wxWidgets_2_9_0/mydest/lib
/usr/bin/install: cannot open `/home/franz/src/wxWidgets_2_9_0/mydest/
lib/libwx_gtk2ud-2.9.so' for reading: No such file or directory
first entry was:
/usr/bin/install -c -m 644 /home/franz/src/wxWidgets_2_9_0/mydest/lib/
libwx_baseud-2.9.so /home/franz/src/wxWidgets_2_9_0/mydest/lib
/usr/bin/install: cannot stat `/home/franz/src/wxWidgets_2_9_0/mydest/
lib/libwx_baseud-2.9.so': No such file or directory
because it is currently named:
/home/franz/src/wxWidgets_2_9_0/mydest/lib/libwx_baseud-2.9.so.0
/home/franz/src/wxWidgets_2_9_0/mydest/lib/libwx_baseud-2.9.so.0.0.0
one difference is, from what I saw at the first glances, that you must
know before exactly the number of items used in
flexgridsizer, otherwise there is an excpetion (that was not the case
in 2.8)
another one is
wx.MessageBox("a", "b", wx.ICON_EXCLAMATION)
that was ok in 2.8, now it is needed either wx.YES, ... additionally
so:
wx.MessageBox("a", "b", wx.ICON_EXCLAMATION | wx.YES)
is ok for 2.9.
I'm curious, if there were still some other changes.
Did anyone recently build current wxPython under ubuntu?
Did i made something wrong?
The build wiki page could be updated again
Finally I got it to run.
When I started DrPython with 2.9, I thought: Oh my god!
There were apparantly a few changes with sizers, ...
IIRC there was only one change to sizers that I remember that actually affected their layout behavior, and it was determined that only a very few use cases would actually be affected by it. Apparently you were one of the few. Sorry about that.
I will have to repair DrPython or (in other words) make it fit for
wxPy 2.9.
One question: Can I rely, that there are no big changes anymore,
No, there will likely be many, much bigger changes over the life of the 2.9.x series. That's why it's called "unstable" See ReleaseSeries - wxPyWiki
or
in other words:
should I wait until wxPy 2.9 is "officially" released, before I begin
to
make drpyhton run again without bugs?
2.9.0 will essentially be exactly what you see now, but be prepared for more changes in future 2.9.x releases.
···
On 7 Aug., 10:44, franz steinhaeusler <franz.steinhaeus...@gmail.com> > wrote:
one difference is, from what I saw at the first glances, that you must
know before exactly the number of items used in
flexgridsizer, otherwise there is an excpetion (that was not the case
in 2.8)
another one is
wx.MessageBox("a", "b", wx.ICON_EXCLAMATION)
that was ok in 2.8, now it is needed either wx.YES, ... additionally
so:
wx.MessageBox("a", "b", wx.ICON_EXCLAMATION | wx.YES)
is ok for 2.9.
I'm curious, if there were still some other changes.
See the wxWidgets changes.txt and the wxPython CHANGES.txt.
>> Did anyone recently build current wxPython under ubuntu?
>> Did i made something wrong?
>> The build wiki page could be updated again
> Finally I got it to run.
> When I started DrPython with 2.9, I thought: Oh my god!
> There were apparantly a few changes with sizers, ...
IIRC there was only one change to sizers that I remember that actually
affected their layout behavior, and it was determined that only a very
few use cases would actually be affected by it. Apparently you were one
of the few. Sorry about that.
Ok, it is not so bad. Only the flexgridsizer requires the right amount
of rows or columns. In some cases, the rows exceeded the number of
specified values. So I replaced the first argument by 0.
> I will have to repair DrPython or (in other words) make it fit for
> wxPy 2.9.
> One question: Can I rely, that there are no big changes anymore,
No, there will likely be many, much bigger changes over the life of the
2.9.x series. That's why it's called "unstable" Seehttp://wiki.wxpython.org/ReleaseSeries
> or
> in other words:
> should I wait until wxPy 2.9 is "officially" released, before I begin
> to
> make drpyhton run again without bugs?
2.9.0 will essentially be exactly what you see now, but be prepared for
more changes in future 2.9.x releases.
Ok, thanks
···
On 10 Aug., 20:23, Robin Dunn <ro...@alldunn.com> wrote:
> On 7 Aug., 10:44, franz steinhaeusler <franz.steinhaeus...@gmail.com> > > wrote:
Did anyone recently build current wxPython under ubuntu?
Did i made something wrong?
The build wiki page could be updated again
Finally I got it to run.
When I started DrPython with 2.9, I thought: Oh my god!
There were apparantly a few changes with sizers, ...
IIRC there was only one change to sizers that I remember that actually
affected their layout behavior, and it was determined that only a very
few use cases would actually be affected by it. Apparently you were one
of the few. Sorry about that.
Ok, it is not so bad. Only the flexgridsizer requires the right amount
of rows or columns. In some cases, the rows exceeded the number of
specified values. So I replaced the first argument by 0.
Ah, that was different than the change I was thinking of. Basically for this one they just added an assert to ensure that the parameters to the constructor are correct. In the demo I just changed all FGSs to use keyword args, and that not only fixed this problem but it eliminated some confusion too.
fgs = wx.FlexGridSizer(cols=3, hgap=10, vgap=10)
···
On 10 Aug., 20:23, Robin Dunn <ro...@alldunn.com> wrote:
On 7 Aug., 10:44, franz steinhaeusler <franz.steinhaeus...@gmail.com> >>> wrote: