github/atom
1
1
Fork 0
mirror of https://github.com/atom/atom.git synced 2026-01-23 13:58:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

Add Max's focus

Browse Source
This commit is contained in:
Max Brunsfeld
2018-02-20 13:39:19 -08:00
committed by GitHub
parent df3291a81c
commit df9a4c9226
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/focus/2018-02-19.md
View File

@@ -20,7 +20,12 @@
- We made a slight change of plans and decided to spend more time clarifying the overall vision for the project.
- We have a [branch](https://github.com/atom/xray/tree/roadmap) with a new README that matches our current thinking, but the Q1 roadmap is still in progress.
- We did manage to get text rendering with retina displays and non-clipped characters, but there's still work to do. We are also experimenting populating our glyph atlas with up to 4 variants of each glyph at different subpixel positions to more closely match text rendered purely on the CPU.
- Tree-sitter
- Took some time to fix unrelated regressions from the bug-bash month
- Fixed a bug where atom --wait did not work correctly on Windows (#16740)
- Fixed a bug that prevented Atom from reusing an existing window when the same path was opened twice (#16764)
- Fixed regressions in the behavior of the atom.textEditors.getGrammarOverride and atom.grammars.loadGrammar methods (#16733, #16747)
- Fixed several syntax highlighting bugs (#16642, #16643)
## Focus for week ahead
- Atom IDE
@@ -34,6 +39,9 @@
- Merge and use [atom/fuzzy-finder#335](https://github.com/atom/fuzzy-finder/pull/335), [atom/teletype-client#52](https://github.com/atom/teletype-client/pull/52) and [atom/teletype#323](https://github.com/atom/teletype/pull/323).
- Publish Teletype v0.9.0 containing the new fuzzy-finder support.
- Tree-sitter
- Fix an issue where snippets are not available when using tree-sitter (#16621)
- Start work on optimizing editing in the presence of large parse errors (#16590)
- Start work on allowing parsing to take place on a background thread
- Xray
- We will continue clarifying the overall vision with a focus on real time collaboration. This may extend beyond the scope of Xray, but is important to get clarity on before comitting to a roadmap.
- We hope to iron out the remaining issues with subpixel-positioning of glyphs to more faithfully reproduce Chrome's behavior when rendering text via the normal DOM-based code path.