My two cents on the porting process: 1. Download the source from Subversion. (Hopefully Subversion is already ported!) 2. Get it to compile. (Looking at what is compiled on Windows or the Linux/GDK/Qt ports is probably most helpful. Note that none of the other projects is "feature complete", or in parity with the original port, yet.) 3. Start posting patches for review on http://bugs.webkit.org/. Smaller patches with logically-grouped changes are easier to review than One Big Patch(tm). Also note code style guidelines on http:// webkit.org/. 4. Write a browser "shell" (like Spinneret for Windows) that will provide basic browsing features. 5. Start fixing bugs. Post patches on bugs.webkit.org for review and commit. Note that there are currently five IDE/make systems in the tree: Apple's XCode (*.xcodeproj), Windows Visual Studio (*.vcproj), Bakefile (*.bkl), CMake (CMakeLists.txt) and QMake (*.pri, *.pro). I would recommend trying to reuse one of them (probably CMake or QMake), even if you have to port that software as well. It's been quite a challenge to keep all the build files in sync. Dave On Dec 14, 2006, at 3:48 AM, Ryan Leavengood wrote:

Hello,

I'm a developer on the Haiku project (which is recreating BeOS) and there is a lot of interest in the BeOS community in getting WebKit/ KHTML working on BeOS-compatible systems.

Various projects have been started in the past to do this but not much has come out of it yet.

I am emailing because it seems now that this project is interested in ports and has a decent infrastructure for helping in their creation. I would love to hear any tips, tricks and suggestions on beginning a port to a new system like BeOS.

FYI Mozilla and FireFox have been ported with reasonable success so it is not as if BeOS is a backwards and therefore hard to port to system.

Thanks, Ryan Leavengood _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev