That’s incredible, I would 100% use this addon if you are able to create it… it would be a total game changer for me. Thanks for all your hard work, all of these addons are great and I’m excited to check out what comes next.
I’m looking at it right now, might get a version out today.
edit: → something like this
For the first version of the script I’ll do some simpler ones like change the tts key and the toggle translation button. Stay tuned on the main web extensions page.
third edit: → Please let me know which keybindings you actually use and i’ll include those in the first version.
→ The word limit bug has been solved.
→ You will now see all words for any size lesson.
→ The script encountered errors when there was no data available on a word it was trying to see.
→ We now check if no data and just display no selectable buttons nothing for that word
→ Full individual word count for a lesson is listed in the console.
Wow, you work quick, haha. So the main shortcuts I use are:
(arrow keys) - move left/right between lingqs and up/down choosing from the list on the righthand definition panel
(enter) - choose definition
(1,2,3,4) - rating lingq’s
(x) - ignore lingq
(k) - make lingq known
Just as an example, I’d probably switch this around so that it’s more like vim (the text editor) where your hands stay over homerow. It would probably look something like this:
(hjkl) - movement
(space) - choose definition
(asdf) - rate lingqs 1-4
(v) - make lingq known
(c) - ignore lingq
It would be amazing if you could also set a key to select the text box for entering your own definition… I don’t think there’s currently a keyboard shortcut to do that so I’m guessing that would be a ton of work. If that was possible you could basically use only the keyboard and never touch the mouse!
Shift + movement for jumping between pages would be awesome too but the above are the main ones that are used non-stop for me.
Thanks again for working on this, really excited to check out the addon.
I was working more with LingQing via LingQ observer, and I was wondering if — like the line starters for LingQs — we could have line starters for our LingQ’s notes section:
Root Word Meanings:
For more personal versions of these LingQs.
When the toggle line starters were created, I thought they were line starters for the notes section rather than the “meaning” section of the LingQ for the whole community. I’m only now realizing that they appear as a meaning of a LingQ over a Note of a LingQ.
Sorry, I must have been out of it not to realize this before.
Regardless, the community could use the line starters to contribute to public LingQ meanings.
This way, learners know where the meaning input came from exactly.
And use the notes section to personalize more detailed information (using the same line starters that are in the meanings section of Rooster Observer) that would be too much/personalized (to the learner) to appear on a public meaning of a LingQ.
Quick side question: Was there a reason for us not to be able to add notes via the Rooster Observer to our LingQs in addition to the meanings?
Would this be a premium feature instead?
I also noticed that when you toggle and use the line starters, it creates one larger LingQ rather than having multiple saved meanings for one LingQ. Is there a way, in addition to that, to create an experience like within Ling where multiple meanings are attached to one word?:
Edit: It’d be used differently than the grammar tags by LingQ towards the top. This would give the ability for a more detailed side-by-side breakdown (or sentence explanation) of grammar (like in the above image).
Copy of my Firefox add-on review, if you start a “Testimonial” Section for the Rooster Observer and want to use it (you have my permission ):
This is a solid add-on to up your efficiency in LingQing within LingQ! I love it and will continue to use it — though maybe in its other forms since I love more than one Rooster Extension. I’m checking it out within the Master LingQ (Premium) addon (see Rooster’s web extension support page for info on that) soon.
With Rooster Observer, learners can see the LingQ(/potential LingQ) add grammar tags, add meanings (more than one in the most recent update), toggle line starters for your notes section of a LingQ, and update LingQs that you’ve already made/ignored.
My target language is Korean, and I’ve found a smoother process in LingQing via Rooster Observer since it’s compact and comprehensive.
My setup is Rooster Observer (while I’m in sentence mode) + Rooster Hotkeys to LingQ and study more efficiently for me.
→ Simplified GUI colors / styling
→ Audio consistency
→ Fragments toggle
→ Term is now bold in the phrase
→ Added Display more fragments button
→ Added ‘New Word’ button
→ GUI update for Status selection
→ Added Transliteration for Known/Lingqed words.
→ Global display toggle at the top that persists between reloads
→ Added colors for selected and translated hints in Known/Lingqed words
→ Changed selected hint color
→ Bug fixes for New words Creation/Update
→ Phrase shows before Lingqing on new words
→ Added Translate button to Phrases
→ Added Translation fragment box
→ Changed Hint Button display
→ Added Dictionaries for All languages
→ Add/Remove Dictionaries
→ Added close button to Observer LITE
→ Fix for broken tags on LingQed words
→ Styling updates
→ Bug fix for all hints button
→ Grammar and Translation Line Starters added
→ Second and Third meanings support
→ Extra Meanings auto load and extra boxes are toggle-able
→ Added Notes section for all word types
→ Line Starters moved to Notes Section
→ Bug fixes for updating new LingQs
Sorry to hear that. Are you using manual install, or install from chrome/Firefox store?
Edit: I just tested the most recent patch 1.44 and found no issue on Chrome or Firefox. You might be having an issue if the master lingq addon is installed at the same time. To log the error you could open console (F12), click show lingqs and post a pic.
2nd edit: Problem may arise from your language not being in the new voice map. I’ll sort out the remainder languages today.
3rd edit: I have completed the entire voice map of LingQ and resubmitted the extension. Should be no problems now!