2b6ccde030
... such as virtual directories or read-only media. Also applies to open/save panels. Menu items disabled on read-only volumes: * New > * Duplicate * Move to Trash * Move To > * Cut * Paste Other reasons a menu item is disabled: * Duplicate, Move To Trash, Cut, Copy, Move to >, Copy to >, Create link > and Identify require a selection. * Paste requires something in your clipboard. * Edit name requires a single item is selected. Edit name is permitted on a read-only volume so that you may copy the name. However the name is not editable, you may only select and copy. Pop system folder warning dialog on Edit name commit instead, this way you won't see the dialog if you just want to copy the name. Move "Create link here" option last in the right- click drag menu. Disable "Move here" if source or dest is read-only, rest if dest is read-only. Ignore Paste to virtual directory, (even more) but permit Edit name. Allow drag-and-drop to virtual directory but alert and disable all right-click drag menu items like other read-only directories. Tint window backgrounds on all read-only windows darker, not just on virtual and query folders. Automatically switch the background color as you navigate in and out of read-only folders. Fix highlight color on column resize when background color is not white. Fix "reverse video" effect so that the highlight color is the inverse of the background color. On Desktop however, highlight color is always black or white. Do not alter focus in save dialogs after initial focus on the file name because focus on the pose view is required for cut/copy/paste to work. Make Edit Name work in file open/save dialogs and make Cut/Copy/Paste work while editing file name. Make Select all work in Edit name. Duplicate code cleanup: NameAttributeText::CommitEditedTextFlavor() and HeaderView::FinishEditingTitle() call common EditModelName() function in FSUtils. RealNameAttributeText inherits from NameAttributeText and calls its inherited CommitEditedTextFlavor() method. The alert text is defined in just one place in FSUtils ShouldEditRefName() instead of three. Consequently file name changed in the info window can now be undone. Change-Id: I3a78960057b8fb42d1f71af2ec3c808754c9b314 Reviewed-on: https://review.haiku-os.org/c/haiku/+/6357 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: waddlesplash <waddlesplash@gmail.com> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| lgtm.yml | ||
| 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 web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
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.