| | 11 | The API was largely inherited from BeOS, unfortunately the documentation for it was not released under an open source license. It can still be used as an example of what we have in mind: https://www.haiku-os.org/legacy-docs/bebook/ |
| | 12 | |
| | 13 | The idea is to give an overview of how to write applications for Haiku, by going though the different functional parts of the API (called "kits"). In each kit, there should be an overview of the functionality at medium-high level, as well as a more detailed explanation of each class and method. |
| | 14 | |
| | 15 | We expect people referring this documentation to be either seasoned Haiku programmers, using it as a reference, or programmers discovering Haiku but already having some experience writing applications for other operating systems. Therefore, we do not need to make this a course for complete begginners (the separate "Learning to Program with Haiku" book is designed for that). |
| | 16 | |
| | 17 | The Haiku API documentation is generated using Doxygen, which allows to more easily cross-reference it with the sourcecode. However, it is not stored in the same files as the sourcecode, making it easier for documentation to be worked on as a separate tasks from writing the code. You can check the sourcefiles for the documentation here: https://git.haiku-os.org/haiku/tree/docs/user |
| | 18 | |
