04ba75e2e5
TL;DR our version of [HIG's Box](https://developer.apple.com/design/human-interface-guidelines/boxes) We can't use the name `Box` (because rust) or `ContentBox` (because taffy/styles/css). --- This PR introduces the `ContentGroup` component, a flexible container inspired by HIG's `Box` component. It's designed to hold and organize various UI elements with options to toggle borders and background fills. **Example usage**: ```rust ContentGroup::new() .flex_1() .items_center() .justify_center() .h_48() .child(Label::new("Flexible ContentBox")) ``` Here are some configurations: - Default: Includes both border and fill. - Borderless: No border for a clean look. - Unfilled: No background fill for a transparent appearance. **Preview**:  --- _This PR was written by a large language model with input from the author._ Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.