Blender 2.8 Support

Andrea Gavana wrote:

Hi James,

I am using the latest version of wxpython and everyone writes that i should
use blender as my GUI builder the one issue is that it doesn't work! What do
you people use for a GUI builder

I usually do everything by hand, using wx.aui to layout the main
components in the application frame. However, sometimes I build
complex layouts also using wxGlade, which is my favourite one.
However, there are also other possibilities, like Boa Constructor for
example.

I also would recommend just coding your GUI. Maybe this isn't practical in other toolkits but in wxPython, getting an app up and running is very easy. If you are new to wxPython and pressed for time, perhaps putting up with a learning curve is impractical. Don't forget to look at XRC which comes with the wxPython Docs and Demos, and is what I hear a bunch of people use for creating their GUIs. However otherwise I would greatly recommend learning sizers and layout.

I have attached two screen shots of my most recent application. Each tab took me only a few minutes to layout and tweak (the underlying functionality of course, took much longer :). Once you understand sizers, making a layout like this is pretty trivial. Plus it will be much easier to code the communication between, and the control of everything appropriately, because something else didn't create the GUI code for you.

Maybe there are lots of people out there who have had great success from just using GUI builders though, and prefer them over coding even though they are quite comfortable coding a GUI? I would be interested to hear about people in these positions.

- Mike

···

On 4/11/07, James Matthews wrote:

Andrea Gavana wrote:

Hi Mike and All,

Andrea Gavana wrote:
> Hi James,
>
>> I am using the latest version of wxpython and everyone writes that i
>> should
>> use blender as my GUI builder the one issue is that it doesn't work!
>> What do
>> you people use for a GUI builder
>
> I usually do everything by hand, using wx.aui to layout the main
> components in the application frame. However, sometimes I build
> complex layouts also using wxGlade, which is my favourite one.
> However, there are also other possibilities, like Boa Constructor for
> example.
>

I also would recommend just coding your GUI. Maybe this isn't practical
in other toolkits but in wxPython, getting an app up and running is very
easy. If you are new to wxPython and pressed for time, perhaps putting
up with a learning curve is impractical. Don't forget to look at XRC
which comes with the wxPython Docs and Demos, and is what I hear a bunch
of people use for creating their GUIs. However otherwise I would greatly
recommend learning sizers and layout.

I have attached two screen shots of my most recent application. Each tab
took me only a few minutes to layout and tweak (the underlying
functionality of course, took much longer :). Once you understand
sizers, making a layout like this is pretty trivial. Plus it will be
much easier to code the communication between, and the control of
everything appropriately, because something else didn't create the GUI
code for you.

Nice screenies :-D. It looks like CustomTreeCtrl has helped you,
unless I am misinterpreting the second screenshot and you are using a
normal TreeCtrl.

Yes it is your CustomTreeCtrl :D. It has been incredibly stable and wonderful since the 2.8.3 patches plus your horizontal scroll patch. After I made the screen shot I thought I should have expanded a few nodes to show it off more but, I was too lazy to make it again.

Maybe there are lots of people out there who have had great success from
just using GUI builders though, and prefer them over coding even though
they are quite comfortable coding a GUI? I would be interested to hear
about people in these positions.

Well, that depends on the layout I want to construct and what I have
in mind. If a panel, for example, has a very complex hierachy of
boxsizers, flexgridsizers and friends, I feel very confortable with
wxGlade, with which I can visualize the widgets layout and panel
appearance while building the panel. It is a very useful tool in my
opinion, but I think it's just a matter of taste. Just pick up the
tool (or the solution) with which you feel most confortable.

Yes, I guess this makes sense. The layouts in my screenshots don't have sizers nested very deeply I suppose, so it was not very complex to code. The way I keep it simple is by making a few panels, for example tab1.png is three panels in an hsizer, and tab2.png is two panels in an hsizer. In fact there is only one non-BoxSizer, which I think is the 2x2 grid of Checkbox ListCtrls.

So if you were making something like either of these tabs in a gui designer, would it all be in one gigantic (code-wise) panel? Or is it easy to make a bunch of separate panels and then reference them later from another sizer. In my small experience with GUI builders (really only wxGlade and XRC) they generate some nasty (or at least confusingly verbose) code sometimes, generally to the point that finding all the things I need in the generated code to add functionality cancels out the time saved by just doing it myself. Maybe I will have to give Boa a try though, it seems I am hearing good things.

- Mike

···

On 4/11/07, Mike Rooney wrote:

> On 4/11/07, James Matthews wrote: