Conclusion

7 - Conclusion Writing video drivers is nice to do a while. It is very instructive and (yet) good to do when the whole structure is addressed. Sometimes writing video drivers requires the necessary imagination from the programmer, because it is difficult to test some (combinations) of things or make them testable. Also, the retrieval and understanding of the specifications is sometimes a challenge. Even if there is some documentation from a chip or card manufacturer, you still need to be puzzled regularly.

Writing The Driver

6 - Writing The Video Driver When writing a video driver, a number of issues are important: -A plan is required to indicate the order in which the components can be constructed; -There must be possibilities for testing the driver; And -The driver must be constructed in such a way that its stability is ensured as well as possible. This chapter will deal with these issues. The information given here is an important tool in actually building a video driver.

Students

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)

Students

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

Ideas

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.

Application Patterns

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]

Prepare for Publishing

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

To Create or Contribute?

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.

Setting up a Development Environment

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.

Students

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)