wxGlade GUI builder release 0.8.0

Hi!

  I'm pleased to announce the availability of wxGlade revision

0.8.0 from the download page

wxGlade is a GUI builder for wxPython/wxWidgets.
Revision 0.8 is a major change. If you have evaluated previous
versions, please give 0.8 a try.

  A snapshot of the included documentation is also available here:

http://wxglade.sourceforge.net/docs/index.html

Major changes compared to 0.7.x:

  • Support for wxPython Phoenix and Python 3
  • More consistent user interface.
  •       Rewritten documentation / tutorial and examples; the target
    
    audience includes people who are just starting with wxPython.
  •       Repeat feature (Ctrl-R and Ctrl-Y) to apply property
    
    change(s) to multiple widgets
  • new Menu and Toolbar editors
  • support for GridBagSizer

Generated Code:

  • bind menu handlers without the need for user-defined IDs
  • default file encoding is now UTF-8

Internal:

  •       very major refactoring of property handling, code generation
    
    and sizers
  • reformatted code and comments to be more compact
  • always use DestroyLater to avoid crashes
  •       less redundant calls to widget.Show() to reduce display
    
    errors
  • better handling of size changes due to fonts
  • refactored testing

The changes from the last beta versions:

  • some bug fixes

  • examples for Custom Widget updated and documented:

        matplotlib, html, html2, py shell, SpeedMeter
    Especially the Matplotlib examples should be very useful if
    

you’re implementing data analysis applications.

The project repository is now on GitHub: https://github.com/wxGlade/wxGlade

The bug tracker is here: https://github.com/wxGlade/wxGlade/issues
(It’s also linked from the help menu.)

The wxGlade mailing list: https://sourceforge.net/p/wxglade/mailman/wxglade-general/

The plans for 0.9:

  •     change user interface (combine Palette, Tree and Properties
    
    windows)
  •     support events from the base classes and the addition of any
    
    event type as text
  • code properties: use stc and resize dynamically
  • toolbar and maybe menu editor: add Drop target for images
  • Notebook: add context menu entries ‘add page’ / ‘remove page’
  •     option to remove all the BEGIN/END wxGlade comments in the
    
    generated code (only with overwrite True)
  •     lib.buttons (feature request #45 Add support for generic
    
    buttons)
  •     Button: support more images (for normal, disabled, pressed,
    
    focus, current)
  • WrapSizer, maybe also StdDialogButtonSizer

Regards,

Dietmar

···


https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/
[

  ](https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/)

Congrats Dietmar!

···

Robin

On Monday, March 26, 2018 at 3:24:33 AM UTC-7, Dietmar Schwertberger wrote:

Hi!

  I'm pleased to announce the availability of wxGlade revision

0.8.0 from the download page
https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/

wxGlade is a GUI builder for wxPython/wxWidgets.
Revision 0.8 is a major change. If you have evaluated previous
versions, please give 0.8 a try.

[

  ](https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/)
  A snapshot of the included documentation is also available here:

http://wxglade.sourceforge.net/docs/index.html

Major changes compared to 0.7.x:

  • Support for wxPython Phoenix and Python 3
  • More consistent user interface.
  •       Rewritten documentation / tutorial and examples; the target
    
    audience includes people who are just starting with wxPython.
  •       Repeat feature (Ctrl-R and Ctrl-Y) to apply property
    
    change(s) to multiple widgets
  • new Menu and Toolbar editors
  • support for GridBagSizer

Generated Code:

  • bind menu handlers without the need for user-defined IDs
  • default file encoding is now UTF-8

Internal:

  •       very major refactoring of property handling, code generation
    
    and sizers
  • reformatted code and comments to be more compact
  • always use DestroyLater to avoid crashes
  •       less redundant calls to widget.Show() to reduce display
    
    errors
  • better handling of size changes due to fonts
  • refactored testing

The changes from the last beta versions:

  • some bug fixes

  • examples for Custom Widget updated and documented:

        matplotlib, html, html2, py shell, SpeedMeter
    Especially the Matplotlib examples should be very useful if
    

you’re implementing data analysis applications.

The project repository is now on GitHub: https://github.com/wxGlade/wxGlade

The bug tracker is here: https://github.com/wxGlade/wxGlade/issues
(It’s also linked from the help menu.)

The wxGlade mailing list: https://sourceforge.net/p/wxglade/mailman/wxglade-general/

The plans for 0.9:

  •     change user interface (combine Palette, Tree and Properties
    
    windows)
  •     support events from the base classes and the addition of any
    
    event type as text
  • code properties: use stc and resize dynamically
  • toolbar and maybe menu editor: add Drop target for images
  • Notebook: add context menu entries ‘add page’ / ‘remove page’
  •     option to remove all the BEGIN/END wxGlade comments in the
    
    generated code (only with overwrite True)
  •     lib.buttons (feature request #45 Add support for generic
    
    buttons)
  •     Button: support more images (for normal, disabled, pressed,
    
    focus, current)
  • WrapSizer, maybe also StdDialogButtonSizer

Regards,

Dietmar

+1

Karsten

···

On Mon, Mar 26, 2018 at 10:20:45AM -0700, Robin Dunn wrote:

Congrats Dietmar!

--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

+1

Just a small remarq : the shebang in wxglade.py and wxglade.pyw prevent to run wxGlade with Python 3

I simply had to remove the version and all worked fine.

Regards

Xav’

···

On Monday, March 26, 2018 at 7:20:45 PM UTC+2, Robin Dunn wrote:

Congrats Dietmar!

Robin

Thanks for the info. I'm not using the shebang mechanism, so I did not notice.

I will change to 3 with one of the next releases. Starting with "python3 wxglade.py" should work, though.

Regards,

Dietmar

···

On 3/28/2018 4:45 PM, Xaviou wrote:

Just a small remarq : the shebang in wxglade.py and wxglade.pyw prevent to run wxGlade with Python 3
I simply had to remove the version and all worked fine.

Hi
Perhaps not specifying the version should be better : it will use the default installed python version

#!/usr/bin/env python

instead of

#!/usr/bin/env python2

(it worked for me)

Regards

Xav’

···

On Wednesday, March 28, 2018 at 5:30:20 PM UTC+2, Dietmar Schwertberger wrote:

On 3/28/2018 4:45 PM, Xaviou wrote:

Just a small remarq : the shebang in wxglade.py and wxglade.pyw
prevent to run wxGlade with Python 3

I simply had to remove the version and all worked fine.

Thanks for the info. I’m not using the shebang mechanism, so I did not
notice.

I will change to 3 with one of the next releases. Starting with “python3
wxglade.py” should work, though.

Regards,

Dietmar

Xav',

   Two observations from here: 1) I have both Python2 and Python3 installed
because some applcations require Python2; and 2) the new wxGlade requires
wxPython-4.0.1 to start with Python3. I'm having issues building
wxPython-4.0.1 so wxGlade loads only when started with Python2.

Rich

···

On Wed, 28 Mar 2018, Xaviou wrote:

Perhaps not specifying the version should be better : it will use the
default installed python version
*#!/usr/bin/env python*
instead of
*#!/usr/bin/env python2*
(it worked for me)

Hi.
I only have Python 3.6 on Windows 10 and wxGlade runs fine with the latest wxPython snapshot build installed from wheels :

I did not test under Linux (Debian Stretch) yet (I’ll try ASAP to give feedback)

Regards

Xav’

···

2018-03-28 18:19 GMT+02:00 Rich Shepard rshepard@appl-ecosys.com:

On Wed, 28 Mar 2018, Xaviou wrote:

Perhaps not specifying the version should be better : it will use the

default installed python version

#!/usr/bin/env python

instead of

#!/usr/bin/env python2

(it worked for me)

Xav’,

Two observations from here: 1) I have both Python2 and Python3 installed

because some applcations require Python2; and 2) the new wxGlade requires

wxPython-4.0.1 to start with Python3. I’m having issues building

wxPython-4.0.1 so wxGlade loads only when started with Python2.

Rich

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/0x9V03iOV00/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Hi, it sound nice, I’ll give it a try.

Thanks to your effort

···

El lunes, 26 de marzo de 2018, 5:24:33 (UTC-5), Dietmar Schwertberger escribió:

Hi!

  I'm pleased to announce the availability of wxGlade revision

0.8.0 from the download page
https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/

wxGlade is a GUI builder for wxPython/wxWidgets.
Revision 0.8 is a major change. If you have evaluated previous
versions, please give 0.8 a try.

[

  ](https://sourceforge.net/projects/wxglade/files/wxglade/0.8.0/)
  A snapshot of the included documentation is also available here:

http://wxglade.sourceforge.net/docs/index.html

Major changes compared to 0.7.x:

  • Support for wxPython Phoenix and Python 3
  • More consistent user interface.
  •       Rewritten documentation / tutorial and examples; the target
    
    audience includes people who are just starting with wxPython.
  •       Repeat feature (Ctrl-R and Ctrl-Y) to apply property
    
    change(s) to multiple widgets
  • new Menu and Toolbar editors
  • support for GridBagSizer

Generated Code:

  • bind menu handlers without the need for user-defined IDs
  • default file encoding is now UTF-8

Internal:

  •       very major refactoring of property handling, code generation
    
    and sizers
  • reformatted code and comments to be more compact
  • always use DestroyLater to avoid crashes
  •       less redundant calls to widget.Show() to reduce display
    
    errors
  • better handling of size changes due to fonts
  • refactored testing

The changes from the last beta versions:

  • some bug fixes

  • examples for Custom Widget updated and documented:

        matplotlib, html, html2, py shell, SpeedMeter
    Especially the Matplotlib examples should be very useful if
    

you’re implementing data analysis applications.

The project repository is now on GitHub: https://github.com/wxGlade/wxGlade

The bug tracker is here: https://github.com/wxGlade/wxGlade/issues
(It’s also linked from the help menu.)

The wxGlade mailing list: https://sourceforge.net/p/wxglade/mailman/wxglade-general/

The plans for 0.9:

  •     change user interface (combine Palette, Tree and Properties
    
    windows)
  •     support events from the base classes and the addition of any
    
    event type as text
  • code properties: use stc and resize dynamically
  • toolbar and maybe menu editor: add Drop target for images
  • Notebook: add context menu entries ‘add page’ / ‘remove page’
  •     option to remove all the BEGIN/END wxGlade comments in the
    
    generated code (only with overwrite True)
  •     lib.buttons (feature request #45 Add support for generic
    
    buttons)
  •     Button: support more images (for normal, disabled, pressed,
    
    focus, current)
  • WrapSizer, maybe also StdDialogButtonSizer

Regards,

Dietmar

Hi, this new study made me very happy. And there are thousands of users who are rejoicing like me.

We will fix the “accessibility” areas of your claim. There are many areas without labels. Screen readers can not detect them. Some checkboxes and edit fields are unlabeled.

Buttons, text fields … I think we need to drag them into a frame we created. Unfortunately, the blind can not use the mouse. You need to define keyboard shortcuts for this and develop other methods.

I apologize if I could not; I did not have a chance to fully investigate.

Many people will design GUI with this tool. This is so beautiful. I think that the GUIs created can be scored for “accessibility” and can be shown to the developer. In this way, many people become sensitive.

If you need support, https://www.nvaccess.org will help you.