GSoC 2019 Webkit2 work #4

Bulk import without cleanup. The goal is only to preserve the next commits in the GSoC 2019 webkit2 branch.

Again, no cleanup is attempted. Just archiving the GSoC 2019 WebKit2 work in the next commits

This lets us use our native APIs to reserve address space without allocating memory for it immediately. Gets HaikuLauncher down to about 30MB of RAM used to display Google homepage, instead of 40MB before on 32bit systems. Untested yet on 64bit but it should free about 1GB there.

Replace our broken implementation by one done by waddlesplash based on the curl one: - Does not need to run two threads - Does not crash - Supports SSL There is one limitation: we don't have a way to wait for a socket to be either readable or writable. So get away with timeouts for now. I'll revisit that after I figure out a way to add a WaitForReadableOrWritable to BSocket and BSecureSocket (trying to not break the ABI while doing so).

Thanks to the work done on updating to webkit2, we now have working "forwarding headers" generation. This means the public headers for WebCore are copied to a directory where WebKitLegacy and WebKit2 can easily locate them. This allows to cleanup a lot of the include path tricks we were playing to get things working before.

This completes the cleanup of the forwarding headers setup. I had missed these the last time because I had not done a full clean build.

Add a static_assert to make sure pid_t fits there. Add conversion functions but I think they will not be needed (C integer promotion will do the magic)

…string Note:destructors not handled yet

For now have ignored the case of posting a message to main run loop. So it isn't doing much yet.

…ructure

Who wants to use fork/exec when we have much nicer native APIs?

We need a MIME signature so the roster can find it.

- Added a message handler to look out for incoming messages to runloop - Created new aux support so we can attach all handlers to the main apps looper - Added a message stashing feature so it stashes the messages and interprets them when the loop is ready to run - used maps to store loopers and BApplications to forward message to appropriate loopers - Created a message from ui process to network process that notifies the pid of webprocess - Added NetworkSession so it doesnt crash

- Add minimal support for ANGLE as build is broken when disabling it - Fix various minor things in Haiku specific files - A bit more cleanup of include files and forwarding headers management

1)This makes few important changes in adding the view 2)Partial mouse events which is kept aside now as main focus is put on webpage rendering

1) Few callbacks for finished loading and forward and backward stop etc is now fully functional 2) status text is partially done 3)shared memory done with mapping part pending(i need to understand a little bit more)

Fix various include path, do not include ANGLE headers when not needed. Some headers are added to the forwarding headers that probably shouldn't need to be there (date time chooser stuff, and not sure about image and image buffer). But it gets things working at least and it's more clean than what we had before.

1) removed unwanted comments 2) removed unwanted methods

1) Loading, changing title and adding redirected url are added to minibrowser 2) Get data and run on main thread - fixes network process run on main thread problem

1) Put widgets in window thread 2) webkit events on main thread

1) Enabled 3D Rendering 2) Shareable Bitmap to get data and initialize a bitmap 3) Added few drawing mechanisms to webview 4) Backing store update

Use a NativeImagePtr so the constructor will automatically initialize it.

We still need it for now and it's not that hard to keep it working. Link it with OpenGL and disable coordinated graphics as we don't need that for now.

1) Loading, changing title and adding redirected url are added to minibrowser 2) Get data and run on main thread - fixes network process run on main thread problem

1) Removed that painful wait between network and webprocess connection 2) Resizing a webpage ( very slow )

1) Cleanup all the unwanted debug messages 2) More predictable rendering Next commit would focus on Indentation

…issue

1) Inconsistent use of spaces and tabs I had to clean up this manually as i couldnt find a good extension So i will clean even more files if i come across them

1) Moved handhskaing as a part of internal WebView API 2) Placed Invalidation right after backing store changes i think this is the best place to invalidate- now paints without having to switch workspaces

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GSoC 2019 Webkit2 work #4

GSoC 2019 Webkit2 work #4

Commits on Jan 28, 2021

GSoC 2019 Webkit2 work #4

Are you sure you want to change the base?

GSoC 2019 Webkit2 work #4

Commits on Jan 28, 2021