| | 36 | |
| | 37 | ==== Bluetooth Stack Improvements ==== |
| | 38 | |
| | 39 | Haiku Bluetooth Stack implements basic functionality on lower and middle layers, this functionality needs to be completed and Bluetooth 2.X possibilities explored. |
| | 40 | |
| | 41 | Requirements: Bluetooth enabled Haiku system |
| | 42 | Skill set: C++, kernel development, userland development, global bluetooth stack knowledge(optional) |
| | 43 | Tasks: RemoteDevices Database, UserLand tools(Preferences), Pairing/Auth/Encryption use cases, etc. |
| | 44 | |
| | 45 | ==== Integrate our PPP implementation ==== |
| | 46 | |
| | 47 | Port the PPP implementation to our new network stack. Add phone-line modem support, including HDLC framing and VJC compression (porting both algorithms is sufficient, but make sure the license is compatible to MIT). Implement CHAP authentication. Find and fix bugs. |
| | 48 | |
| | 49 | Tickets: #812, #869, #873, #922, #923, #1059, maybe: #1057, #1058 |
| | 50 | Requirements: multi-threading basics, maybe network protocols and some kernel/drivers development, maybe UI development |
| | 51 | |
| | 52 | ==== Multi-monitor support for the app_server ==== |
| | 53 | |
| | 54 | The app_server needs to handle multiple monitors in its internal screen representation and configuration. The drawing call dispatching would need to be split up, so that drawing commands are dispatched to different Accelerants. |
| | 55 | |
| | 56 | To ease development, having two graphics cards in your computer is recommended, as none of the existing Haiku drivers currently support dual head output correctly (as the accelerant interface does not define a way to use it). |
| | 57 | |
| | 58 | Skill set: graphics drivers, application design |
| | 79 | Haiku has an NFS client, but using the out of date NFSv2 specification and the old file system API. This makes it unusable for any practical purpose. Also, the current implementation doesn't support caching, which makes it slow, and lacks xattr handling, which is very important in Haiku. |
| | 80 | |
| | 81 | Requirements: network protocols, maybe kernel development, userland development |
| | 82 | |
| | 83 | ==== Hardware 3D acceleration ==== |
| | 84 | |
| | 85 | Design or port an existing 3D driver interface. See for example the Gallium3D project. Another option is to write a compatibility layer to load binary Linux 3D graphics drivers. There should probably still be our own 3D acceleration API for drivers. |
| | 86 | |
| | 87 | Skill set: graphics drivers, API design |
