Well, now that Flash on AmigaOS seems near (at least not impossible) and system plugin can become "standard" also on our platform would be cool to extend this technology in other area expecially if Joerg can enable NPAPI on OWB
Reading a PDF or watching a video with MPlayer/DvPlayer inside OWB seems a nice gesture to me
Reading a PDF or watching a video with MPlayer/DvPlayer inside OWB ? That would be a dream Great idea if it is possible! I would spend some money for that plugin(s), just as for OWB and flash-plugin.
Wouldn't NPAPI have to be implemented in the OS, a plugin for each application at least.?
IBrowse uses mime types, is there a way to use plugins in the same way?
NPAPI must be implemented by the browsers, not by the OS. After that, it's a matter of people writing plugins. For example, if Stephen made an appropriate API for DvPlayer so that it could be embedded into another program, a DvPlayer plugin could be made that uses DvPlayer to embed video into a webpage.
Indeed - has everybody forgotten about IBrowse already? The NPAPI compatible API was after all one of the main reasons IBrowse 2.4 was delayed so long. Stefan initially added NPAPI support to IBrowse many years ago - believe it or not, Christmas 2002 was the first time I saw flash up and running in IBrowse, but obviously it was a while before this was integrated into the IB2.x source tree.
Indeed - has everybody forgotten about IBrowse already?
well, if you don't hear anything (new) about it one tends to forget... believe it or not but it seems that ibrowse has been replaced by owb for most of the (os4) users. sadly... i really would appreciate to hear some updates about ibrowse development from time to time - IF there is any.
Reading a PDF or watching a video with MPlayer/DvPlayer inside OWB ? That would be a dream Great idea if it is possible! I would spend some money for that plugin(s), just as for OWB and flash-plugin.
Why are everybody so eager to get these plugin solutions? I have never understood why it is better to e.g. read a PDF file in a reader window embedded inside your browser window, when you could read it in a separate window with the application's full functionality available and where you can resize the window and flip it back/front as you wish, whle still being able to use the browser independently in its own window while you read.
On Windoze at work, it always irritates me to e.g. get Word files opened in IE; when I'm done reading them, I always by habit close the window thinking I'm closing Word and getting back to IE -- which closes IE so I have to start it again.
I'm much happier with the Amiga Way (TM): Delegate tasks to the programs that were made for them, make use of IPC (using ARexx or whatever means you want), and don't try to hide the fact that you're doing it, it is after all one of the strengths of our platform.
Indeed - has everybody forgotten about IBrowse already? The NPAPI compatible API was after all one of the main reasons IBrowse 2.4 was delayed so long. Stefan initially added NPAPI support to IBrowse many years ago - believe it or not, Christmas 2002 was the first time I saw flash up and running in IBrowse, but obviously it was a while before this was integrated into the IB2.x source tree.
It's been noted before, and no doubt the NPAPI on OWB will be made compatible; it doesn't make sense to have conflicting versions of the same API on one system. However, this post in another thread says that Ibrowse 2.4's implementation isn't 100% compatible with NPAPI.
Is there any chance that we'll see this fixed in a 2.5 release? And what about 3.0? I'm sure that many are wondering if there's been any progress on that front.
You can always choose if you like to open your document (talking about doc files) in an "external" program as always or alternative embedded on OWB, if we only speak about document I can agree with you but there's a lot of other implications and use that you can reach only with NPAPI expecially regarding videos or audio stream on various website
So IMHO plugins and NPAPI are really needed on AmigaOS
It's been noted before, and no doubt the NPAPI on OWB will be made compatible; it doesn't make sense to have conflicting versions of the same API on one system. However, this post in another thread says that Ibrowse 2.4's implementation isn't 100% compatible with NPAPI.
Is there any chance that we'll see this fixed in a 2.5 release? And what about 3.0? I'm sure that many are wondering if there's been any progress on that front.
Depends what you mean by 100% compatible - I doubt any browser is 100% compliant with the full NPAPI spec. Certainly there are some bugs and omissions, but everything that is needed to get stuff like flash plugins up and running is there already in 2.4. Remember that we only had a flash plugin to test the API with, and we work with developers to address any NPAPI issues in IBrowse. A number of NPAPI issues have already been fixed for 2.5.
As for 3.0, at this moment in time it's not looking like it's going to happen, but never say never . And indeed with OWB, why bother? It's frustrating for me personally that 2.5 was not released on schedule (could have been released 12-18 months ago), with IBrowse running natively on OS4 since July 2007. The reasons for the delay are that our testers (and me too) had lots of stability issues with IBrowse on OS4, and it now seems that the majority of those problems were down to OS4 itself (recent OS4 beta updates have fixed remaining issues with IBrowse). Another major deciding factor is that we still need to sort out the distribution mess which has not changed at all since IOSPIRIT closed - this has to be sorted out with Stefan if we are ever to move forward .
As for 3.0, at this moment in time it's not looking like it's going to happen, but never say never . And indeed with OWB, why bother?
Because it's a complete browser, unlike OWB which doesn't even have a toolbar (in the SDL, GTK and Qt versions).
The WebKit engine used by OWB is of course much better than the one of IBrowse and it's impossible to add all features of WebKit or Gecko to the IBrowse engine, but adding the missing features (DOM, CSS and IFrames) to get 99% of the pages working correctly again in IBrowse is very likely less work than implementing an AmigaOS 4.x browser around OWB.
Another option would be to throw away the IBrowse engine and replace it by WebKit or Gecko, for example just using the IBrowse GUI and network functions (in which the only important missing feature is AFAIK HTTP/1.1 persistent connections) with WebKit as engine, which should be quite easy if you use OWB instead of WebKit directly, would be a much better browser than OWB. It would have a disk cache, working cookie support, cookie manager, download manager, support for HTTP authentication with password manager and a lot of other features OWB doesn't have, and wont get for years.
Even if most people use owb,like myself. If a IB 3.0 comes out i'd buy it before you could blink. I think that goes for many of us. IB is a great program,just needs some updates. And why not distribute like bille suggests?
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
