What is MUI & Reaction all about after all?

[sexton]

Hi,

Does anyone know what does MUI really do?. Isn't it something like Java's Swing in the sense that it provides propietary widgets by rendering "pixel by pixel" non native stuff?. In that case, what is the way of programming in which you ASK the OS to draw the widgets for you as using windows.h in Windows 95? That way, in the future, your widgets may look different without breaking compatibility.

Thanks in advance for your answers.

[downix]

I don't know ReAction, so I can't comment there

But I know a bit about MUI.  It's an object-oriented user interface solution.  Not just the widgets, but *how* a window is drawn can be handled by MUI.  it's flexible, and turns a desktop into an object-oriented solution allowing for future expantion without breaking existing code.  Think OS/2 or BeOS here.

[FluffyMcDeath]

Ya know, that's a hard question. Both ReAction and MUI are ways to draw UIs with clickable buttons, lists, widgets, all the standard stuff, and they both do it by "drawing" the pixels of course, and since ReAction is the OS set of tools for drawing these things, then that is the OS way of doing things, but if OS4 is provided with both ReAction and MUI then MUI will also be the OS way of doing things.

MUI is pretty configurable so that you can change the look of the UI for all MUI progs you use, but so is reaction (but to a lesser extent). ReAction has fewer gadgets defined as well, but that is probably because MUI has always existed outside of the OS, and therefore people have felt freer about making new gadgets for it than they have with the OS gadget system.

ReAction builds on Boopsi, so it too is object oriented.

[iamaboringperson]

in the case of mui:

application: i want to open a window
mui: done
application: i want a button
mui: ok
application: now tell me when the user hits it
mui: will do

in the case of ReAction just replace mui: above with ReAction:

simple eh?