Quote:

What's left, Feeln?

Dammy

Quote:

I had to do some change in zune.library and let me tell you I am not impressed by the things I have seen of the MUI architecture. I would not mind MUI being replaced by a better framework.

greets,
Staf.

@Donar

of course! AROS official GUI toolkit is Zune. But having access to ClassAct apps would still be nice! Or do you think we should delete the old gadtools.library?

I do not think we need a second GUI clone/standard. As for KHTML - we should get a AROS Browser with a Zune GUI at some time...

Quote:

I don't think so, as MUI is not specific to MorphOS. But of course most of them prefer using MUI over Reaction.

Quote:

Well, some OS4 applications already work with ClassAct, some require at least Reaction (OS 3.9). Some need additonal classes introduced with OS4.
It's true that there are not many OS4 only programs that a MOS user might desire. But which applications fulfill this varies depending on the needs of a user. There are some interesting programs. The next new one appearing might require latest Reaction.
If an OS4 developer wants to port his application to MOS he doesn't want to switch GUI for this. The number of programers having access to OS4 AND MOS at the same time will surely increase, now as OS4 for Classic is available
I think increasing compatibility between different incarnations of the Amiga Spirit (OS3,OS4,MOS,AROS,p.OS :>) is definitely desirable.

An application I'd like to see on MOS is MindSpace. It works, but slowly. And there are issues with refreshing the map area which make it nearly unusable. Taht could be a problem with Reaction.

Regarding TuneNet: Are you sure that it works with the latest *publically* available version of OS4Emu ?

@Itix

yeah! sorry! I meant AmiFTP.

Quote:

Are you sure you dont mean AmiFTP?

Quote:

I doubt. To many MorphOS users reason to choose MorphOS was MUI.

Native Reaction could improve OS4Emu compatibility but generally speaking ClassAct from Aminet seems to be sufficient. I.e. tunenet works with ClassAct just fine and I dont know any other major Reaction based application for OS4 (which dont exist on other platforms already).

I have looked more into Reaction.

I think that an even better start could be reimplementing Bevel/Label images as Button.gadget seems to depend on it. Of course also Button.gadget could be implemented in the beggining as it will probably raise your mood sooner.

ClassAct/Reaction methods/atributes can be added directly to the sources of AROS button.gadget.

If somebody wants to see the sources of some Reaction classes he or she may take a look at the following files:
http://aminet.net/package/dev/lib/ExtrasLib
http://aminet.net/package/dev/gui/MR_Classes


----------------------------------------------------------
For a bounty I would suggest something like this:
-Create a ClassAct/Reaction compatible toolkit library
-Most ClassAct/Reaction examples must compile without major changes (just minor changes to make it 64bit compatible and allow aros compilation will be allowed).

The developer could choose one of these two options:
-An AmigaOS 3.0/3.1 m68k version will be required as proof of binary compatibility
-A port of an example application to choose between AmFTP, AWeb and ClassAction compiled with the new Toolkit must be provided as proof of API compatibility.

---------------------------------------------------------

-edit-
I am not sure about a wrapper being a good idea because that could cause compatibility problems and we are just trying to increase AROS compatibility to run more software, not to unify the amiga toolkit library world. It won't be advised to develop new ClassAct/Reaction apps and Zune should be used instead...

I think that the toolkit could try to use some MUI features like preferences (textures, gadgets, skins,...) but I don't think making a wrapper is a good idea because when you create a Reaction GUI sometimes you make things in a more primitive/lowlevel way than MUI. E.g. you refresh some groups manually and the event loop is quite primitive compared to MUI. Even if it could be done in MUI the result probably wouldn't be desirable.

I think that reading the MUI/Zune preferences (optionally) to keep the cosmetics consistent may be enough.

So if we focus on ClassAct wrapper, we could use a actual bounty description from someone. I wasn't planning on throwing any more money on new bounties till Summer, but I may break my plans for this one.

Dammy
TeamAROS