This is excessively beautiful, both the website and the library's UI.
But I have to ask: what's the rationale on dedicating such an elaborate and gorgeous website for just a library? Are you hoping to get hired for web design? Are you seeking fame and repute? Do you merely do it for the love of the game? Why, for the love of all that's good, pray tell why put all this effort into mere documentation?
This is very interesting, I haven’t touched macOS development for quite a while but it’s good to know that libraries are still being written for both AppKit and SwiftUI on macOS.
I do feel that this library would benefit from an explanation on why this was needed. AFAIR AppKit already provides a native tabbing API where you can “just” (that “just” is doing a lot of heavy lifting) implement a few delegate methods and you get tabbing behavior for free, especially on document-based apps. (Sorry, I do not remember the specifics, it might have been a tad more difficult)
I’m not updated on the SwiftUI equivalent, but I would imagine that a similar API would exist much alike API for multiple windows or multiple documents.
I think everyone would benefit from a “why” explanation (which I definitely think would exist, since I’ve used too many AppKit APIs in pain), and also some screenshots for a demo app (so that we can expect how it would look and how much the look and feel would deviate from the native counterparts).
You're not the only one. I first assumed it was a library when I was scanning the headlines, but then when I started opening up tabs moments later I thought it added tabs and splits to existing apps. I remember something that brought tabs system-wide to Windows so it's not even too crazy of an idea.
This is excessively beautiful, both the website and the library's UI.
But I have to ask: what's the rationale on dedicating such an elaborate and gorgeous website for just a library? Are you hoping to get hired for web design? Are you seeking fame and repute? Do you merely do it for the love of the game? Why, for the love of all that's good, pray tell why put all this effort into mere documentation?
This is very interesting, I haven’t touched macOS development for quite a while but it’s good to know that libraries are still being written for both AppKit and SwiftUI on macOS.
I do feel that this library would benefit from an explanation on why this was needed. AFAIR AppKit already provides a native tabbing API where you can “just” (that “just” is doing a lot of heavy lifting) implement a few delegate methods and you get tabbing behavior for free, especially on document-based apps. (Sorry, I do not remember the specifics, it might have been a tad more difficult)
I’m not updated on the SwiftUI equivalent, but I would imagine that a similar API would exist much alike API for multiple windows or multiple documents.
I think everyone would benefit from a “why” explanation (which I definitely think would exist, since I’ve used too many AppKit APIs in pain), and also some screenshots for a demo app (so that we can expect how it would look and how much the look and feel would deviate from the native counterparts).
The website already has a demonstration of what this does that native tabs don’t do and how they look.
- library
- functionality/effect looks like Sublime Text origami mode
I don't know why, but I thought this was going to sandbox style tab/split support for the all the baselines macos apps.
This is very cool, but somehow got myself disappointed that something I didn't know I wanted doesn't exist.
You're not the only one. I first assumed it was a library when I was scanning the headlines, but then when I started opening up tabs moments later I thought it added tabs and splits to existing apps. I remember something that brought tabs system-wide to Windows so it's not even too crazy of an idea.
Easter egg: Click the logo!
The title really should include "library"...