Welcome, Guest. Please login or register.

Author Topic: First impressions of 4.1 Update 1  (Read 6654 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Matt_HTopic starter

First impressions of 4.1 Update 1
« on: January 16, 2010, 10:56:23 PM »
Sigh. What on earth is going on in the proverbial OS4 development labs? It seems like every new release I enjoy less and less. This update feels like a disparate collection of improvements that no one thought to analyze how they worked together usability-wise. Overbearing/bad management may have killed Commodore, but the utter lack of management and lack of an overall vision for the design of OS4 is effectively driving me away - me, a will-be-the-last-Amiga-user-on-Earth kind of guy! What is going on?

Some observations I've made so far:

* No PNG icon support out of the box
There's really no excuse for this. A PNG icon module exists, why is it not bundled? Better yet, why doesn't icon.library support PNGs directly?

* Deprecated tools
IconEdit (still!) doesn't support the 32bit icon format introduced in 4.0
The 2bit Pointer prefs tool doesn't do anything since the default pointer is a 24bit one controlled by the presence/content of a deficon buried in ENVARC:Sys
This will no doubt confuse the hell out of new users. Why haven't these tools been updated?

*Another new icon set
These new icons have been appearing in releases of OWB and other programs for months/years already, and now they're system-wide. Personally, I don't care for them. They're absolutely gigantic, too.

*Inconsistent icon scaling
Fortunately, Workbench prefs now includes an option to set limits on the sizes of icons. It's adjustable to the exact pixel and there are separate scales for the Workbench itself and within drawer windows. Unfortunately, AmiDock is unaffected by the settings. I've had to remove programs from my dock in order to not have it look like a screen real estate monstrosity.

*Nonexistent bitmap scaling
Back in the 4.0 days, gadget images came in several different sizes, each suitable for different screen resolutions. Now there's only one size, so many options in GUI prefs end up having no effect (like attempting to reduce the height of the window titlebar). Scaling for gadgets should be a priority for the next release.

What I've done is created a virtually empty bitmap set - the only things in it are the Amiga key, checkbox, and Boing Ball. Everything else falls back to vector-based gadgets which, though lacking in polish, behave how I expect them to.

*Still no Preview/Test option in GUI prefs
GUI prefs is an absolute mess. There are too many options and it's not clear what they all do. There was a "Preview" button in early releases of 4.0 which said something along the lines of "Not working yet" when pressed. It was cleverly removed in later releases, but the problem of not being able to quickly test what each option does remains.

*Disappointing redesign of ASL requesters
Just as MorphOS has moved to an MUI-based ASL replacement, OS4's is now ReAction-based. Unfortunately, it comes with the expense of the requester not displaying anything until the entire directory has been loaded (older ASL would display files/drawers as they were read from the filesystem in near-real time). The ability to use the RMB to quickly switch to the devices list has also changed (it only works with the third, fourth, or fifth buttons now). It doesn't seem particularly responsive. If you're in the devices list, although pressing the button again will get you back to the directory you were in, nothing changes until the directory has been read. That is, you will continue to see the devices list until your directory is ready to go. The visual feedback is very confusing. I ended up pressing the MMB 3 or 4 times because I thought the click hadn't registered. Instead, the clicks were held in the input buffer so that as soon as the directory was read, it would take me there for a fraction of a second, then back to the devices list, where it would attempt to read the directory in again. Not fun. I may just turn off the feature altogether and use the Volumes button like in OS3.1.

There is a new clickable button in ASL to select All, None, or all files with the same extension as the currently-selected one. That's kind of neat. The devices list also shows multi-assigns in bold (usually entries like FONTS:, HELP:, etc).

*No more WBStartup!
This bothers me most of all. While I understand that the intent was to integrate something like WBStartup+, the implementation is, frankly, bad. WBStartup+ works by moving everything in your WBStartup drawer into Enabled and Disabled subdirectories. WBStartup+ then becomes the only program in WBStartup and executes everything in Enabled when run.

OS4 has removed the WBStartup drawer entirely. Instead, a new Prefs tool controls a list of programs that will be executed (I guess by LoadWB). Now instead of dragging stuff into a drawer, I have to open up a prefs tool and drag stuff in there (or navigate another ASL requester). It's far less parsimonious. I use T.H.E. to enhance keyboard and menu options in Workbench, but it seems this new WBStartup implementation can't execute scripts. It also seems that manually creating a WBStartup directory doesn't do anything. This is the biggest annoyance I've found so far, so my first priority will be to find a workaround.

That's all for now. Can't wait to have my MorphOS machine back, to be honest.

How is everyone else getting on with the new update?
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #1 on: January 16, 2010, 11:22:31 PM »
I'm ready :)

Another observation:

*Yet another redundant API!
The history of the Amiga is filled with pointless battles: MUI vs. ReAction, PowerUp vs. WarpOS, CGX vs. P96. Now we've got another one: OpenURL vs. URLOpen.

Maybe someone can correct me, but URLOpen seems to do the exact same thing as OpenURL. What was the point of creating it? Okay, it does come with a handler implementation in L:, but so did older versions of OpenURL. Wouldn't it have made more sense to just bring that up to date?

I can't imagine developers are too pleased about this, especially those who compile for all Amiga variants...
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #2 on: January 16, 2010, 11:57:39 PM »
@ Karlos

Quote from: Karlos;538659
TBH, I really don't see what the WBStartup thing was about. One of the best things about the existing system was it's sheer simplicity. I can understand that perhaps people don't want to drag stuff there and forget where it came from if they ever wanted to put it back or disable it, but there are surely other ways to deal with that (tooltypes to mark as disabled and where a tool was dragged from might have sufficed, for example).


That's what's good about the way WBStartup+ does it. You can still drag stuff in if you want to (and if an installer copies things to WBStartup everything will continue to work fine). It gives you flexibility. The new OS4 implementation doesn't.

Quote
As for not running scripts, that's not good for me. I use a few ARexx scripts to extend my Workbench with various shortcuts that I've been using since OS3.5 and still use in 4.1.


I've now got my scripts working by running T.H.E.'s setKEYandMENU from the startup-sequence (after LoadWB). Far less elegant than dragging into WBStartup, but at least it works.
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #3 on: January 17, 2010, 01:53:35 AM »
@ Dragster

Thanks for the reference - I'm experimenting now.

EDIT: Okay, I can now confirm that renaming/deleting ENVARC:Sys/wbstartup.prefs and creating SYS:WBStartup will restore the WBStartup functionality we know and love - ARexx script support and all. This solution is marginally cleaner than the one Simon Archer suggested (deleting wbstartup.library), as all that's needed to go back to 4.1.1 default behavior is to hit "Save" in WBStartup prefs.

@ thread

Observations continue:

*What is Ringhio for?
It's the new notification server, apparently. Do any programs use it yet? I'd like to see what it does. And what it looks like.
« Last Edit: January 17, 2010, 02:08:58 AM by Matt_H »
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #4 on: January 17, 2010, 05:08:21 AM »
@ redfox

I glanced over some posts about boot problems. What did you use to download the ISO? My download was corrupted by the combination of IBrowse and Hyperion's site, but OWB/Firefox were fine.
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #5 on: January 17, 2010, 02:55:20 PM »
Quote
Welcome back good old WBStartup directory!

I'm reminded of the old saying, "If it ain't broke, don't fix it" (the way WBStartup has worked for 20 years, that is) :)
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #6 on: January 17, 2010, 03:22:20 PM »
@ redfox

Apart from the IBrowse corruption, my installation/bootup was very smooth on an XE-G4. Sounds like a bug in the reworked USB drivers.

@ Framiga

Quote
the OS4 betatester coordinator is kicking out some as well "pretending" a full job-like time dedication

That is unfortunate. A smaller/less representative sample of users in the beta pool will inevitably lead to more bugs discovered upon public release. Although maybe it will cut the testing phase from 18 months down to 14 ;)
 

Offline Matt_HTopic starter

Re: First impressions of 4.1 Update 1
« Reply #7 on: February 04, 2010, 01:33:56 AM »
Quote from: Karlos;541419
It works fine for me, provided the scripts have a proper icon with the associated default tool.


What default tool did you use? I thought I couldn't get anything going with RX, but it's been a few weeks since I tried and I may not be remembering correctly (and I've since gone back to the "classic" WBStartup methodology, so it's not a big deal).