I'm sure there is at least 1 GUI module in the works as we speak (the B+ module), so I'm just waiting patiently... But I'd really like to see someone with a lot more gray matter than me come up with as near perfect a solution for this as possible. Some suggestions:
1) The BMax commands for creating GUI elements and receiving events, etc. should be the same on all supported platforms. Cross-platform portability is the main reason a lot of us bought Bmax, so catering to Windows only or Mac only will only split us apart!
2) The windows and other GUI elements themselves should be 'proper' native OS GUI elements, rather than Max-created elements. Some people may not agree with this (and maybe they have good reasons), but I think BMax will get a lot more respect if it does it this way. Plus, it will almost certainly be easier since most of the hard work has already been done by Microsoft, Apple or whoever!
3) Supporting OS-specific events, gadgets (sorry, that's what I call 'em), etc should also be possible, of course, through some clever means. Any ideas? Naturally, the features that ALL of the supported OSes share should be the common base. I could be wrong, but I'd guess that 90% or more of these features are shared already by these OSes. Afterall, are they not all event-driven pre-emptive multitasking operating systems that use graphical elements such as buttons, windows (Microsoft calls EVERYTHING in the gui a 'window' practically), menus, etc to interact with the user?
4) Along with the GUI module, I'd really like to see, of course, a Visual Designer (oops, I think that's PureBasic's area) or whatever GUI editor to top things off.
So far, I'm just having fun experimenting with BMax's 2D capabilites. But application programming is also on my mind, and BMax seems open enough to handle it with 'gusto' <crosses fingers>.
Russell
1) The BMax commands for creating GUI elements and receiving events, etc. should be the same on all supported platforms. Cross-platform portability is the main reason a lot of us bought Bmax, so catering to Windows only or Mac only will only split us apart!
2) The windows and other GUI elements themselves should be 'proper' native OS GUI elements, rather than Max-created elements. Some people may not agree with this (and maybe they have good reasons), but I think BMax will get a lot more respect if it does it this way. Plus, it will almost certainly be easier since most of the hard work has already been done by Microsoft, Apple or whoever!
3) Supporting OS-specific events, gadgets (sorry, that's what I call 'em), etc should also be possible, of course, through some clever means. Any ideas? Naturally, the features that ALL of the supported OSes share should be the common base. I could be wrong, but I'd guess that 90% or more of these features are shared already by these OSes. Afterall, are they not all event-driven pre-emptive multitasking operating systems that use graphical elements such as buttons, windows (Microsoft calls EVERYTHING in the gui a 'window' practically), menus, etc to interact with the user?
4) Along with the GUI module, I'd really like to see, of course, a Visual Designer (oops, I think that's PureBasic's area) or whatever GUI editor to top things off.
So far, I'm just having fun experimenting with BMax's 2D capabilites. But application programming is also on my mind, and BMax seems open enough to handle it with 'gusto' <crosses fingers>.
Russell