Changes between Version 32 and Version 33 of GoogleSummerOfCodeIdeas

Jan 22, 2011, 9:12:38 PM (9 years ago)



  • GoogleSummerOfCodeIdeas

    v32 v33  
    5353    A port of VirtualBox to Haiku, would allow developers and users to run another operating system within Haiku. [ Preliminary VirtualBox port to Haiku]
    55     * VirtualBox guest additions for Haiku
    57     This is to improve the end-user experience of running Haiku within VirtualBox.
     55    * Enhancements for Virtualization Software
     57    Haiku works nicely both on real hardware and virtualized machines, but lacks most of the so-called "guest additions" that allows smoother integration with the host. This include changing resolution on window resize, mouse automatically switching from host to guest and back, file sharing. Write such a guest addition package for virtualbox or/and vmware
     59    * TTY Layer
     61    The TTY layer is needed for proper serial port support in Haiku. Until now the serial port was reserved for kernel debugging, but it is now time for proper userland support. Rewrite the API that was available in BeOS R5, and make sure it can be used with a real serial port. USB to serial converter may or may not be included.
     63    * Fix and improve Haiku's mail system (which tickets exactly has yet to be decided).
     65    Haiku features an integrated mail management system allowing to manage your mail using Tracker, the file explorer. This system needs some improvements and updates.
     67    * Gallium3d
     69    Gallium3d is a software stack allowing faster hardware acceleration in a more cross-platform way. Some work was started to make it run on Haiku, but it lacks a kernel module for handling DRM, so the drivers upper in the stack can plug to it. Write such a module and bring 3d acceleration to Haiku.
     71    * Language bindings in SWIG
     72            * Python
     73            * perl
     74            * ...
     76    Scripting languages should be able to use the system API directly. Python and Perl have an object-oriented approach that would allow using the Be API and using the full power of the Be API right inside your scripts. This includes displaying windows, but also accessing the locale kit, or other native stuff.
     78    In previous years, it has been discussed to utilize a dual-layer approach: First to use SWIG to generate uniform bindings and then to have a more natural syntax that binds to the SWIG bindings.