Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #14 from previous page: February 14, 2011, 06:40:05 PM »
Quote from: lsmart;615530
No, the event loop just gathers enough information to continue. The rest is done elsewhere. But you are obviously thinking that I have written Amiga software after 1995. But I did most of my Amiga development before that. And much of it wasn´t in C.


Then it changes quite lot.

Quote
I do adapt to language and font-size. Iconify wasn´t useful in my software and frankly I don´t know what snappshotting means in an Amiga application context. But I do know that there are a million great Amiga programms that don´t use MUI or Reaction.


Sure there are and I dont want to mockup that old software. Programmers did their best with tools they had available. But this was almost 20 years ago!
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #15 on: February 14, 2011, 06:41:30 PM »
Quote from: kolla;615544
http://aminet.net/package/dev/misc/AWNP_2-54 and you're all set.


Great, so I can install multifunction pipe on my Amiga 500. What now?
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #16 on: February 14, 2011, 07:15:20 PM »
Quote from: kolla;615553
Now you pass data through that pipe, to build GUIs and do whatever you like.


So, it seems ClassAct is not much use at all.
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #17 on: February 15, 2011, 06:47:11 PM »
Quote from: Jose;615740
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 ?


See this for BOOPSI objects in MUI.

It can not be done other way around (embedding MUI objects into Reaction GUI), mostly due to the notification system which does not exist in Reaction.
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: Reaction vs MUI (as what concerns the API)
« Reply #18 on: February 15, 2011, 07:04:08 PM »
Getting back to the topic (sorry we got carried far away to sideline) I think notification system is one of strong points in MUI API. You can add callback hooks and methods to events so you dont have to mess with this in your event loop. It also allows simple automation of events i.e. when user presses a button MUI could automatically window title for example.

Another difference in MUI is that you can define window or context menus as objects. You dont necessarily have to define static menu structure (but you can if you want to). They can be used to store attributes and they are part of notification system so menu selections can be automated just like everything else. You can expand and shrink menus simply by adding or removing objects from them.
My Amigas: A500, Mac Mini and PowerBook