fc23c09758
Add methods to get and set "Always on top", "Auto raise", and "auto hide" which are all booleans which control aspects of the Deskbar window to BDeskbar. Set the bool to the default value initially. Check if sending the message succeeds, if so check the reply which also fills out the bool. Don't check to see if reply succeeded because the bool will only be overwritten if it did. Follow the BDeskbar convention Is...() for getter, Set...() for setter e.g IsAlwaysOnTop() is the getter, SetAlwaysOnTop() is the setter. Define new message constants to call the newly created methods. Follow BDeskbar convention: 'gtla' is used for getter, 'stla' for setter. g/s for getter/setter, tla is an all-lowercase code unique to each getter/setter pair. Copy/paste these message constants into BarApp.h unchanged. Replace four letter codes with imported message constants in BarApp.cpp and BarWindow.cpp. Much nicer than using bare codes. The new BDeskbar methods are all handled by TBarApp. The getters send back a reply message containing the bool while the setters fall through to existing setter cases.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.