5e726ed442
* For the moment i still remain with the classic lateness calculus. My code wasn't perfect, but this commit fix the remaining problems from my perspective. * The first reason is that if we have a patologic latency such as adding for experimental reasons a snooze() before a SendBuffer or in the BufferReceived callback, we still can't do anything about it. If we use enqueue_time and don't send a LateProducer notice, this latency will never be detected by the API client. We can't do anything about it, and it's even better that systems with such problems are recognized as soon as possible IMO. * The second reason is that the lateness calculus described in the BeBook is done this way because the media_kit want us to adjust our timing in both early and late situations. * Realtime expect that things are always delivered under a certain time limit, if the software at the bottom doesn't meet with this requirement, it's just not realtime and things can't work in realtime. * enqueue_time has nothing to do with the performance_time. But we can still add this to the media_timed_event struct so that applications can make use of it. * Lateness was probably not used a lot in BeOS programs as it looks like a relatively new feature but i have the concern to complete our API implementation to be close to what i see was reasonably the designers aim.
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.