[webkit-dev] Place For new Core Module

[Chinmaya Sn]

Let me put it this way, I am working on a new standard, which
leverages some of HTML5 standards but tries to extend them
 (not enhance) to answer some of the Cable industry challenges.

I started by analysing WebKit layer, it has very strong assumption of
layering browser-engine, and mostly has APIs which helps you
 build a html browser, why not, WebKit is a browser-engine.

In my first case, of rendering a special kind of "app" on top of HTML5 video;
these apps don't speak html/javascript, they speak primitives such as
drawRectangle, drawLine etc. and has own events and processing
 functions (its a language in itself) which needs to be translated into
either C++ or HTML/JavaScript.

My primary requirements is to add new modules which represent new
standards which work in conjunction with HTML5 (very closely) without
any changes inside WebCore.



Today WebKit would not gain anything, this is new standard work in
progress. Tomorrow things might change, and if someone says I
want this Cable specific feature, one could easily tell 'hey build
WebKit with this flag and you will get that feature for free',
that is my motto.

I am driving this as as future proof solution.
Currently I'll be performing these changes only in my own branch.

Makes sense?



On Tue, Aug 24, 2010 at 2:09 PM, Ariya Hidayat <ariya.hidayat at gmail.com> wrote:
> I guess you also need to supply the justification: what would WebKit
> gain from such modules? Are the modules part of HTML5 and other web
> standards?
>
>
> Regards,
>




On Tue, Aug 24, 2010 at 2:17 PM, Simon Fraser <simon.fraser at apple.com> wrote:
> 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 <pkasting at google.com> wrote:
>>> On Tue, Aug 24, 2010 at 12:21 PM, Chinmaya Sn <chinmaya at 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
>>
>
>



--
Chinmaya