develooper Front page | perl.wxperl.users | Postings from January 2013

Re: wxGlade

Thread Previous | Thread Next
Johan Vromans
January 5, 2013 17:21
Re: wxGlade
Message ID:
> Wallace Winfrey <> writes:
>> Bottom-line: wxGlade felt clunky and rough around the edges, while
>> wxFormBuilder felt polished and more consistent. However, it's ultimately
>> an aesthetic choice. While it's true that it's easier to get Perl code from
>> wxGlade than the roundabout method I've described using Padre, I feel the
>> gains I get from designing my interfaces in wxFormBuilder over designing
>> them in wxGlade more than compensate for this.

I'm not as familiar with wxFormBuilder as with wxGlade but I was
wondering: How do you develop with wxFormBuilder generated code?

wxGlade uses protected regions, so you can generate code, adjust most of
the contents, change the design, re-generate and all your changes are
still there. This doesn't seem te be possible with wxFormBuilder
generated code.

Even if you take the approach to not touch the generated code and only
use it as base classes for yor own code then still I miss the ability to
have actions executed while forms are being constructed. For example, a
typical wxGlade form constructor has separate (hence overridable)
methods to set property values and handle layout issues. By overriding
the __set_properties method one can e.g. populate form fields from a
database before the form is layed out. How would you do this with
wxFormBuilder code?

Note that I'm not implying that wxGlade is better than wxFormBuilder or
vice versa, it is just something of interest when working with these
tools. Information like this could be interesting to put on the wiki.

-- Johan

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About