Go to file
John Scipione deaae5fc20 Deskbar: Persist ExpandoMenuBar
Add private BMenu::_SetMenuLayout() method. Set TExpandoMenuBar
as a friend class in BMenu to call this method. A little hacky,
but, this keeps SetMenuLayout() from being exposed as part of
the public API.

Don't destroy and rebuild the ExpandoMenuBar when switching from
horizontal to vertical mode. Instead build the TExpandoMenuBar
when the application starts and then switch it from B_ITEMS_IN_ROW
to B_ITEMS_IN_COLUMNS by using the newly added _SetMenuLayout()
method.

When we resize from vertical to horizontal, recalc the max
menu item widths, this resizes the application menu items so
that they take up the right amount of space.

Since we no longer destroy the menu bar we no longer have to
save whether menu items are expanded or not in a separate list.
Instead we can store that information in directly in
TExpandoMenuBar. This removes a lot of code.

Fixes #9350
2015-02-19 19:02:39 -05:00
3rdparty checkstyle.vim: add catch to checked keywords 2014-11-26 13:27:33 +01:00
build Add package for bonnie++ 2015-02-17 15:53:46 +01:00
data Update translations from Pootle 2015-02-14 06:29:19 +01:00
docs interface_guidelines: add a convert.sh script that uses XMLTO. 2015-02-13 11:26:28 -05:00
headers Deskbar: Persist ExpandoMenuBar 2015-02-19 19:02:39 -05:00
src Deskbar: Persist ExpandoMenuBar 2015-02-19 19:02:39 -05:00
.gitignore Update ACPICA to 20140724. 2014-08-23 16:30:50 +02:00
configure configure: Add variable to see if we're bootstrapping 2014-10-26 21:07:57 +01:00
Jamfile Add coreutils packages for x86_gcc2, x86 and x86_64. 2015-02-05 18:57:21 +01:00
Jamrules Merge branch 'gcc_syslibs' 2014-08-13 13:50:29 +02:00
makehaikufloppy Updated makehaikufloppy script, based on a patch by Rob Judd. I have no idea 2009-04-15 19:26:03 +00:00
ReadMe.Compiling Interface Guidelines: migrate to docs/, use DocBookCSS. 2015-02-12 17:08:04 -05:00
ReadMe.md ReadMe: Convert to Markdown, various cleanup. 2015-02-11 18:56:15 -05:00

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:

Contributing documentation

The main piece of documentation that still needs work are the API docs (found in the tree at src/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.