-
Notifications
You must be signed in to change notification settings - Fork 11
Add guide dynamic libraries #105
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
base: main
Are you sure you want to change the base?
Conversation
docs/Chords.rst
Outdated
|
|
||
| The same chord input can have a unique output in each dynamic library. | ||
|
|
||
| For example, the chord: ``ar`` can output: |
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 want to lean away from using 2 letter inputs as examples because we discourage common bigrams as chord inputs, but, I like this example. I see no issue with it, but, just a note for you
docs/Chords.rst
Outdated
| To switch between dynamic libraries, we add library chords in the device | ||
| manager's library editor: https://charachorder.io/config/chords/ | ||
|
|
||
| First we add a base library chord. This exits any dynamic library. |
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.
Add a comma after "First"
docs/Chords.rst
Outdated
| * chord: ``lib`` | ||
| * output: ``{action: base library}base`` | ||
|
|
||
| Then we add a dynamic library chord. |
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.
Add a comma after "Then"
docs/Chords.rst
Outdated
| #. Add an impulse chord: ``i + DUP`` | ||
| #. At the impulse output prompt, type: ``arm`` | ||
| #. Press: ``enter`` | ||
| #. At the impulse input prompt, chord: ``ar`` |
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.
Change the chord input to our chord notation, "a+r"
docs/Chords.rst
Outdated
| on a new line. We'll make it easier to erase the library name in the | ||
| next section. | ||
|
|
||
| #. Add an impulse chord: ``i + DUP`` |
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.
MODIFY
"Open the impulse chord menu:"
docs/Chords.rst
Outdated
| next section. | ||
|
|
||
| #. Add an impulse chord: ``i + DUP`` | ||
| #. At the impulse output prompt, type: ``arm`` |
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.
ADD
"... type your desired output:"
docs/Chords.rst
Outdated
|
|
||
| .. note:: | ||
|
|
||
| It doesn't overwrite an existing chord on the base library. |
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.
REVISE
"Adding a chord in a dynamic library doesn't overwrite..."
docs/Chords.rst
Outdated
| .. note:: | ||
|
|
||
| It doesn't overwrite an existing chord on the base library. | ||
| Because it adds the dynamic library chord as a prefix. |
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.
Join this sentence with the previous one.
"..on the base library because it adds..."
docs/Chords.rst
Outdated
|
|
||
| Now, while we're in the dynamic library: ``lib1`` | ||
|
|
||
| * when we chord: ``ar`` |
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.
Chord notation, please "a+r"
docs/Chords.rst
Outdated
| * when we chord: ``ar`` | ||
| * it outputs: ``arm`` | ||
|
|
||
| #. Switch to the base library, with the chord: ``lib`` |
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.
REVISE
"Switch to the base library by using the base library chord we created earlier:"
docs/Chords.rst
Outdated
|
|
||
| Now, while we're on the base library: ``base`` | ||
|
|
||
| * when we chord: ``ar`` |
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.
Chording notation
docs/Chords.rst
Outdated
| Select the dynamic library name automatically | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| This isn't required, but it's a convenience. |
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.
REVISE
"This step isn't required..."
docs/Chords.rst
Outdated
| When we switch between dynamic libraries, the library chord outputs the | ||
| library name. It's an extra step to erase the library name manually. | ||
|
|
||
| Instead, let's select the dynamic library name automatically, by adding |
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.
Remove the comma
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.
There are two commas 😄
I'm guessing the second comma, since the previous suggestion: #105 (comment)
didn't have a comma before "by":
"Switch to the base library by using the base library chord we created earlier:"
CCMaverick
left a comment
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.
Easy to understand manual. I never took the time to learn this, but now I know how to do it lol. Minor changes
d44cd7c to
959e2d6
Compare
|
|
||
| Dynamic Libraries | ||
| ~~~~~~~~~~~~~~~~~ | ||
|
|
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'm thinking we give a brief explanation of what Dynamic Libraries are.
"Dynamic Libraries are a way with which you can store multiple different chord libraries on a device. You can switch between the different libraries by using a pre-defined chord. With Dynamic Libraries, you can use the same chord to produce different outputs, depending on what library is currently active."
docs/Chords.rst
Outdated
| * ``Eneot of Draconia`` in a library for Novel writing | ||
| * ``OnePlus`` in a library for Cell Phone blogging | ||
|
|
||
| Add dynamic library switching chords |
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.
Let's rename this to Dynamic Toggle Chords"
I think Dynamic toggle is pretty clear and unique enough that it won't be confused with other CC functions. You can add a note explaining this name immediately before the instructions in the section below. "We call these chords Dynamic Toggles." I kinda like your "library chords" but that can be confused with general chords in a library, which is how I was reading it until I really thought about it lol. I thought you meant to simply add a chord into the library, but then I realized that you're calling them Library chords... so, if I was confused I can imagine others may get confused as well.
docs/Chords.rst
Outdated
| To switch between dynamic libraries, we add library chords in the device | ||
| manager's library editor: https://charachorder.io/config/chords/ | ||
|
|
||
| First, we add a base library chord. This exits any dynamic library. |
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.
REVISE:
"...base library chord. This is the Dynamic Toggle that we'll use to exit any dynamic library and return to the base library."
docs/Chords.rst
Outdated
| * chord: ``b+a+l+i`` | ||
| * output: ``{action: base library}base`` | ||
|
|
||
| Then, we add a work dynamic library chord. |
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.
Because we're dealing with new vocabulary that we're making up, we need to be careful with being extremely clear what each word means. "work dynamic library chord". Does that mean a working library? As in, simply a Dynamic library? Or does it mean something else? I propose revising to:
"Then, we add a Dynamic Toggle for a library used at work."
docs/Chords.rst
Outdated
|
|
||
| .. note:: | ||
|
|
||
| Both the chords ``b+a+l+i`` and ``w+l+i+b``, and the dynamic library |
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.
In the spirit of being super clear, consider:
"The chords we used in the examples above (b+a+l+i and w+l+i+b) and their outputs (base and wlib) are merely examples; they don't have to be exactly that. You can make the chord inputs and their outputs whatever you want, as long as you include the dynamic library action in the chord output."
docs/Chords.rst
Outdated
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| #. Switch to the work library, by chording: ``w+l+i+b`` | ||
| #. It switches to the work library and outputs its name: ``wlib`` |
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.
ADD: "in plain text." to the end of this last sentence.
docs/Chords.rst
Outdated
|
|
||
| #. Switch to the work library, by chording: ``w+l+i+b`` | ||
| #. It switches to the work library and outputs its name: ``wlib`` | ||
| #. You can ignore the name, erase it or just press ``enter`` to continue |
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.
In the spirit of keeping readable and consistent documentation, I like making any function keys and modifiers all caps. Idk how they appear on .io, but I really thing using all caps is a useful way to differentiate between modifiers and text. Thoughts?
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.
Uppercase key names, modifiers, etc. #116
| Add a chord in a dynamic library | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| #. Switch to the work library, by chording: ``w+l+i+b`` |
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.
Attempting to keep consistency, all of these should either have a period at the end, or not. I don't have a preference (I think), but we should be consistent.
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.
The period was removed after the only list item with a period at the end.
docs/Chords.rst
Outdated
| #. Switch to the work library, by chording: ``w+l+i+b`` | ||
| #. It switches to the work library and outputs its name: ``wlib`` | ||
| #. You can ignore the name, erase it or just press ``enter`` to continue | ||
| on a new line. We'll make it easier to erase the library name in the |
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.
REVISE:
"...We'll get rid of the printed library name in the next section."
docs/Chords.rst
Outdated
| * when we chord: ``r+a+l`` | ||
| * it outputs: ``realtor@email.com`` | ||
|
|
||
| #. Switch to the base library by using the base library chord we |
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.
REVISE:
"...using the base Dynamic Toggle that we created earlier:"
| * when we chord: ``r+a+l`` | ||
| * it outputs: ``really`` | ||
|
|
||
| Select the dynamic library name automatically |
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.
How about we make this a dropdown?
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.
With the last section as a dropdown.
The last section might be overlooked.
The dropdown box with a right arrow on the right side, might be seen as just another navigation button, like the previous and next buttons below it.
And if a link to the last section, is added in the previous section:
We’ll get rid of the printed library name in the next section
Clicking on the link scrolls us to the bottom of the page, but it isn't obvious that the link is referring to the dropdown at the bottom of the page.
Without a dropdown.
You can't miss the there's another section when scrolling down the page.
Clicking the link: next section
Scrolls the section header: Select the dynamic library name automatically
to the top of the page.
docs/Chords.rst
Outdated
| library name. It's an extra step to erase the library name manually. | ||
|
|
||
| Instead, let's select the dynamic library name automatically by adding | ||
| these actions to the end of the library chord output. |
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.
REVISE:
"...end of the Dynamic Toggle chord output."
docs/Chords.rst
Outdated
| {release_next}{left_shift} | ||
| The number of ``{arrow left}`` actions should match the number of | ||
| characters in the base and dynamic library names, in this case we used |
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.
REVISE:
"...in the dynamic library's name; in this case, we used..."
CCMaverick
left a comment
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.
Some comments for your consideration.
- Replaced the two letter chord with a three letter chord - Changed the image format from .webp to .png, because GitHubs diff doesn't support webp, with png the images are visible while reviewing a PR on GitHub.
Added an introduction. Changed: Dynamic Library Switching Chords And: Library Chords To: Dynamic Toggles Uppercased key names: ENTER, BACKSPACE Added images: Base Library Action Dynamic Library Action Dynamic Toggle chords without selecting the library names
959e2d6 to
7d5f2b2
Compare
|
Ready for review |
No description provided.