-
Notifications
You must be signed in to change notification settings - Fork 1
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
Context Version Feature Request #3
Comments
I will implement the suggested features but context data needed for adding it to Anki notes which I have not. |
The note template would be essentially the same as the current template you have, but it would enable you to have context text before and after the construction portion. Here's an example with Japanese (I don't know Chinese, so this will hopefully be enough to explain it):
Note Fields (simplified to only what is needed for the above for this example): Sentence: なかなか予約が取れなくて行けなかったレストランにようやく行けることになった。 Before: なかなか After: 行けることになった。 Splitted: ようやく 行けなかった レストランに 予約が取れなくて The "Before" and "After" fields would be optional to fill out. If either of them are filled out, the text in the field will render before or after the construction area (which accepts the buttons after clicking them below). The button text should align with the "Before" and "After" text after it is clicked. If the "Before" and "After" fields are blank, the note type would behave in the same way it does in the current version. What I would recommend is updating the note type for the Chinese grammar deck to support the "Before" and "After" fields and leaving all of the "Before" and "After" fields blank for users to fill out if they feel it helps clarify a particular card. If there are problem cards in the Chinese grammar deck, where the context makes the problem more clear, they can be submitted back to you to be updated in the Ankiweb version of the deck. |
Sentence Grammar Practice.zip This contains |
Thank you. It works as expected. The only other thing that'd be great to have would be for the buttons to fill the blanks from left to right as they're clicked, rather than filling the last blank first and filling in right to left. It's a minor thing, since the note type functions perfectly regardless with the update though. Thanks again for your help. |
It can be implemented by changing js code in card templates. I may view this later. |
I was curious if it may be possible to create a version of this note type that optionally supports context before and after the construction portion? The card would look something like this:
Text Context [ Construction Portion ] Text Context
_________
Options
[Check] [Reset] [Hint]
Clicking the options would have the same functionality as the current note type, but it would place the buttons in the construction portion aligned with the text on the left and right hand side. It would be great if it would be possible to have the construction portion appear anywhere as well (optional context before, after, or both before and after the construction portion).
I think the current implementation of the note type is great, but I feel having the ability to optionally place context anywhere around the construction will add a significant amount of utility to this note type. I noticed that some questions in the Chinese grammar deck are not intuitive to assemble without the context available (questions with dates in the sentence for example can be ambiguous).
I think this addition would manifest itself in 2 additional fields on the note type that would cover context before, after, and both when both fields are filled in. I tried coding it up a little bit myself, but I was having issues getting the alignment correct between the outside text and the construction area where the buttons are placed. Ideally the location of the buttons should align exactly with the outside text vertically to look like you filled in a complete sentence. Any help with implementing this would be very much appreciated. Thanks for making this great note type!
The text was updated successfully, but these errors were encountered: