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.
Post a Comment
Member since:
2005-09-19
Member since:
2005-12-05
Member since:
2007-03-26
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?
Member since:2006-06-09
Member since:
2005-10-21
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!
Member since:
2005-07-13
Member since:
2006-07-25
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: http://scarybeastsecurity.blogspot.com/2009/09/patching-ffmpeg-into...
Member since:2009-12-14
Member since:2006-08-15
Member since:
2009-12-14
Member since:2006-07-14
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.
Member since:
2006-01-10
Member since:
2006-01-22
Member since:
2006-03-29
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
Member since:2006-10-10
Member since:
2006-02-06
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?
Member since:2008-11-19
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.
Member since:
2008-03-29
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.