Reaction:
+ fast
+ small
+ expandable (boopsi objects)
+ integrated very well with AmigaOS
- not available on AROS
- not as many ready made custom classes or examples
MUI/Zune:
+ available on all Amiga like platforms
+ expandable (boopsi objects) with many available custom classes
+ very configurable
+ easy and fast to program
+ lots of documentation
- slow
- memory hog
- many different versions and classes make installation a pain
- user interface is non standard (e.g. PSI instead of standard screen mode requestor)
I prefer to use and look at Reaction. MUI is easier to program and powerful (more configurability and ready made custom classes). I hope that all Amiga platforms will support both at this point. I can't image doing without either.
MUI : Slow? Memory hog? Do you have any numbers?
To make some factual statement, we need to write a GUI benchmarking working on both ui framework : Reaction / MUI.
For example, how long does it take to MUI / Reaction to create a window with 1024 buttons (32 x 32 buttons grid) and release all resources. The window shall be opened and then closed and application exited.
The test should be run on the same hardware (let say a Pegasos2) and execution time measured from start to end of program.
Another version of the program that exit on window close button should be created. This version is for memory test:
- avail flush
- run <>nil: memtestprogram
- avail flush
Compare numbers.
This would give a raw and rough estimation about which one is the fastest (for buttons at least). MUI button should be set to something that looks like Reaction button.
I can write the MUI program test... if anyone feel writing the reaction one.
Both sources shall be published for comparison. No custom startup code allowed. The only allowed optimisation is using gcc -O3.