Linked by Kroc Camen on Mon 8th Mar 2010 11:36 UTC
Morphos Fabien "Fab" Coeurjoly has released Origyn Web Browser 1.7 for MorphOS. HTML5 video and audio is provided through FFMpeg, supporting a wide range of codecs (Ogg/Theora/Vorbis, MPEG4, H264, AAC, MP3, Wav). Highlights of the change log follow.
Order by: Score:
video tag support
by hornett on Mon 8th Mar 2010 12:30 UTC
Member since:

Great to see a small project get the video tag working IMHO. And it supports Theora *and* h264!

Well done devs!

Reply Score: 1

Ballot screen
by rjamorim on Mon 8th Mar 2010 12:47 UTC
Member since:

Too bad it doesn't run on Windows. The ballots screen needs more browsers!!

Reply Score: 4

Comment by Laurence
by Laurence on Mon 8th Mar 2010 13:41 UTC
Member since:

It says a lot when a virtually unheard of web browser for a platform that occupies less than 1% market share is a whole set of standards ahead of the most widely used browser on the planet built by the biggest software house in history.

On a related note: Am I right I believing OWB boasts a webkit engine?

Reply Score: 5

RE: Comment by Laurence
by phoudoin on Mon 8th Mar 2010 14:14 UTC in reply to "Comment by Laurence"
phoudoin Member since:

On a related note: Am I right I believing OWB boasts a webkit engine?

You are.

Edited 2010-03-08 14:15 UTC

Reply Score: 1

works like a charme
by -ujb- on Mon 8th Mar 2010 14:43 UTC
Member since:

It is really great to see how fast OWB for MorphOS is progressing. Not too log ago browsing the net with MorphOS was rather limited, but today it is really quite up to date again. And it is not only the underlying techniques, but also many well thought small additions that make the program pretty convenient.
In the meanwhile I ditched Opera (on Win or OS X) as my main browser in favour to OWB on MorphOS. It is very, very stable, conveniently fast and supports the latest standards.
Only the flash support could be better (as on all platforms that don't have official support from Adobe), albeit pretty useable for many things though.

Hats off for Fab - he really did a good job!

Reply Score: 1

by poundsmack on Mon 8th Mar 2010 15:27 UTC
Member since:

great news indeed!

Reply Score: 2

by Timmmm on Mon 8th Mar 2010 15:59 UTC
Member since:

Cool, but it's a very bad idea to just pass anything in a video tag through to ffmpeg. It's a great library, but I absolutely guarantee you there are a ton of security vulnerabilities in it.

Interesting reading:

Reply Score: 1

RE: Security
by iaefai on Mon 8th Mar 2010 16:20 UTC in reply to "Security"
iaefai Member since:

When I looked at ffmpeg's main.c a few years ago there was at least a function in there with over a thousand lines of code in it.

I don't know if things have changed since then, but it doesn't give me confidence in its use.

Reply Score: 1

RE: Security
by ferrels on Mon 8th Mar 2010 22:50 UTC in reply to "Security"
ferrels Member since:

That's OK. MorphOS is a case-study in security thru obscurity. There are probably less than 100 people on the planet who even code for it anymore.

Reply Score: 2

Lazy developers?
by iaefai on Mon 8th Mar 2010 16:17 UTC
Member since:

Sir, are you suggesting that only lazy developers do not target MorphOS?

Reply Score: 1

RE: Lazy developers?
by Bill Shooter of Bul on Mon 8th Mar 2010 17:03 UTC in reply to "Lazy developers?"
Bill Shooter of Bul Member since:

Well Some are lazy and some are la$ee. Tough to tell the difference when you pronounce them the same. Simple mistake really.

Me, I'm too lazy to be la$ee. Or maybe there really isn't any difference between ignoring a platform because you forget about the platform, or ignoring a platform because its not worth your time to invest any resources in it.

Reply Score: 2

Port to Amiga OS3.9?
by leech on Mon 8th Mar 2010 17:04 UTC
Member since:

I've seen the port to Amiga OS3.9, but it hasn't been updated in a while.

Bring on the classic Amiga web browsing goodness! Or something...

Reply Score: 2

by panzi on Mon 8th Mar 2010 20:31 UTC
Member since:

I want ffmpeg to be integrated into firefox! (And arora and rekonq.)

Reply Score: 3

What about containers? (Not codecs)
by dindin on Mon 8th Mar 2010 21:54 UTC
Member since:

I hear a lot of debate about codecs (H.264 vs. Ogg) but what about the containers supported in HTML5?

To playback a file, I think the SRC can point to a .mp4 file, or a .ogm/.ogg file. What other containers are supported?

How about live video? If I want to stream live content with HTML5, how is that done? What containers are supported? MPEG2-TS like for Apple Adaptive HTTP streaming? Has anyone done live streaming with HTML5?

Edited 2010-03-08 21:54 UTC

Reply Score: 2

edogawaconan Member since:

I hear a lot of debate about codecs (H.264 vs. Ogg) but what about the containers supported in HTML5?

Please stop using Ogg when referring to Theora.

Reply Score: 3

About GNUStep.
by AlexandreAM on Tue 9th Mar 2010 01:48 UTC
Member since:

Ok, I know this is off topic, but it's a genuine question. I'm not trying to flame the guys on GNUStep either, I know they have their (few) hands full.

But is there a reason why every single platform on earth is sporting a Webkit implementation except for the one in which it seems to make more sense: GNUStep?

Reply Score: 2

RE: About GNUStep.
by Hypnos on Tue 9th Mar 2010 09:05 UTC in reply to "About GNUStep."
Hypnos Member since:

You gave the answer -- porting WebKit is highly nontrivial. Perhaps all it takes is one dedicated developer, but he would have to be quite experienced in GNUstep and also willing to put in many hundreds of hours.

You can't just adapt the OSX port because calls to CoreFoundation are sprinkled throughout. Also, if you ask the WebKit people, they would strongly suggest a cleanroom port for future maintainability.

Reply Score: 1

Porting OWB? SDL?
by BigBentheAussie on Fri 12th Mar 2010 05:46 UTC
Member since:

I know it is hardly the same....but I heard there was an SDL port of OWB. I don't know how far that went or if it is still maintained, but one would think that would be somewhat easier to port. I would think an SDL port of OWB/Webkit rendering engine should be useful as a fallback for all OSes. You could then develop your own OS native browser application around it. Sure it would be lowest common denominator, but highly portable and especially useful for modernising the browsing experience for the more obscure OSes and hardware platforms out there. I could even see the rendering engine being embedded in applications for several purposes.

Reply Score: 1