What about the IBrowse NPAPI flash plugin? Can't you test against that?
No, NPAPI plugins are shared objects, the IBrowse plugins aren't.
On Windows, NPAPI plugins are DLLs not shared-objects, so I see no difference between this and using Amiga OS shared libraries on Amiga OS, particularly considering that IBrowse is a 68k app, and shared objects don't exist there.
@Hans Quote:
It's been noted before, and no doubt the NPAPI on OWB will be made compatible
If someone else wants to add support for IBrowse plugins that's no problem. OWB is open source, just implement it and add a patch to the OWB trac, or send it to me. I wont implement support for AWeb, IBrowse, or any other custom plugin system in the AmigaOS 4.x port of OWB, I'll only implement support for standard NPAPI plugins.[/quote]
I have no problem with OWB being able to load .so based NPAPI plugins, but I hope that someone will do this so that we have one common NPAP Iimplementation that is supported by all browsers. It shouldn't be too hard to do.
@joerg What happened to the network progress bar that previously appeared in the lower right hand corner of the OWB window?
When I clicked the link to send this message, this page loaded with the last part of the link still visible at the lower right where the progress bar used to be. When I moved the pointer over another link, the old link residue disappeared. It's kind of a nitpick just to report it. It's no big deal really.
You forget that Windows DLLs work very much like shared objects.
AmigaOS shared libraries OTOH are completely different beasts. For one thing they are much more work to create for the other they have to be reentrant while shared objects and DLLs do not have this requirement.
I have the same problem with the progress bar like you. Sometimes it works and sometimes don't. I use fuelgauge.gadget 52.2 (9.6.08) like Salass00 too.
You forget that Windows DLLs work very much like shared objects.
AmigaOS shared libraries OTOH are completely different beasts. For one thing they are much more work to create for the other they have to be reentrant while shared objects and DLLs do not have this requirement.
I'm aware that DLLs are a lot like shared objects. However, it's still different. If shared object support didn't exist on Amiga OS 4, we wouldn't be having this conversation, since no one would have an issue with adapting NPAPI to work as a shared library.
The reentrant requirement isn't as big a deal as it looks, because it's entirely possible to provide each program that opens the library with its own variables, and even code.
Admittedly it's not as easy to create a shared library as it is to create a .so, but that's simply because no one has decided to create an easy way to make them. It shouldn't be too hard to create a compiler (or a separate program that uses GCC) that automatically scans source-files for "libexport" (equivalent to "dllexport") as it's being compiled, adds them to the main interface (the idltool XML file will ensure that order is preserved), and compiles it into a shared library. I thought of doing something like this a while ago, but just didn't have the time. Source code parsers never were my cup of tea.
Same here, althought the bar DOES pop up but it stays with only a pixel width of 1 or 2 pixels ... doesn't grow (even with massive content) and shuts down when the site has finished loading. Strange error
Has anyone found out how to use the OPENURL tooltype?
It should work if OpenURL is installed correctly and one clicks on a "mailto:" link (at least, thats how i understand it, but here nothing happens. Do i need to add a command after the tooltype (the path to the exe maybe?)
If anyone wants to test, there is a pretty easy mailto: link here
@salass00 I'm using v52.2 as well. I'll have to do a little investigating with Snoopy. Does fuelguage use some custom imagery in the OWB directory? I did keep some old images I like better than new ones.
Has anyone found out how to use the OPENURL tooltype?
Yes. Your link works fine with OpenURL set to use YAM for mailto links.
You need to install OpenURL from the archive at OS4Depot. You need to set the OpenURL prefs for your system & programs. Set the OWB Tooltype: OPENURL=OpenURL %s . If OpenURL is not in your command path ( C: ) then use the complete path in the OWB TOOLTYPE.
The OpenURL default prefs may not work on your system so you need to check that before using OpenURL. Be sure that you don't have an old copy of OpenURL, OpenURL prefs or openurl.library lurking somewhere on your system. Mixing newer and older versions can have unexpected consequences. Older OpenURL archives give the same name to the OpenURL prefs program as the OpenURL command. The OS4 version has changed the name of the prefs program by adding a space (i.e. "Open URL") to eliminate potential problems.
If you see OpenURL archives with higher version numbers than the one at OS4Depot, ignore them. The previous author released versions for MorphOS (and possibly OS3) that are not completely based on the code at SourceForge. The OS4 version is compiled from the SourceForge code and can be fixed when necessary.
@joerg Your readme mentions a problem with OpenURL when the requested program can't be found. I was unable to reproduce the problem. Could you check and be sure that you are using OS4 OpenURL from OS4Depot? I helped test the library for the programmer that got the sources into a SourceForge repository and ported it to OS4. I helped him update the OpenURL command based on my PopURL program and can contact him if there really is a problem with the OS4 version of OpenURL.
Same here, althought the bar DOES pop up but it stays with only a pixel width of 1 or 2 pixels ... doesn't grow (even with massive content) and shuts down when the site has finished loading. Strange error
I am not using TABS (I prefer seperate windows). The fuelguage doesn't appear at all if I don't use TABS and acts like yours if I do use TABS. It's a little wider than you describe but never moves. It just pops up when a page is being loaded, does nothing and then disappears when the page is loaded. The readings I saw in earlier OWB versions didn't seem to accurately indicate how much total data remained to be D/L and I judge when the page is finished loading by the ghosting of the stop-sign gadget anyway. I suspect that it is more noticeable to me because I am on dialup and I get to stare at the fuelguage for a long time while pages are loaded
This is a great webbrowser it works wery fast on my A4000. By I have a problem whit my webmail TDC (Denmark). When I try to login I get the following error:
I get a complete system freeze that requires a hardware reset when I visit the http://www.realtor.com/ main page. I just watch the house images scroll by for a couple of minutes without clicking anything and my ?A1/OS 4.1 freezes and I have to use the reset button to reboot. Can anyone else comfirm this??