Hi, I think DRT's way is robust enough to be deployed and used. WRT does it exactly that way.
On Wed, Apr 21, 2010 at 12:45 PM, Jason Rukman <[email protected]> wrote: > I’m looking at some custom javascript extensions and trying to decide if I > should use a plugin or add javascript API’s similar to how DRT does it. > > > > This would be things that may be device specific for a custom application; > stuff like accessing battery level, charging information… things like that. > This isn’t something that I can see adding back to the webkit community > though as it’s very application specific. > > > > Can anyone give me some opinions on which of these two paths may be better? > I can see that using a plugin may let me add different plugins without > modify the webkit client but in this case I really will likely only have a > single plugin but the API interface hooking into > didClearWindowObjectForFrameInScriptWorld seems cleaner and easier to > implement (especially as DRT itself provides some nice sample code for it). > > > > _______________________________________________ > webkit-help mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-help > > -- --Antonio Gomes _______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
