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?
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).
This is very cool, but somehow got myself disappointed that something I didn't know I wanted doesn't exist.
From looking at the demo and the docs...
What I didn't see in the demo was changing the order of a tab within a panel via drag-and-drop (no "allowIntraPaneTabMove"?). Also presuming you can close tabs to left, right, or all other tabs (would need tabs as list to implement this in application). Also might like to somehow manage title elision when there are multiple tabs. Also want to change pane proportions on the fly. Also assuming one can have two views of the same document in different tabs.
So many possibilities! I'll try it in some app...
Getting drag and drop right is hard, it's so much more complex than you might think.
https://assets.agentastic.ai/agentastic-dev-assets/videos/0....
- functionality/effect looks like Sublime Text origami mode
One odd thing, the library doesn't have a license associated with it (in the repo, at least).