张小白
c0259a448d
Upper before this PR, lower after.  This PR manually applies a MSAA to the font atlas. Before this PR, the font may seem aliased ( espeacially on low DPI monitors ), that's because `DirectWrite` and `CoreText` ( on which currently `Zed` built the whole text system ) uses different anti-aliasing strategy. The different anti-aliasing approach used by `DirectWrite` and `CoreText`:  The upper is `VSCode` font rendering result, middle `macOS`, lower this PR ( pic captured with same font face, same font size, same DPI, same physical resolution, same editor theme, and same magnification rate ). This PR brings a quality similiar to `CoreText`. What's more, from the `VSCode` image, you can see how `DirectWrite` sub-pixel anti-aliasing is performed on the edge of the glyph. Can we achieve the same rendering quality? Currently, No. `Zed` use a grayscale image to render glyph, and a sub-pixel anti-aliasing `DirectWrite` requires all RGB channels and the foreground color of the rendering glyph, which `Zed` dose not provide. So, to achieve the quality of `VSCode` font rendering, the text system of `Zed` needs much much more efforts to refactor the codes. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
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.