Welcome, Guest. Please login or register.

Author Topic: MUI 4.0-2016R2 for AmigaOS4/PPC and AmigaOS3/m68k released  (Read 3490 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline cgutjahr

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 697
  • Country: 00
    • Show all replies
Quote from: Dandy;810663
Fine that old keyfiles work.
Why can the "MUI for AmigaOS"-development team not generate and sell new keyfiles for their piece of work

The "MUI for AmigaOS" team 'accidentally' released a version that did no longer require a keyfile. I don't think Mr. Stuntz is too keen on letting them handle registrations.

Quote

AFAIR, you needed a license key to be able to use MUI 3.8 for GUI development.

No, you only need a keyfile if you want to use MUI to its full extent, developing for it never was a problem.

You do have to pay licensing fees though, if you're selling a commercial application that requires MUI. That's why there's so few commercial releases using MUI (Drawstudio, Ibrowse...?) and lots of 'Shareware' releases.

Quote

I deem it 'higher nonsense' to offer a new, updated piece of software that requires license keys of an old and no longer supported version, that can't be bought anymore...

Agreed. Not to mention that AmigaOS has its very own GUI system which could use some attention aswell.

Jens and Thore are pushing MUI, because it benefits their cross-plattform approach (YAM...). For AmigaOS users (and, to a lesser extent, MorphOS and AROS people) this simply means that the amount of applications not properly adopted to OS4 (i.e. using Ringhio and application.library, OS4's support for translating codepages into the native ISO-8859 etc.) is going to increase.

It's like 1995/1996 all over again: no leadership, no strategy, no money - the obvious result is bedroom coders doing whatever they feel like doing.
 

Offline cgutjahr

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 697
  • Country: 00
    • Show all replies
Re: MUI 4.0-2016R2 for AmigaOS4/PPC and AmigaOS3/m68k released
« Reply #1 on: July 06, 2016, 10:24:21 PM »
Quote from: itix;810683

tl;dr CA/RA issues are not so much in the user side but its developer interface need streamlining.

Like I said, "it needs work". A priority for both the dev team and the users should be the/a native GUI system. What that would be, what it would look like etc. is up for debate - the only thing that's certain is that it can never be MUI, as MUI's development is controlled by the main competitor.

Quote

The cross platform approach does not prevent using vendor specific extensions.

Like Reaction? ;)

Quote

And there is multiplatform codesets.library that takes an advantage of some/all OS4 and MorphOS codepage translations.

And if one of those systems gets actual UTF support, YAM users will be left behind... Same goes for a new scripting interface, embedded HTML, PDF or video rendering, etc. I remember a MorphOS only SimpleMail fork created for pretty much that reason.

My point is: the complete list of all noteworthy cross-plattform Amiga applications looks like this: YAM and Odyssey - with the latter's development slowing down to a crawl, now that Fab abandoned it. There was never a better time to just forgot about compatibility with other Amiga solutions, simply because all Amiga solutions are pretty much dead as far as application development is concerned. If one of the solutions will ever get in better shape again - cross-platform applications will automatically fall behind.

Quote

Remember when computing was fun ;^)

Lol, good point. At least we still had BBS meetings back then, and actual news to dicsuss at these meetings.