wxMax - A BlitzMax GUI Module

Miscellaneous Forums/Blitz Showcase/wxMax - A BlitzMax GUI Module

I am pleased to announce the release of wxMax v1.00, a wxWidgets language binding for BlitzMax.

After trying to use MaxGUI for long enough to do proper application development in BlitzMax, I gave up and decided to find something that worked. wxWidgets, although a bit big, turned out to be a good choice for a cross-platform GUI module.
It is customizable, the event model is excellent, and it just works :-)

It supports native UI controls, including multi-column list boxes, GDI drawing, printing, PDF generation, serial I/O, scintilla (editor), grid-style tables, and lots more.

It also ships with tutorials and samples.

* The official site
* Downloads Page

* wxmax_1_00_win32_bin.rar - Win32 src + binaries release (14.9 meg)

* Discussion Forum


If you are interested in serious Application development in BlitzMax, then wxMax is probably the easiest decision you could make.

I'm rolling out the other platform releases as I get round to them...

Feel free to post feedback.

:o)

This just might get me back to BMax. It's soooo much easier than using the original GUI system.

Thank you for sharing...

Barney

Can you use it like you would MaxGUI?
window=CreateFrame(....)
button=CreateButton(...,window)

Or does it have to be OO?

Looking forward to exploring this module. I really *hate* to moan straight away but I am going to air one gripe now I've compiled it... it totally takes over the 'Third Party Modules' list in the Home tab on the right of the IDE. Is there any way to organise the docs so that all the sub-modules are collapsed underneath the main (wx.wx?) entry? I really don't want to have to see that stuff if I'm not using the module (yup I know that sounds really picky, but there are well over one hundred of them!)

Other than that, WOOT! I'm going to have to go and read some tutorials now. The PDF stuff looks interesting...

Or does it have to be OO?

It is OOP I'm afraid. It follows the original API almost exactly, which is also OOP. The advantage to a matching API is that you can read a "How to program wxWidgets" guide/book of C++, and can create a BlitzMax version of the code that has the same structure.

For example, it's quite easy to use this book to learn wxMax, even though all the examples are in C++.


it totally takes over the 'Third Party Modules'

I know... sorry. At the moment, there's not much I can do about that. docmods will need some TLC in order sort it out, and I haven't had much time of late to be tweaking that too ;-)

Congrats Brucey, it's been 6 months to this point right?

Is this what Gtk uses?

Well done!

I really wish there would be one good GUI module and not different island solutions... :(

it's been 6 months to this point right?

12 months on August 20th ;-)

wxWidgets uses Gtk, on Linux, as its native renderer. (Like what Gnome sits on top of). wxWidgets is just a standardized crossplatform API... a bit like what MaxGUI tries to be - except that it's been in development for much longer, and has more developers working on it.

amazing job brucey... I just ran a svn update... is the svn version current?

Oer, 12 months on and off I hope. :)

Thanks for the info about Gtk.

I'll be making a point of trying wxMax out soon.

is the svn version current?

SVN is always more current than the latest release :-)