Re: [webkit-dev] S60WebKit MIME type question

2009-07-15 Thread Zalan Bujtas
One thing to look out for is that I don't thin the NPAPI is fully implemented on S60. it is pretty much fully implemented on S60 AFAIK, though the API got symbianized for some reason, by changing some data types (char*) to Symbian types (HBufC*).

[webkit-dev] S60WebKit MIME type question

2009-07-14 Thread Sam Critchley
Hi, Apologies for the very basic question, but I'm trying to find out how you can use custom MIME types in WebKit on S60 (3rd and 5th editions). We're looking at doing something like triggering the S60 camera app using a camera button in a web form (which is accessed in an app using

Re: [webkit-dev] S60WebKit MIME type question

2009-07-14 Thread Jack Wootton
If a browser finds a MIME type it cannot display (for example from an embed or object tag) then is will iterate through available plugins and load the plugin which handles that MIME type. Regarding camera on S60, you may want to take a look at: Nokia hvave released a beta version of the their

Re: [webkit-dev] S60WebKit MIME type question

2009-07-14 Thread Sam Critchley
Hi Jack, Thanks for taking the time to reply. The Nokia Platform Services resources are great, but currently only available in WRT on their S60 5th edition devices (5800 and N97). I think we're also going to look closely at the plug-in route as well - I wonder if there's a repository of

Re: [webkit-dev] S60WebKit MIME type question

2009-07-14 Thread Jack Wootton
Plugins should follow the NPAPI (https://developer.mozilla.org/en/Gecko_Plugin_API_Reference) and so it shouldn't really matter if it pre-dates WebKit. No doubt someone else on this mailing list can offer more help here (since I'm new to webkit). If you sign up to the Symbian Foundation, then

Re: [webkit-dev] S60WebKit MIME type question

2009-07-14 Thread Jack Wootton
Just to add, you are right, S60 browser uses ECOM to load a list of plugins at runtime that implement the interface 'CEcomBrowserPluginInterface'. It stores meta data about each plugin, such as the MIME type it handles and the UID of the DLL implementing the plugin. The browser then loads the