Welcome, Guest. Please login or register.

Author Topic: Reaction vs MUI (as what concerns the API)  (Read 39266 times)

Description:

0 Members and 5 Guests are viewing this topic.

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Reaction vs MUI (as what concerns the API)
« on: February 12, 2011, 04:35:14 PM »
Not at the user level so please no flamming wars :) I decided I'll take some time to slowly learn one of the APIs and would like advice on advantages/disadvantages of both regarding:
- User ability to make your own Boopsi objects and mix them with Reaction/MUI's own ones.
- Ability to modify Reaction/MUI's own objects to add features / behavious, just like you can do with subclassing a Boopsi object
- Compatiblity regarding AOS4/MOS/Classic. Think MUI is ahead on this one but the users had to buy the licence to run MUI on OS4 or something and it wasn't granted that development would continue. My memory is probably failing on this one but again, please no flame wars, just present the facts.

Thanks!
José
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #1 on: February 15, 2011, 05:58:32 PM »
I like brunettes don't know why... :)

Regarding Reaction the biggest stumble I've found so far is that there isn't much documentation! The original ClassAct release on Aminet has some stuff, also the NDK3.9 has descriptions on each class and there are some examples on the DevCD. Should be enouph. There's also a PDF tutorial somone did wich seems more oriented towards OS4 but should be usefull.
MUI docs on the contrary seem to be very good.
I've only read part of the intro on the ClassAct release and it seems every class on Reaction/ClassAct is a boopsi object, wich makes it usable from any other Boopsi object. Someone above mentioned that to use Boopsi classes on MUI you have to encapsulate them in a MUI class so maybe the result is the same, does it work the other way around too, i.e. can you call a MUI class method from a standard Boopsi object ?

Pah, I guess the best way is try both. I might even do some benchmark program thing.
Granted I expect each one to have it's advantages/disadvantages depending on each context.

BTW, regarding complex GUIs with Reaction, I've recently read the Boopsi chapter on the RKRMs and it seems to me that a lot of people jumped into MUI/Reaction without knowing Boopsi, I think if you know how interconnection Boopsi classes work you can do very complex GUIS pretty straightforward, maybe it takes a bit more code to set up your connection objects but it didn't seem that much. And it's very flexible.

Anyway, when I get the time I'm gonna try both that's for sure...
« Last Edit: February 15, 2011, 06:03:58 PM by Jose »
\\"We made Amiga, they {bleep}ed it up\\"