And now Runestone for AppKit supports moving to the line and document boundaries as well as clicking with the mouse to move to the closest location.
Maybe the next step is to support text selection. Or something more fun like line numbers.
Baby steps, y'all.
Line numbers and highlighting the selected line now works in Runestone for AppKit.
This one was a bit tricky because the view hierarchy is different between AppKit and UIKit and there's some important layering going on here to make it look the way I want it to.
On the other hand, disabling line wrapping worked without any changes 😃
Baby steps, y'all.
Taking a break from this thread tonight*. I did a few minor things that aren’t worth showing off but I’ll prioritize playing with the Quest 2 and watching Slow Horses for the rest of the evening. I need a short break 🤗
* Since I’m posting this I guess I’m not really taking a break.
Just tested syntax highlighting in Runestone for AppKit for the first time. Was happy to discover that it just works 😃
Baby steps, y'all.
Mostly got text selection, copy, paste, and cut working in Runestone for AppKit today 😃
There are still a couple of bugs in the text selection that needs to be fixed but it's getting there.
Baby steps, y'all.
Still polishing the text selection in Runestone for AppKit. Getting all keyboard shortcuts working as expected is extremely tricky but I'm getting closer. However, I've just got text selection working with the mouse so that's something 😄
Baby steps, y'all.
In case you would like to start playing around with Runestone for AppKit, you can do so already now. It’s available in the GitHub repository: https://github.com/simonbs/Runestone/tree/mac
I’m still working on this, so bugs should be expected. Don’t waste too much time reporting issues. At this point I likely know they’re there but haven’t gotten around to fixing them yet 😊
And in case you are using Runestone in your project, remember that I have GitHub sponsors setup 🫶 https://github.com/sponsors/simonbs
Got double and triple clicking to select words and lines working in Runestone for AppKit 😃
Notice that it's even possible to double click an opening or closing bracket to select everything within the brackets 🤓
Baby steps, y'all.
Word selection was a prerequisite to support right-clicking to cut, copy, and paste and with word selection in place, it was trivial to the right-click menu 😃
Baby steps, y'all.
And now Runestone for AppKit supports undo and redo too 😃
Text selection, the right-click menu, and undo/redo are things I have missed while working on other features, so it is great to finally have those in place.
Baby steps, y'all.
Hoping to fix this difference between Runestone and UITextView as part of bringing Runestone to the Mac.
TextKit, and as a result UITextView, will remove leading spaces one line fragments when wrapping lines. This ensures that line fragments align vertically.
It's going to be tricky though 🤔
This turned out to be much easier than I anticipated! 😃
Runestone will now remove leading whitespace in line fragments to match the text layout of UITextView and NSTextView much closer.
This difference has been bothering me since the launch of Runestone so it feels great to finally have it addressed.
Here are the changes for anyone interested: https://github.com/simonbs/Runestone/pull/272
The changes in this PR hides the leading whitespace in line fragments to align with TextKit, i.e. UITextView and NSTextView. See the screenshot below for a comparison. The new caretLocation(forLine...
Fixed a bug in Runestone for AppKit where it would reapply the syntax highlighting every time the window was resized, as such, causing the text to "blink”. 😃
Baby steps, y’all.
Got window cascading working 😃
I was not able to get it working without using a storyboard which I'm not so happy about. Storyboards seem more common in the AppKit-world than in the iOS-world though.
Baby steps, y'all.
Happy to see that Runestone for AppKit has a pretty decent scroll performance 😃
This was a big focus point of mine when building Runestone for iOS and unsurprisingly, I can harvest the fruits when running Runestone on the Mac too.
This is a large JSON file with absurdly long lines and scrolling is fine but not perfect but I'm happy with it as a benchmark 😊
Baby steps, y'all.
Need to figure out how I can avoid the line numbers becoming "clipped" when scrolling past edge on the left-hand side 🤔
I have previously worked around this by adding the line numbers on top of the NSScrollView but now I'd like the line numbers to be part of the scroll view's document view.
This one is tricky…
Adding the line numbers as a floating view to the NSScrollView works fine until the find/replace panel is presented. Why does it have to be so hard to work with scroll views in AppKit? 😭
In UIKit I just add the line numbers to my scroll view and manually offset them when the user scrolls to make them appear sticky. That *almost* works in AppKit but the UI will sometimes flicker and get clipped in a way I don't like 😔
This thread is going to be a bit quite the next few days as I rework some of the internals of Runestone to make it easier to support both the AppKit and the UIKit implementation. These changes should make the implementation of line numbers and find/replace a bit prettier, hopefully.
Baby steps, y'all.
As I move code out of large types in Runestone, I struggle to find proper names for those types. Here are a few examples.
- What's the name of the type coordinating a text change? TextEditService? TextEditController? TextEditor?
- The type laying out line fragments? LineFragmentLayouter? LineFragmentLayoutManager? LineFragmentLayoutController?
- The type managing the content size of the scroll view? ContentSizeManager? ContentSizeService?
I'm spending way to much time on this 😑
Refactoring my code to make it less it easier to maintain in the long wrong and I feel like I have forgotten how to write code. I'm like
"What's the best way to get notified when this object changes? 🫤💫”
Making some progress on bringing the Composition Root pattern to the Runestone framework 😃
On one hand it's stressing me out a bit that I'm spending so much time refactoring Runestone's code but on the other hand, I think I'll appreciate this effort for several years going forward.
Today I made a small breakthrough in the clean up of the Runestone codebase. It feels so good and it's such a relief 😃😌
The past week I have written very little code on Runestone because I have been trying to figure out how I want to structure the code, each component's dependencies, and the communication between them. Today I realized that the question was right in front of me the entire time: Combine.
Refactoring large parts of Runestone to isolate logic and make it communicate using Combine. This morning I got cursor movement working again and it feels like a tiny milestone 😄
Baby steps, y'all.
Lately I've been struggling to work on Runestone. I haven't had the motivation. Maybe I was a little burned out from working on it *very* intensively for a period of time.
Now I'm on vacation and slowly finding the motivation again. I'm hoping to progress a little on the refactoring each day but not so much that I end up not having a vacation and being burned out again.
The past month or so I have been working on a big refactor of Runestone to split up some types in smaller types that are easier to unit test. Now I'm finally harvesting some of the fruits 😃
Baby steps, y'all.
Took a stab at supporting more caret shapes in Runestone for Mac and it now supports the vertical bar, underline, and my favorite caret shape: the block.
It was tricky to support the block caret as I need to draw the character the caret is on top of to ensure it is visible. As such, this is still very experimental but it’s a good start 😃
Baby steps, y'all.
I struggle to make the text within the block caret align exactly with the underlying text. It's most notable when the caret is on top of an emoji.
I won't ship this unless I can get it pixel perfect but I'm running out of ideas to try 😬
I am drawing the caret on top of the original text and then I’m drawing the character that is below the caret on top of the caret again. This makes it seem like the caret is below the character.
I considered drawing the caret behind the text instead. However, the selected character will need to be drawn in a distinct color so the caret doesn’t hide it. I’d like to avoid redrawing the entire line so I thought it’s smart to redraw only that character on top of the caret.
The character within the caret now aligns perfectly with the text below it. Now I just need to prevent emoji from being filled with color 😄
Baby steps, y'all.
Supporting the block caret turned out to be trickier than anticipated but it seems to work now 😃
Regular characters, invisible characters, and emoji now all show on top of the caret in the correct colors.
Baby steps, y'all.
Working on supporting the block caret in Runestone for iPhone and iPad 😃
This is tricky because UIKit manages the caret but I need a custom view to show the block caret. So I need to hide UIKit's caret and add my own. Next up I need to ensure it works with the floating caret that's shown when long pressing to drag the caret to another locaton.
Baby steps, y'all.
The three shapes of carets are working on iOS now 🙌
Someday Runestone users will be able to choose between the Vertical Bar, Underline, and Block.
Runestone's custom caret now supports iOS' standard behavior where only the floating caret is shown when dragging the caret around unless the floating caret is far from where it'll land if it's released, in which case both the floating and the underlying caret is shown.
This will be a setting in Runestone, allowing users to have the underlying caret displayed all the time for easier navigation.
Baby steps, y'all.
@christianselig @simonbs I think the ‘character to be affected’ should show on the block cursor at the insertion point as it jumps to each point, not the floating one. It doesn’t have to be the same colour or a reversed colour, just contrasty enough.
*Maybe* you could put it on the floating one when the user pauses the movement momentarily, but I think the floating cursor is subconsciously the ‘where my eyeballs are going’ and having the flashing characters there is distracting.
@simonbs that is fun, if you want to keep it, then perhaps view it as an accessibility thing, highlighting the exact letter you are over. I could see that being useful in certain scenarios.
That said, to me, that is too busy and it adds motion which my eye would be drawn to, rather than the surrounding text, where I would most likely expect it to be.
@simonbs The only way this will work is if you control the CTLineDraw (and typesetter) in both the screen and bitmap context.
As far as masking is concerned, this will be helpful: https://stackoverflow.com/questions/8126276/how-to-convert-uiimage-cgimagerefs-alpha-channel-to-mask/39949611#39949611
@amyworrall Yes but I’ll need to draw text on top again. For example, when my white caret is behind a white character then that character becomes unreadable. Text editors solve this by changing the color of the character. I’m thinking one of doing that is having three layers, from back to top:
1. The original text.
2. The caret.
3. The letter that the caret is on top of redrawn in a different color.
Simon B. Støvring
Andrew Eades
Amy Worrall
Tibo Loete
Daniel
Jakob Haug
Pasi Salenius
Christian Selig
Jason Meaden
Brendan Thompson
Beyond Doomscrolling
ryan!
Leon Cowle
Sir David Nielsen
Ben Scheirman
Marcos Kirsch
Craig Hockenberry
Curtis Hard
lawbecke