Linked by Thom Holwerda on Fri 4th Jun 2010 11:39 UTC, submitted by Amix
Morphos And the MorphOS team continues to expand their hardware support. They released MorphOS version 2.5 today, which adds support for Apple's eMac computers (the 1.25Ghz models, the 1.42 models have not yet been tested). Of course, there's also a whole load of fixes and improvements, too.
Thread beginning with comment 428207
To view parent comment, click here.
To read all comments associated with this story, please click here.
mrAmiga500
Member since:
2009-03-20

I'm a long time Amiga user (using 16Mhz A3000 to post this), but I found that many of the "Amiga things" I've become accustomed to are not part of the OS at all, but third-party add-ons, programs and hacks that are Amiga-only. When I start with a basic Amiga setup, I'm a bit lost until I can get my favourite filemanager, tools, hacks, etc. loaded up. I can certainly understand a newcomer feeling lost. It takes time to get used to different ways of doing things and time to get programs and utilities that work the way you want. Luckily, Amiga has always been easy to hack and change.

I've always wanted to try MorphOS and I probably will when they support PowerMac G4. I'm sure even I will feel a bit lost until I can get it set up similar to the way my other Amigas are.

Reply Parent Score: 1

Kroc Member since:
2005-11-10

MorphOS, like all operating systems, expects me to understand invisible and intangible background processes that change the state of the computer according to commands I execute. Take for example, the cipboard. We take this for granted, but it is an awful piece of UI if there ever was one. You click copy and *nothing happens*. You are expected to understand what is happening within the black box. There’s nothing tangible here with which a new user could expect to understand "copy". When you photocopy something, you get the result straight away. Not when you move to another photocopier and punch a button to get your copy from the previous machine.

The problem I have found with MorphOS—for which it cannot be blamed—is that as it has a small team of developers behind it who are all knowledgeable in the ways of the Amiga and they design and implement the OS according to their knowledge of this black box. As an outsider, where do I fit into this equation? Should I be forced to learn how the black box behaves when I prod it just because that’s how everybody before has done it and I shouldn’t complain; or shouldn’t this be redesigned so that it’s easier to understand to begin with.

How can I review something that is asking me to adopt it as a full time platform, suffer all the difficulty learning it just so that I can be "fair" about it. I can’t. All I can summise is that it is a technical achievement for the makers, it presents itself well and it has a varied and interesting community. I was going to try adopt the OS for a month but I couldn’t wrangle a free licence out of the development team so it put paid to that idea and I can’t get more out of the OS than booting it up and tinkering with it—which is neither fair or realistic when it comes to reviewing. What I did find was an awful lot of bugs—genuinely broken stuff, not only ignorance on my part. This is why I look forward to trying the new version to see what changed.

I would only want to write something if I could do the OS justice. If anything I am more inclined to write about the issues of newcomers to alternative OSes than MorphOS itself specifically.

Reply Parent Score: 1

Neolander Member since:
2010-03-08

Take for example, the cipboard. We take this for granted, but it is an awful piece of UI if there ever was one. You click copy and *nothing happens*. You are expected to understand what is happening within the black box.

How could it be done otherwise without a visually bloated interface which displays endless amount of popups like "I copied something !", "I cancelled something !", "Oh, look, I just found a Wi-Fi network around ! Be sure to try it out !" ? Such a popup is fine for something which happens rarely, not for something which is done everyday.

You say that nothing happened, however I see that...
-> The "copy" link got highlighted when the mouse was hovering it.
-> When I clicked it, as soon as the command was acknowledged, the OS made the popup menu disappear as visual feedback.

In my opinion, for a function as commonly used as copy and paste, it is safe to assume that the user will take a week to get used to it, if he/she is going to use this feature for 10 years long.

My sqrt(2) ct however...

Reply Parent Score: 2

AmigaRobbo Member since:
2005-11-15

So you want a windows (95) clone? For every single 'alternative' OS?

If so count me out of your great dream.

Reply Parent Score: 2

Raffaele Member since:
2005-11-12

MorphOS, like all operating systems, expects me to understand invisible and intangible background processes that change the state of the computer according to commands I execute. Take for example, the cipboard. We take this for granted, but it is an awful piece of UI if there ever was one. You click copy and *nothing happens*. You are expected to understand what is happening within the black box. There’s nothing tangible here with which a new user could expect to understand "copy". When you photocopy something, you get the result straight away. Not when you move to another photocopier and punch a button to get your copy from the previous machine.


Pardon me but I am not capable to see your point.

What is the difficult you find in copy function?

Is the icon remaining the same and not becoming ghosted and then you are unable to understand you clicked and copied it in clipboards?

Do you prefer that the icon will change its state and becoming ghosted until it has been copied to desired position?

Edited 2010-06-05 09:07 UTC

Reply Parent Score: 2