So I got accepted into GSoC again! I’m going to be working on WebKit2. But what is WebKit2, or even WebKit, for that matter? Well, WebPositive uses WebKit to render its web pages. Currently, we use the WebKitLegacy API to communicate with WebKit. It would be nice to switch to the newer version: WebKit2. However, our port of WebKit2 still needs work. At present, it has lost its ability to even render any webpage at all! So, getting WebKit2 to work will be the primary goal of my GSoC project. If there’s time left, I might be able to integrate it into WebPositive.
This report covers hrev57616 through hrev57679.
The goal
My goal is to be able to use CompCert, a certified compiler.
It is a compiler whose passes are formally verified to not introduce change in the semantics from the C code to its translation in asm.
The installation goals
Compcert is installed from its Coq sources. So i need Coq.Coq is installed from sources or as an OPAM package. OPAM being the Ocaml PAckage Manager.opam needs OCaml anyway. So I need OCaml.OCaml is installable through OPAM or from sources.
The easiest part
Porting OCaml was not too hard: copying most of Linux configuration in the configure{.ac} files work as is.
Don’t forget to add some platform detection in config.guess, and some libraries tweaking:
This report covers hrev57561 through hrev57615.
This blog post was originally a forum post. It is reproduced here on the website to make it easier to find and reference.
I heard that some more people may be interesting in helping with WebKit. So here is a summary of the current state, the things I think need work, or the possible future paths to explore.
Keeping WebKitLegacy up and running
The Web moves fast these days. So we have to stay very up to date with upstream WebKit. Until we have a nice and shiny WebKit2 browser, and, anyways, even after that, we need to keep things up to date.
This report covers hrev57494 through hrev57560.
This RFC proposes to change the Haiku coding guidelines to change the formatting of variable and member declarations from a Table Class Member Declaration Style, to a Normalized Declaration Style or a Aligned Declaration Style. The arguments are that (1) the current format has severe limitations which limits the aesthetic value of the current formatting, especially when modern C++ language features are used, and (2) it is not a good use of the time of Haiku’s contributors to modify and maintain custom logic in the haiku-format tool (derived from clang-format). If the proposal is adopted, any new code contributions will have to use the new formatting style, and contributors are required to reformat any declarations that they modify.
This report covers hrev57429 through hrev57493.
This report covers hrev57364 through hrev57428.
This report covers hrev57309 through hrev57363 (again a bit of a shorter month than average.)
