|
|
|
|
|
|
by sephoric
2731 days ago
|
|
|
That is a great list! Autumn's API was inspired by a lot of these, so you may find some similarities, although I redesigned Autumn's API from the ground-up to be intuitive, simple and predictable, and so that it would lend a lot more easily to the built-in documentation viewer. Searching through online documentation was always one of my most sore points when using other programmable window managers, so that was one of my biggest focuses in Autumn, and one of the aspects of it I'm most happy with how it turned out. That, the developer console, and the integrated IDE (Monaco editor), are some ways that I felt I could take the next step up from earlier window managers. |
|
|
For me that is always one of the most sore points of almost every single desktop application, or at least those released this side of the millennium (older stuff tend to have actual offline documentation with them).
I don't use macOS these days (i dislike how Apple doesn't care about backwards compatibility and every time i upgrade macOS i have apps i bought break left and right - at this point almost nothing works on my oldest iMac), but thumbs up for providing your users documentation with the software they bought instead of sticking it to some wiki in a web server somewhere and hoping for the best (of course having the docs available on the web is fine and for some welcome, since they can check out what the app can do before even buying it, just not as a replacement for local docs you can pull up at any moment regardless of your internet connectivity - or even version of the software).