3123432674
... to better match BeOS. Up until this point we have drawn buttons with a perfectly smooth linear gradient that was nicely provided by Stippi. However, BeOS used a more stylized gradient instead. This commit seeks to reproduce this stylized gradient on BeDecorator adjusting itself for larger button sizes. Consolidate and correct colors. button, light1, light2, and shadow1 colors are the same on close and zoom buttons. Zoom has a lighter shadow2 than close button. Try to get as close to the colors used on BeOS as possible. Added comments indicating the colors used on BeOS in active and inactive states for future reference. light1 color stays grayscale if grayscale, otherwise skews non-blue. This replicates how BeOS worked. Fill with window tab color before drawing: lose B_TRANSPARENT. Undraw the bottom left and top right corners of bitmaps in the unpressed state. BeOS did not do this (usually), but it should have as it closes the ring. Define a bunch of bitmaps and use them as stencils to write into ServerBitmaps 1 or 2 colors at a time. Update close and zoom button down states. When the button is pressed rotate bitmap by 180° by reading the source bitmap in forwards while writing destination bitmap out backwards. This allows the dark part to be draw in the top left while the light parts are drawn in the bottom right. (opposite of unpressed) Don't draw the parts of the big zoom square that are obscured by the small square. private _CreateTemporaryBitmap() method stolen from AlphaMask.cpp to create temporary ServerBitmaps and zero them out. Store the pointers on the BeDecorator class and then release them in the destructor method when the class object is deleted. Initialize the ServerBitmaps in the ctor and set fCStatus. On failure set to B_NO_MEMORY and fallback to drawing a linear gradiant. This will most likely never happen but just in case it does we want to avoid crashing. A few 80-line char fixes Change-Id: Ic81837aa387f05b04dda3e1ff76fdf103c93f8e8 |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
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.
Contributing to our infrastructure
See Infrastructure.