Quote:

Would be good if AROS and Morphos could benefit from this also but as it will be Reaction based I don't know how much use it will be

I don't know much about WxWidgets, but I would almost bet that you will end up with a mess if you are trying to map it to Reaction or Intuition boopsi gadgets in general. Because that's a completely different way to handle GUIs compared to just about all other GUIs other there which all run in app task(s) and not partly (input handling, sometimes rendering) in some system task (input.device) with a lot of limitations: stack usage, spend to much time there and you get short freezes (mouse stutter), cannot use functions which require a Process, what about timers, etc.?

And apps using WxWidgets certainly have some way to define their own GUI classes, so even if you turn all standard GUI classes provided by WxWidgets into Boopsi Classes with all the required hacks and stuff (for things which are not possible/too slow in input.device task, use hacks to handle it (MUI like) in app task, or use helper sub processes, ...) what about the custom classes used by the apps?

Quote:

Here is a work-in-progress screenshot of AE5.1 with MIDI sequencing:

Looks cool!

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

@DaveAE

Seems very interesting!

_________________
A1200/020+68882 - 6 MB RAM - AmigaOS 3.0

Home Recording Audio

@Georg

Quote:

I don't know much about WxWidgets, but I would almost bet that you will end up with a mess if you are trying to map it to Reaction or Intuition boopsi gadgets in general. Because that's a completely different way to handle GUIs compared to just about all other GUIs other there which all run in app task(s) and not partly (input handling, sometimes rendering) in some system task (input.device) with a lot of limitations: stack usage, spend to much time there and you get short freezes (mouse stutter), cannot use functions which require a Process, what about timers, etc.?

WxWidgets is designed as a wrapper for whatever the native GUI system is. We'll have to see, but I think that it should be okay.

Quote:

And apps using WxWidgets certainly have some way to define their own GUI classes, so even if you turn all standard GUI classes provided by WxWidgets into Boopsi Classes with all the required hacks and stuff (for things which are not possible/too slow in input.device task, use hacks to handle it (MUI like) in app task, or use helper sub processes, ...) what about the custom classes used by the apps?

It should be possible to create a wrapper that allows wxWidgets custom gadgets to be custom ReAction gadgets. In fact, that's the first thing that I would do if I were involved, since this would make wxWidgets immediately usable, even though the native look and feel wouldn't be there yet.

Hans

Last edited by Hans on 29-May-2009 at 09:30 PM.

_________________
Join the Kea Campus - upgrade your skills; support my work; enjoy the Amiga corner.
https://keasigmadelta.com/ - see more of my work

Any news about WxWidgets?

http://www.amigabounty.net/?function=viewproject&projectid=30

_________________
AmigaOS on Google+
AmigaOS on Facebook