On Tue, Aug 24, 2010 at 11:50 PM, Chinmaya Sn chinm...@gmail.com wrote:
Thanks All. I think I am getting the general idea of what can get into
to WebKit and how things fit.
Right now both the standard and implementation are WIP, spec is intended to
be a Web standard. At this point, neither
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
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,
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
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
On Aug 24, 2010, at 2:26 PM, Chinmaya Sn wrote:
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.
Can you point us to this standard? Is it a W3C spec?
I
I am driving this as as future proof solution.
Currently I'll be performing these changes only in my own branch.
Is your branch available somewhere? Are your patched made public already?
--
Ariya Hidayat
http://www.linkedin.com/in/ariyahidayat
___
Given your description, I'm not sure this functionality is appropriate for
WebKit. We are generally reluctant to take feature patches for features that
are experimental or of niche interest - we prefer to focus on technologies that
are part of the standards-based Web technology stack, that are
Thanks All. I think I am getting the general idea of what can get into
to WebKit and how things fit.
Right now both the standard and implementation are WIP, spec is intended to
be a Web standard. At this point, neither the standard nor the
implementation are public.
My primary goal was to keep
Secret ports have an absolutely horrible track record of ever catching
up with public WebKit.
Only one has ever been successful to my knowledge (Chromium) and I'm
not even sure we could call it full success yet. (They've spent 2
years attempting to fully catch up, and yet you can't build a
10 matches
Mail list logo
