MUI 5.0-2016R3 for AmigaOS4/PPC and AmigaOS3/m68k released

[Pat the Cat]

IIRC, MUI is vital for some applications.

I always found it depended on the application, to a certain extent, as well as the MUI core.

Have things changed a lot with respect to that?

[Pat the Cat]

OK, OK. No need to shout.

MUI was always a bit problematic to get right, and somewhat processor dependent, and I hadn't expected that to change much... but it's nice that the people with the wild horses for processors and sideways crazier modern solutions are being allowed to gallop.

Occasionally getting thrown out of the saddle, true, but that's always the case with bleeding edge technology.

[Pat the Cat]

I get super frustrated with these posts about "a new version". They pop up every few months. Almost as often as some poor schmuck, freshly back to the Amiga community after decades away, posts about all the problems they're having. They think "ooh, I'll just download the latest version", not knowing how many issues it causes. IMHO every post about "a new version" should include a warning about this. Or at least give people a heads up, you know?

Nod nod. Same old story, same old story. Gets you down. Gets anyone down, we've all got our breaking points.

That's why I asked, guvnor. The only real constant is change. Everything changes, in time.

Thing is, a true noob is going to google info and downloads for MUI anyway, to find out what it's for, why they might want it.

Why not have stickies for noobs? Might help reduce the issue, anyway. Might help with passion overflow issues and blood pressure, too.

[Pat the Cat]

Maybe it could also mention about MUI 3.8, which works on classic systems and which is enough for classic software, if this disclaimer was for those who don't know what's going on and maybe think that MUI is MUI.

TBH I always thought MUI was a developer tool for people that couldn't actually code, but could wave a mouse and click occasionally. To the extent that if an app needed MUI, I just didn't bother with that tool. Quite a Luddite attitude to some, but... I guess I wasn't interested in a flash GUI that spent all it's time and resources looking pretty.

Then again, most people aren't like me, and do value attractive tools that actually let them be productive, in some way.

[Pat the Cat]

it doesn't mean it was for those who can't code, and  there wasn't mouse involved with the coding... I don't know where did  you get that

BOOPSI. The middle bit of that.

I have always associated OOP with waving a mouse pointer around and clicking sometimes. :confused:

Don't ask me why, I've forgotten exactly. Possibly in how I was taught  about that (OOP), or perhaps I played with the parent of MUI, as it  were. There were concepts around for things like hypertext at the time,  lot of dev tools for designing interfaces... I just recall Boopsi.

Or maybe it's a reference to Visual Basic or something like that. Unlikely, never even seen a screenshot, I think.

No,  I think I must have reviewed Boopsi at some point, or mentioned it as a  release. Whether it was commercial or started as an educational project  through the PD channels, if it was a public dev toolkit, I kind of HAD  to cover it, unless a previous issue of AF had. Probably stated as a  student project and got ported real quick (years) into the Dev chain,  but that was years before I / the magazine came across it.

Even  after the A500+ shipped to the stores, who bought advertising off us on a regular basis, I don't think we HAD a WB2.04 Amiga in the  office, until an A500+ was delivered. That was months after CBM switched from A500 to the A500+. The new machine went  straight to the games people to test compatibility of releases with, and  of course material for the Coverdisk could be tested too. God only  knows what happened to the floppies at the time. I don't think I even saw  them. I certainly didn't unpack the machine. So couldn't try jack to  test non-games really, on WB2.0. Didn't even have a 2.04 install disk, or any kind of CBM gear except stock Amigas, stock monitors. We had a Hitachi multisync to test flicker fixers on. Graphics card reviews were done out of the office, I never saw the hardware up close, except if it was in a packed in a box, arriving or departing.

I recall reviewing an A3000 and A4000 in turn, only to have them hurtling to another reviewer a few days later. (Kit either stayed or it travelled. You didn't argue with the people who sent it. You could be accused of stealing otherwise). Also hardware died sometimes and had to be cannibalized to maintain coverage. Even then. Issues like 1MB chip RAM compatibility, games compatibility, we tried our best to test for.

I think I got an A3000 and really experienced 2.04 in about 1993/94, on a multisync. Long time after Boopsi had entered the Dev chain "officially".