I'll be the first to ask this question: what do you need to do that you can do with existing WebKit APIs, and existing web technology?
With video, you could use http streaming to deliver custom content, and make sure of accelerated compositing to ensure that you can efficiently layer HTML content on top of video. If your platform does not have support for these, then the "right" way to address this is to add support for these missing pieces, rather than hacking at WebCore internals. Simon On Aug 24, 2010, at 12:31 PM, Chinmaya Sn wrote: > The current module I have implemented works closely with > RenderingEngine/GraphicsContext and HTML5 video player, which > tries to deliver some special interactive Apps (In Cable World) as an > overlay over HTML5 Video, > the apps themselves are delivered as one of the private streams in the > Video, so some work has gone inside implementation > of video player itself. > > In near future, I will be poking around a lot with HTML5 player. I > will be implementing lot more modules like above, > which will be linked to WebCore. Each of the new enhancements I > provide needs to be use WebCore and should be > accessible to HTML page author. So I will be drilling some holes to > expose these modules as a finite set of JavaScript objects. > > -- > Chinmaya > > > > On Tue, Aug 24, 2010 at 1:23 PM, Peter Kasting <pkast...@google.com> wrote: >> On Tue, Aug 24, 2010 at 12:21 PM, Chinmaya Sn <chinm...@gmail.com> wrote: >>> >>> I have special case in my hand; currently I maintain a custom branch >>> of WebKit, I already have >>> implemented a module which sits closely with WebCore and it works just >>> fine. One of my >>> goals is to deliver these changes back to community and even may be >>> back to WebKit repository. In near >>> future I will be implementing at least 2-3 such modules, which work >>> closely with WebCore and >>> JavaScriptCore but they may not have to anything to do HTML browser >>> engine as such. >> >> Why don't you say more about what you're trying to do. It's hard to answer >> in the abstract. >> PK > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
