MUI is perhaps the only valid API for UI which identify the Amiga out of Amiga community: who has used AmigaOS between 1993 and 2001 (when Amiga community was very powerful and was able to mantain in life our platform) knows all most useful Amiga applications were written in MUI and old developers remember how was fun and easy to write a program with MUI.
Who has left Amiga community was inspired by MUI experience to written many projects which are used in other platforms. When OS3.5 was annunced without MUI many developers left Amiga community because for them MUI was an important part of the Amiga experience.
So we can state MUI is an historical piece of AmigaOS like IPC ARexx and Datatypes concepts.
MUI APIs are avaiable in all Amiga flavours in different forms and versions:
OS3 : MUI3.8
OS4 : MUI3.9
Mos : MUI4
AROS: Zune (MUI3.8 compatible)
However, excluding MorphOS, MUI is a shareware framework, which in form of not register software doesn't give to user some of its features (extreme personalization of UI).
Zune is an open source implementation of MUI which is included in AROS project, it is compatible with MUI3.8 APIs and it has some features which are missed on MUI3.8. In the latest years Zune was ported from AROS to AmigaOS3, and so the only MUI registered features and Zune modern features can be used on OS3 for free.
Zune is even ready to be ported on OS4.
Many OS4/AROS/OS3 users are interested to have software like OWB-MOS and Ambient on their systems, but these software use new API of MUI4, so the better way to have these software on OS4/AROS/OS3 would be to have MUI4 on these systems.
However MUI author seems not to be interested to do a port of his latest framework version to OS4/AROS/OS3, so only MorphOS users can use these software and only MorphOS developers can use MUI4 for their software.
We want create a bounty to make Zune MUI4 compatible. In a similar form Zune can give to their users software like OWB-MorphOS and Ambient with few work on system where Zune is avaiable.
To third parts developers a Zune MUI4 compatible would give an easy way to write their software in a easy portable way between different Amiga flavours without too much work because they could use a only powerful framework API instead to workaround different behaviours of MUI3.8/MUI3.9/Zune.
So we have a first draft of a bounty "To make Zune MUI4 compatible":
FIRST STEP
Quote:
@saimon69
Debug current Zune codebase and,where possible, improve existing MUI 3.x
compatibility adding missing functions and fixing current broken features,
Quote:
@Ball000
1. Port Fab1's OWB. Seems it mainly means "Implement in Zune MUI4 functions needed to compile Fab1's OWB" (of course the port itself would need some other work (improve CAIRO?), so this bounty can't be only Zune-related);
Quote:
@Fab
That would indeed be the most practical way. I don't think i'd like to have tons of "duplicated" code in OWB just because previous MUI versions didn't support methods for construction/display and co, for instance.
SECOND STEP
Quote:
@Ball000
2. Implement MUI4 functions needed to compile Ambient (but yet again, the port of Ambient will need other works to be done, especially system functions, as Ambient relies on some specific improvements of MorphOS);
Quote:
@bernd_afa
Sebastian Bauer have zune port to run on OS4.there are some os4 ifdefs in.
Quote:
@ShInKurO
This Zune enhancement would be very good even for an eventual port of Ambient on AROS/OS3/OS4 and to make Ambient in this way what DirectoryOpus Magellan was for AmigaOS some years ago.
THIRD STEP
Quote:
@Ball000
3. Implement remaining functions of MUI4 in Zune.
Other discussions about this topic are:
http://amigaworld.net/modules/newbb/v ... p?topic_id=32260&forum=15http://aros-exec.org/modules/newbb/vi ... t_id=45752#forumpost45752