This year, 2 of our 3 interns in GSoC and Outreachy completed their projects
Rajagopalan Gandhagaran - Webkit2 port Preetpal Kaur (Outreachy) - Input preferences Bharati Ramana Joshi - Btrfs write support (repeated communication issues preventing the project from moving onwards)
This year, all 4 of our GSoC students completed their projects!
Cruxbox - XFS filesystem support Preetpal Kaur - Input preferences Leorize - Services kit rewrite Suhel Mehta - UFS2 filesystem support
For information about Haiku's participation in GSoC this year, please see this page.
Qualifying students can apply for a Haiku project (see the list of suggested projects below). For details about how to apply, please check out Students: How to Apply for a Haiku Idea.
The most successful Google Summer of Code projects are often those proposed by the students themselves. The following list represents some of our ideas and wishes for the project.
There are several common patterns or approaches that you will use when developing Haiku native applications. These are listed below:
These tutorials were created by DarkWyrm unless otherwise stated.
Using the Layout API [PDF] - by waddlesplash Using attributes in your application [PDF] Using attributes in Queries[PDF] Monitoring the File System with the StorageKit [PDF] Registering a new file type [PDF] Using fonts [PDF] Creating a new UI Control [PDF] Using application scripting [PDF] Adding scripting to your applications [PDF] Enabling Drag & Drop [PDF] Exposing re-usable parts of your application with Replicants [PDF] Tutorial Project: Create a text editor [PDF]
The are many tasks you should look in to before publishing your new or latest application.
Translating your application using catkeys files Create an icon for your application
When you spot a need for an application it is tempting to create a new one from scratch. The HaikuArchives contains many projects that were started as an idea, and then fell out of use.
To minimise code waste and maximise re-use, you should consider finding a project that aligns with your goals, and adding your own new feature enhancements to it, rather than default to create Yet Another Application.
The first thing you'll need to do before writing code in Haiku is to set up a development environment. How you do this will depend on whether you are developing for Haiku within Haiku itself, or from another operating system.
In future we hope to provide step by step guides for each platform. For now though, whichever of the below routes you take, see the summary: Building pre-requisities page for details.
This year, 2 out of 3 students completed their GSoC projects
Hrishikesh Hiraskar - Integrating a Git client into Trac Krishnan Iyer - SDHCI support Abhinand N - XFS support (failed as close to no code was written in the first two months)
It’s been just about a month less than six years since Haiku’s last release in November 2012 — too long. As a result of such a long gap between releases, there are a lot more changes in this release than in previous ones, and so this document is weightier than it has been in the past. The notes are mostly organized in order of importance and relevance, not chronologically, and due to the sheer number of changes, thousands of smaller improvements simply aren’t recognized here.
UEFI Booting the anyboot image 64-bit release images (such as Haiku R1/beta3) can be directly booted from UEFI when the system’s hardware supports it. While Haiku’s UEFI bootloader is at an early stage, it can be leveraged to boot a stable system.
Installing UEFI to disk Haiku can be installed to a system with an UEFI bootloader, however it is a manual process as of R1/beta3. If you boot the anyboot media from UEFI (and install as usual) your system will boot via the legacy BIOS loader.
