Reaction vs MUI (as what concerns the API)

[matthey]

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.

[matthey]

In MorphOS PSI uses the standard screen mode widget, the very same widget what screen requester is using ;-)

Do you happen to have a screenshot from Reaction screenmode widget?

PSI doesn't use the standard asl.library screen mode requester under AmigaOS 3.x. Reaction leaves it up to the programmer but most use the standard screen mode requester which follows the Amiga User Interface Style Guide. Maybe MOS does something different but then it isn't AmigaOS and has redefined the user interface also. I prefer the AmigaOS and Reaction way as it's straight forward and less cumbersome to open a screen.

@Tcheko
PSI takes about 5 seconds to open it's window with my 68060@75MHz. That's just sad. Enough said.

[matthey]

@Tcheko
I apologize. I tried again and PSI came up nearly instantly this time. It must have been that CPU intensive task I had in the background slowing things down :O. MUI does seem to be slower although a fast processor makes it less of an issue.

Problem is standard requester is not always what you want. You may wish to embed requester into your window or have custom options there.

True. The MUI way is powerful but it is also different from the standard AmigaOS user interface, slower and less obvious. A good example is in this thread...

http://www.amiga.org/forums/showthread.php?t=56505

Take a file browser as an example. With MUI's filepanel class you can attach standard file requester features into your software without using ASL requesters.

I don't see anything wrong with asl.library requesters. They are somewhat limiting in order to have a standard user interface.

If you use GadTools you have to build your own file panel using its crappy listview gadget.

Gadtools in primitive and was only meant to suffice until boopsi/Reaction became more powerful. Boopsi/Reaction/Datatypes is good but never got finished.