Zune for all platforms

[kamelito]

The "common standard" already is MUI, it will never be Zune. Current version is MUI4, which is an *integrated component* of MorphOS (an OS component required for MorphOS to run, older versions won't work). MUI4 sets the standard, the agenda, if you want a common denominator. On OS4 and AmigaOS, MUI 3.8/3.9 is available as add-on package/bundle. A lot of work has recently been put into bringing some MUI4 features into the OS4 version of MUI3.9, hence it's possible to port Fab's excellent web browser Odyssey, and also other MorphOS stuff, to OS4.

I think this is the path to go for AROS - aim for making Zune MUI4 compatible instead of expecting people to go back and satisfy with a MUI3.8 (i.e. MorphOS 1.0 IIRC) level API. There is a reason to why development goes *forward*, and that's because it brings a lot of new goodies to the table! And once you tastes the sweet's, there is no going back!

I hope that MUI4 is more updated than Ambient, latest commit for this one is August 2010.
Kamel
PS Don't shoot me I'm trying to buy a Powerbook for MOS 3

[kamelito]

I expect Zune developers to have some kind of list like this as their roadmap towards MUI4? If they haven't mapped out the differences between the MUI versions and current Zune, they ought to be quite lost. Maybe they could post it on the bounty page? Would also be a good way of doing progress reports to show how Zune is developing over time...

I suppose this is a starting point...

http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=5805&forum=4&post_id=54683#forumpost54683

[kamelito]

While you could prepare a Zune that'd run alongside MUI on MorphOS, you would indeed need to compile all apps for it with modified headers so that all classes would use a different name (a prefix, like some "non-coder" here suggested could work, but not in the compiler but in headers obviously This of course means that you cannot compile a single binary that'd run using Zune or MUI depending on what's installed. You cannot replace MUI with Zune on MorphOS because MorphOS (for instance, intuition.library) relies on its internals heavily (structures, private methods, attributes, etc). Since those methods are, well, private, they wouldn't be available in Zune. And what would be the point of having two libraries alongside doing virtually the same (but Zune doing obviously less than MUI 4.0 and being poorly integrated)?

In the Morphos site "and AROS for providing the source base of many components, including but not limited to DOS, Intuition, GadTools, Locale, Commodities."

Then Morphos devs said that they gave back source code to Aros. So if intuition rely on MUI internals on Morphos then its not a problem as you gave back the corrected/modified source code to Aros, or Am I missing something?

Kamel

[kamelito]

See APL section 1.9.

I'm no good at licence terms, but is this not more related to the section below ?
Kamel
3.2. Availability of Source Code.

[kamelito]

@kamelito


The MorphOS devs haven't violated the terms of the APL. They aren't required to share every change they made to the AROS code, APL is not like a GPL licence in this way.

@all
Can we get back to discussing the bounty please. Who is interested in donating (if not straight away, then later)? If you're not interested in the Phase 1 bounty, would you be interested in supporting later Zune Fix bounties?
http://www.power2people.org/projects/profile/61

I already donated 20 bucks. If I was a good developer in need of money, I'll be waiting until the money from the zune enhancement bounty is moved to the new bounty. I suppose that the Power2P guy do have the email addresses of the one who haven't moved their money yet, so why not asked them to send a mail explaining all that?

Kamel
PS a bit off topic, MUI4 seems great because of its OOP roots but it's too bad that the entire system is not done that way a bit like NextStep or Cocoa API any plans about this? A bit more abastraction would make development shorter, MUI is only one piece of the puzzle.
PSS I didn't say they violate AROS APL I was just trying to understand it.

[kamelito]

In my opinion, starting with the MUI3.8 target was like asking folks to drop back to kickstart/workbench 2.04 standards (limited AGA/RTG/locale support, etc.)

If you want to gain support of _all_ Amiga-like platforms for an improved Zune, you should try to offer something that they don't already have.   If you're directly targeting MUI4, you might expect support from the communities that don't have that level of MUI API compatibility available to their platform.

One could ask app developers what they think should be in a hypothetical MUI 5.x, feature list and then take that info along with examining the currently available MUI3.9 and MUI4 implementations to shape the Zune development plan.

 Nobody wanted to accept the original bounty because it was a lot of work for say maybe not enough money. (even if money is not everything here). The decision was taken (see aros-exec.org forums) to create a multiple phases bounty. The first one aimed at 3.8 compatibility. The others will take care of MUI 4 and more.   Kamel