WebKit is split into several processes. One of these processes is the browser itself. In my case, this is MiniBrowser, but, hopefully, in the future, it is WebPositive. Since browsers can have any name, WebKit refers to this process as the UIProcess. And, indeed, that process is mainly responsible for the UI. Our port will also be using two other processes: NetworkProcess and WebProcess. Unsurprisingly, NetworkProcess does the networking. WebProcess does all of the work associated with a single web page. For example, it is responsible for running JavaScript and does most of the work for rendering the web page. There is one WebProcess for each web page.
When the coding period began I was expecting to publish a progress report every week. However, we’ve reached the end
of the first month of the coding period and this is my first update: This probably tells that there hasn’t been as
much progress as I expected, although progress have been made.
What works
The library was one of the first things I got done, because it consists of very portable
code, which made it very easy to port, while allowing me to test the (still reduced) driver
capabilities much easier as I could use already existing code examples for NVMM instead of
trying to talk directly to the driver.
Enhancing the Find Panel: A Comprehensive Update
Introduction
Hi there everyone. Since I made my first contribution to the project, I thought making a blog post about it would be helpful. I’m excited to know your thoughts on the changes that have been made to the Find Panel. Most of the current changes are made with ease of use kept in mind.
These updates include the addition of a Menu Bar and the migration of the more-options section into this Menu Bar. This blog post details all the changes and how they are intended to be used.
Project status overview
Despite being a bit silent on the blogs, the project is still alive and kicking.
Completed tasks
I have completed a port of the
gdbserver component of GDB 14.
The port has the full capability of a regular gdbserver port, including:
- Attaching to new and existing processes.
- Manipulating CPU and memory state.
- Reading loaded libraries and symbol information.
- Setting breakpoints.
- Receiving events about breakpoints, teams, threads, images, and syscalls.
Connected to a GDB frontend on a compatible ELF-based system, gdbserver provides a nearly seamless
debugging experience. With the correct configurations, Haiku C/C++ applications can be built on
VSCode, deployed to Haiku, then debugged with the IDE’s UI through gdbserver.
intro
Hello, once again! It’s been a month since the last update, so here we go.
Good news, there is active development of the virtio sound driver for Haiku.
Key progress includes assigning channel maps to their respective streams and
integrating PCM stream scanning.
Additionally, efforts have focused on modularizing the driver, ensuring
compliance with Haiku’s coding standards, and laying the groundwork for further
enhancements to functionality. While progress has been substantial, there are
still areas requiring refinement as we continue to expand the driver’s
capabilities.
This report covers hrev57720 through hrev57753.
Currently, MiniBrowser (the simple browser that we use to test WebKit2) crashes rather easily. It crashes when it is closed, but that’s not too bad. Unfortunately, it also crashes when trying to navigate to a website (shown above)! I will be working on fixing this crash first.
For those who aren’t familiar with WebKit’s code, that’s all I can really say. But if you are familiar, then keep reading. WebKit wants to know how I will fundamentally approach porting WebKit2.
short whoami
Hello! I’m Diego Roux, an undergraduate engineering student at Universidad
Iberoamericana (Mexico). Passionate about low-level stuff, OS/kernel dev,
embed libs, and more!
I’m grateful to be working under Haiku for this GSoC! So, I’ll be working
to add support for sound virtio, enhancing virtualization by working with
the VM.
I’ll be under the guidance of
@Korli. Thanks! :D
brief intro + my plans
Whenever we boot a VM with Haiku in it, it needs to ensure we have a proper
environment, emulating all physical devices we require (e.g. ethernet, sound,
video, graphics, etc); great, isn’t it? we have everything nearly as we
would on actual hardware, but as with all great things in life, this comes
with a downside, emulation is (for our purposes) computationally expensive
(not really, but it does add some unnecessary overhead).
WebKit builds can take a lot of space and time to build on Haiku.
To those working on WebKit, welcome! This blog post is primarily for those working on HaikuWebKit, Haiku’s fork of WebKit, but it may also be useful for you.
I will be covering some techniques that are useful to reduce the size of build files without significant disadvantages. I’ll also cover how to speed up linking.
Introduction
Hey There!
My name is Calisto Abel Mathias, and I am excited to introduce myself as a first-year undergraduate student at the National University of Technology in Karnataka, India. I am honored to have been accepted into the Google Summer of Code (GSoC) program for 2024 under the mentorship of the Haiku project. A huge thanks to my two mentors - Niels and Humdinger for embarking on this journey with me.
