-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: studio features list #2598
docs: studio features list #2598
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for starting on this!
Other items planned, as part of the "configuring behaviors" is tap-dance and macro editing support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is settled already I don't want to re-open this, but is there a major difference between "configuring reserved X" vs. "defining new X" from an end user point-of-view? Also see the final comment here as related to this.
docs/docs/features/studio.md
Outdated
|
||
| Studio Status | **Feature or Capability** | | ||
| :-----------: | ------------------------------------------------------------------------------------------------- | | ||
| ✅ | Making keymap changes while keyboard is in use | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this is necessary. Is it just to constrast with flashing a new keymap?
docs/docs/features/studio.md
Outdated
| :-----------: | ------------------------------------------------------------------------------------------------- | | ||
| ✅ | Making keymap changes while keyboard is in use | | ||
| ✅ | Making changes while connected via USB | | ||
| ✅ | Native app for: Windows, Linux, MacOS | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar question for this one, seems like it shouldn't be in the feature list and is already mentioned below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm ok if this isn't included in the list. It's not really a "feature" per se.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of the possible features that Studio could be extended with in the future when mentioning this and the previous point. For completeness I felt it's nice to have them listed in that case.
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com> Co-authored-by: Peter Johanson <peter@peterjohanson.com>
50fc89e
to
82110fa
Compare
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com> Co-authored-by: Peter Johanson <peter@peterjohanson.com>
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com> Co-authored-by: Peter Johanson <peter@peterjohanson.com>
Trying to resolve studio 70.
Likely there are things that I've missed and need to be listed. I think this table makes the most sense in this page, at least for now.