-
Notifications
You must be signed in to change notification settings - Fork 67
Implement selection menu location #94
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
Conversation
@pgaskin I'm afraid I have no idea what this feature is, so not sure what you want me to do. |
|
This is for adding items to the selection menu, with support for substituting the selection (with many options) into action arguments. See the documentation in the changes tab. |
|
A quick test w/ Wiktionary appears to handle url encoding just fine, despite the pages themselves being stored with underscores in place of spaces. |
I'll add that as an example (I might also add some custom CSS to clean it up a bit). How did you find the documentation from the perspective of a user? Also, how many items can the screen on your Forma fit at once? I can fit around 4 on my Aura2, and I haven't tested it on my Clara yet.
That gave me an idea: transformation flags for title-case, space-removal, and spaces-to-underscores. This'll be useful for a bunch of wikis and so on. |
The examples definitely help, which means viewing it as a diff with both close together did, too, so, maybe a human-readable recap at the end of the token listing might be helpful, e.g.
No idea, that was on the H2O ;p. That menu probably has weird positioning constraints, though, so it's probably hard to give a definite answer besides "not many". Not that it needs much, anyway ;).
👍 |
|
Also, possibly naming the token groups with something other than letters that can be used inside of some of them might help avoid confusion? (say, 1, 2, 3 instead of A, B, C). |
|
And make the fact that "nothing" is a valid token outside of an example ;). |
|
Random other idea: possibly naming the token themselves with something vaguely related to what they do (like the escape ones), àla ZSH: http://zsh.sourceforge.net/Doc/Release/Expansion.html#Parameter-Expansion |
I had already read the doc changes! 😄 If this is aimed at the mini-menu which pops up when you long-press a word then it's not surprising it's not resonating with me. The only thing I've ever used that for is to undo a highlight I accidently added when I meant to turn the page. I've never annotated nor connected any reader to the internet so the various searches are never used. Anyway, I see NiLuJe has now responded so hopefully he can be more helpful. |
|
Another example for French readers (or simply readers of French ;p), since the monolingual dictionary still isn't all that great for French: (This is a frontend, I didn't bother trying to use the TLFi directly, since it appears to require POSTing a form). |
|
Is this even better? |
|
Indeed it is, the keyboard showing up in particular was fairly annoying ;). |
|
In the future, I might add an option to filter the selection menu items based on characteristics of the selected text (e.g. how many words selected) or based on the book title/author/series/path. It would look something like |
|
@NiLuJe, can you have one last look at this before I merge it? |
|
After I merge this, I'll add @NiLuJe's TLFi example, and after I release this, I'll update the thread and webpage. |
|
Still working fine, I like the new tokens ;). 👍 |
pgaskin
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.
Tested on Aura2, Clara, and Mini with most actions and placeholders.
) This fixes the regression introduced by #94 in v0.5.0 which caused the built-in Wikipedia search to fail to load when NM is installed.
closes #93