[webkit-dev] Help regarding rendering in webkit2 port of haiku

Rajagopalan Gangadharan g.raju2000 at gmail.com
Mon Jun 10 00:07:16 PDT 2019


>btw I might be able to help out (no promises), I haven't touched WebKit
code in a few years but I was responsible for TextureMapper and the
coordinated graphics system and I like bizarre >projects (a Haiku port
sounds like one). Let's see how it goes :)

Sure thank you for very great insite will look into to it and get back :)

Regards
G.Rajagoapalan

On Mon, Jun 10, 2019 at 12:07 PM Noam Rosenthal <noam at webkit.org> wrote:

> ~ (reposting from webkit email)
>
> Hello!
> I suggest starting by learning one of the other ports - like GTK - how the
> whole flow works from the windowing system to WebCore to the graphics
> system. Read the code, run it in debug mode and put breakpoints, get those
> aha moments of how it all works together.
>
> Note that coordinated graphics is not automatically the right choice for
> every port - it was created for mobile windowing systems where window
> context-switching was expensive and single-context hardware acceleration
> was cheap. If you're looking for a guide check out
> https://trac.webkit.org/wiki/CoordinatedGraphicsSystem, hopefully it's
> still somewhat valid. I would start there by understanding the flow and how
> it fits with the Haiku architecture, seems like you've started doing that
> already. you're on the right track there.
>
> btw I might be able to help out (no promises), I haven't touched WebKit
> code in a few years but I was responsible for TextureMapper and the
> coordinated graphics system and I like bizarre projects (a Haiku port
> sounds like one). Let's see how it goes :)
>
>
> On Mon, Jun 10, 2019 at 9:05 AM Rajagopalan Gangadharan <
> g.raju2000 at gmail.com> wrote:
>
>> Hello everybody,
>>
>> A quick look back on what we have done so far. We are trying to port
>> webkit2 to haiku and we have a working IPC with us. So the next step i
>> presume is to be rendering.
>>
>> I did few amount of research and have few basic ideas. Correct me if I am
>> wrong.
>>
>> 1) The rendering takes place in webprocess over a shared bitmap which is
>> then rendered onto the client area in UIProcess.
>>
>> 2) Webkit uses coordinated graphics system which relies on OPENGL.
>>
>> So we look forward to get the rendering step done or is there anything we
>> should take care in between? .
>> Our platform doesnt have hardware accelerated OpenGL yet we have software
>> implementation vesa which we tend not to use.
>> We have a working texture mapper and compositing coordinator from our
>> webkit legacy port. I think this makes up the entire compositing
>> coordinator.
>>
>> So it would be of great help if any tells how could we proceed like what
>> should be our next move. Perhaps a small guide would be better.
>>
>> Thank you
>>
>> Regards
>> G.Rajagopalan
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> https://lists.webkit.org/mailman/listinfo/webkit-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20190610/f5d8bfa9/attachment.html>


More information about the webkit-dev mailing list