Preparing the release announcement blog post is always quite a bit of work (despite some help from the robot).
Posts by Karl Traunmüller
The source editor Find panel is now also in place on Windows: github.com/ktraunmuelle...
Quick overview of upcoming milestones:
- release 0.7 will bring syntax highlighting, code completion, and other source editor improvements
- release 0.8 will bring inspector panels and a visual table editor to Windows
- release 0.9 will bring a graphical formula editor
github.com/ktraunmuelle...
We're getting close to the Windows & macOS 0.7 release! Maybe another week or so. github.com/ktraunmuelle...
The new source editor now features a Find panel (the same one used in the WYSIWYG editor). Replace functionality is planned for an upcoming release. github.com/ktraunmuelle...
I finally replaced the garish app bar toggle buttons with something nicer looking. This improvement will be shipped with the upcoming 0.7 release github.com/ktraunmuelle...
I ended up implementing proper glyph run splitting for whitespace highlighting. I think the result justifies the slight extra cost.
This is the low-overhead version: spaces and tabs are simply rendered as part of the containing glyph run. That's why they take on the styling of the run. For newlines, a synthetic glyph run is created at layout time. The other, more expensive option would be to split glyph runs around whitespace.
Another example
Experimenting with whitespace rendering (github.com/ktraunmuelle...)
I am experimenting with indicating the focused scope using an unobtrusive side bar (instead of the previous masking approach). What do you think?
I went over the new "Go to Line" panels on macOS & Windows again, and turned them into lightweight floating panels. github.com/ktraunmuelle...
Added matching brace highlighting to the new source editor github.com/ktraunmuelle...
With the code completions popup code now largely shared between macOS and Windows, updating the Windows code completions UI to match the Mac app was quick work.
I added an optional help text for command options. I will leave it at that for now, but created a ticket to improve the option values selection UI/UX later: github.com/ktraunmuelle...
Oh, Ok, thanks, I wasn’t aware of that. I will renew the certificate.
What’s the problem?
Experimenting with a two-pane layout for the code completions popup. I think I like that better, more space for details.
Tweaking the new code completions UI
I refactored the code completions code to have all logic, controllers & models in the shared Core library, and only have a thin UI layer in the macOS & Windows apps. Also, the UI is getting a touch-up in the process:
The existing code completion infrastructure (from the old source editor) is mostly hooked up with the new source editor on macOS, and it's also coming together on Windows. github.com/ktraunmuelle...
Added a "Go to Source Line" panel on both macOS & Windows: github.com/ktraunmuelle...
Added issue markers to the source editor's vertical scroll bar: github.com/ktraunmuelle...
After implementing and testing syntax highlighting on macOS, it worked right out of the box, with zero additional changes needed, on Windows as well:
Next up: tweak the colour scheme, and profile the implementation.
Syntax highlighting making its first appearance in the new source editor! 🎉 The implementation fits nicely with the editor’s glyph run-based architecture.
One strategy I found can make a big difference w.r.t. success or failure is to go in smaller steps.
Codex has completely changed the way I work. After less than an hour of design discussion and exploring options, I have agreed with Codex on a detailed, focused plan for how to add syntax highlighting to the new source editor.
And here's soft line-wrapping in the Windows app.