Aren/haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
53,432 Commits 9 Branches 0 Tags 473 MiB
C++ 52.9%
C 45.9%
Assembly 0.4%
HTML 0.3%
Python 0.1%
e837ee8bc6
Go to file
Michael Lotz e837ee8bc6 BView: Fix destruction order of layout items. 
Because of the virtual hooks a BLayout must never be destroyed while it
still has layout items. If these items are only removed from the layout
in its destructor, the subclass version of hooks like ItemRemoved() are
not called anymore. This lead to leaks because many BLayout subclasses
use the ItemRemoved() hook to clean up associated data (as is suggested
explicitly in the BLayout documentation).

In the same line of thought, a BLayoutItem must never be deleted when it
is still attached to a layout, as it similarly has virtual hooks like
DetachedFromLayout() that can not be called at this point anymore.

The destructors of BLayout and BLayoutItem now have debugger calls in
case these conditions are not met which should help to avoid
accidentally introducing such hard to debug issues.

To ensure the correct destruction order the sequence is now:

* Destroy the child views first. This cleans up their layout items while
  the layout tree is still intact.
* Unset the view layout before removing layout items so it can properly
  detach from the layout instead of just deleting it.
2015-04-15 00:34:07 +02:00
3rdparty checkstyle.vim: add catch to checked keywords 2014-11-26 13:27:33 +01:00
build x86: Update BePDF, Pe,Vision packages. Add libsanta package. 2015-04-13 22:28:32 -04:00
data Update translations from Pootle 2015-04-11 06:27:18 +02:00
docs Fix some typos and whitespace in BLayout docs. 2015-04-15 00:30:55 +02:00
headers BLayoutItem: Add RemoveSelf() convenience method. 2015-04-15 00:34:05 +02:00
src BView: Fix destruction order of layout items. 2015-04-15 00:34:07 +02:00
.gitignore Update ACPICA to 20140724. 2014-08-23 16:30:50 +02:00
configure arm: Initial Cubieboard4 work 2015-04-11 16:53:04 -05:00
Jamfile Added netcat packages for x86 and x86_64, use them. 2015-03-03 22:49:00 +01:00
Jamrules Merge branch 'gcc_syslibs' 2014-08-13 13:50:29 +02:00
makehaikufloppy
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

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:

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.