This is seriously Cool, no more clipdown on Youtube.

Fantastic - Thank you guys, look forward to trying out a release version

@Mikey_C

While it of course looks pretty cool on screenshot, still, there is not everything clear. I will try to explain:

For plaing html5 audio/video, browser have some kind of "mediplayer" code, which, in general, its small video-player. For muiowb (for example), on morphos, they use their own write mediplayer, which have overlay support , and that is mean, that in the fullscreen mode, everything will works fast even on 600mhz machines.

But in case with Firefox code, i think there is some kind of "default crossplatform player", which just by using of software rendering do all the stuff (via ffmpeg maybe, or so).

And so, in the result, all what is matter, is:

If mediplayer of TW will not have overlay support (which should be done by porters of course, as overlay its something os-specific), then it will be not fast , or even more - slow (even on 1ghz machines). Full screen will be slow as well.

That is only what is can be seen cleary. But noone know how good or bad done mediaplayer of FF at all, even without overlay it can be worse or better than we can expect.

Personally I hope TW doesn't suffer from the memory leak problem that MUI-OWB and OWB suffer from.

Look forward :D

@kas1e

I think it will be slow like an hell on the first Alpha release, then surely the speed will be improved a lot but i don't expect to use decently any type HTML5 video on the first TW4 release ..

Of course i hope to be wrong

BTW: I doubt TW use FFMpeg to handle videos, more probably there are somethings already "integrated" with the browser

@samo79

ffmpeg is a library so integration doesn't yet mean that it isn't used.

I want it now

I also think that without overlay videos was really slow...

But on an alpha no need overlay :)

I haven't looked into the video replay code yet, but I'm pretty sure that to make it usable at all, it has to be able to be made machine specific.

In essence, it does not need a video overlay. What it needs it the possibility to create a special video surface with the correct format.

Making it actually usable is something we'll address once we're happy with the functionality, i.e. the plan is to first get all functionality in place and then get the parts accelerated that need it.

Most likely, we will, at one point, start releasing regular updated versions (not nightly like with the original FF, but maybe weekly or on an "as ready" basis), to gather information about bugs and areas that need improvement. This is especially useful for gathering information on a wider range of computers.

Stay tuned.

@tfrieden
Quote:

Right choice! Weekly ones imho good enough. Expectually if it will be organazed with bug-tracker and stuff on some site.

@kas1e
OT:
Quote:
Which reminds me, when are you going to make a next release of MUIOWB ?

@TSK
Quote:
With update4 imho :)

@tfrieden

Excellent, eventually we can use bugs.os4depot

Keep it up!

Nice to see progress, still not crazy about the old Windows/Linux style menus though, totally doesn't fit the Amiga UI.

I presume this will be fixed in the final though?

@kas1e

Bugtracker is a given, of course. It's the only really practical way of getting bug reports

@danwood_uk

Amiga features will come in once the code translation is finished, i.e. once everything that has to work does work, we'll be going for additional features.

Firefox 4+ has cleaned up the menu strips, anyway, and added the option of either keeping it, or moving it into a system defined location (on Windows, you get the small orange button in the titlebar). There's no reason why we can't drop that button altogether and add the option of making it a standard Amiga menu.

Note, though, that as I said before, the Firefox menus need a certain set of features, and I am not sure whether the AmigaOS menus allow for those features. Also, the right mouse button is used heavily in FF itself, so it might not be feasible to make it work the original Amiga way. We will most likely offer the option, though. I can say more the further the work progresses.