@ChrisH

Quote:

Just to be noted that displaying icons or thumbnails doesn't necessarily have to slow down anything, when done properly. By properly, i mean that it should be done in a low priority thread, running asynchronously to the main requester context once scan is done. That way, you get all files displayed blazingly fast first, and then you add icons and all kind of stuff (optionally, for those who hate icons or thumbnails) in the visible area.

But if icon/thumbnail creation is done synchronously, it will really be catastrophic, of course.

@vox

Nice effort, but it can in no way compete with actively developed OSes.
And the comparison list on the second page is wrong in a few places...
- DOS is more advanced in OS4 than with any OS3 patches.
- OWB 68k isn't superior. The OWB version available for 68k is way behind the OS4 one (or any other one)).
- OS4 doesn't have MUI4.
- Warp3D Nova was never developed (AFAIK).

Many other points could be discussed as well.

@LiveForIt

If he removes the tag, he won't see much of the image. :)

Anyway, it would berather weird if dtpic.mui wouldn't work the same way on OS4 as on 3.x or MorphOS.

@ZeroG

It doesn't seem to happen in my webkit port (clicking second link open in a new tab/window), even with an older webkit revision than the one used in OWB 3.27. So i wonder if it wouldn't just be related to some webkit option that would have been enabled in OS4 port.

@Vulture

I'll probably implement a script manager (greasemonkey like), and then one can run whatever userscript he wants, yes.

@K-L

It's also possible in OWB actually. WebKit indeed has userscript functionality, which does the same as greasemonkey, except a script manager UI has to be written (to load/remove scripts and so on).

I just tested that script in OWB, and besides a minor modification to use HTML5 video first instead of x-mplayer plugin, it rewrites properly the youtube page.

@Mlehto

Ambient is inspired by Dopus Magellan features/concepts, not explorer.

@TSK

About Ambient window toolbars, it's optional, and brushes are themable too, of course.

@kas1e

He certainly should fix it and use memmove() instead, because memcpy isn't supposed to support overlapping areas, and that's in memcpy manual page. :)

@Deniil

Maybe it confuses it indeed (or CURL), because OWB certainly handles other gzipped pages.

@Skov

This is a fairly simple game, and it compiles (and works) directly, but the "issue" is the game itself isn't totally complete yet (missing random events like aliens, earthquakes, ...)

@davebraco

When the remote host isn't reachable anymore, it seems to leave the handler in a state leading to doslist lock too (which explains why the whole workbench or asl requesters and so on are locked too). Fortunately, you can still break smbfs process (ctrl-c).

@DAX

Quote:

It's nice to have faith, but seriously...

MorphOS would be surpassed by a vague announcement, that might not even have anything to do with actual features? Right.

And what exactly in 4.1.1 is surpassing MorphOS by the way? Let's review the features announced for 4.1.1:
- Dynamically scaled icons? Available in ambient since four years.
- USB2 (only OHCI (= low-speed) was announced for 4.1.1)? EHCI (hi-speed) and OHCI are available since MorphOS 2 (or 1.4.5 if we take the older USB2 3rd party driver into account).
- Workbench DOS notifications (AutoupdateWB proper replacement)? Available in Ambient since about five years.
- Shell with tabs, history, scrollbar, completion? Available in MorphOS since six years (and relooked with MUICon in 2006).
- DDC support? Available in MorphOS since MorphOS2.
- Window shadows? Available since MorphOS2.
- Friendly installer? Available since MorphOS2.
- Faster overlay support? Available since MorphOS 1.4.5.
- Contextmenus and ClicktoFront by default? Default in MorphOS since 1.1 or so.

So what's left:
- New theme.
- Notification system. Ok, fine, why not.
- Wbstartup manager (but it's available on OS3.x since a dozen years with WBStartup+ tool)

@Snuffy

First, genesi has nothing to do with MorphOS, so asking them is pointless. Secondly, MorphOS Team has no motivation in porting MorphOS to buggy (A1) or underpowered hardware (SAM).

@afxgroup

In fact, i doubt it's streaming being your problem. Here that easyvideo.swf + some lowres flv also takes 35% cpu with swfdec, but the actual problem (at least in swfdec, but i suspect in gnash too) is that the usual video players (youtube in particular) add much overhead with their slider, time status and so on. Youtube in particular hurts swfdec very much, because it forces it to take a slow render path because of some shapes.

And of course, youtube has slowly migrated to h264 content, which makes it worse too (because decoding lowres flv takes about 2% cpu with ffmpeg :)).

@samo79

Like daff said, it's currently a bit slow for video stuff (depending on the player.. googlevideo is rather fast, youtube is really slower, dailymotion is in between, ...). All this comes down to Flash script overhead (which explains the difference between players) and rendering method used by swfdec.

While the current plugin is still usable for other stuff, I'd rather try to find a way to accelerate it a bit more before releasing it. :)

@daff

Quote:

Depends what you really use. Video is of course demanding, but there are many other uses in Flash besides video.

@Arnie
Quote:

You'll probably be able to see that kind of thing on OS4 in the future too, once GNASH plugin is available.

Here's what it gives on MorphOS (with swfdec)... :) http://fabportnawak.free.fr/swfdec-owb-plugin6.png

But anyway, it's way more efficient to stream the youtube stream with MPlayer (with the link retrieved by getvideo, for instance).

@freddix

Learn to code properly?

What you ask is very bad practice.

@Elwood

No, since the current cairo font backend and gtk port in general handles all that just fine.

@Elwood

Quote:

This is about WebKit (and its graphics/fonts/... backends) being compliant... Sandlabs or OWB porters don't have much to do with that result, actually (IIRC the only fix I had to do to reach 100 was to fix the base64 decoder).

And Chrome or safari should also reach 100 anyway. Also, this doesn't cover the whole browser compliance. WebKit is often tested against this acid3 test, but in the meanwhile, it also fails to render properly many other things (often more simple).

And at last, for the user experience, I'd say it's way preferrable to have a feature-rich browser reaching only 50/100 (good history support, url completion, bookmarks, dl manager, whatever) than having a feature-less very compliant browser.

@ssolie

Why, it's MUI stuff anyway, totally useless and worthless. :)

And the generic download code (that was written by aros owb porter and me) is already imported in main tree.