I just made a plea for API updates on the LingQApi functionality. While creating the csv is a good workaround, creating new lingqs through the api as the user creates them would be much preferred of course, and a much more attractive system for members and possibly new users.
@Lyise I have yet to look too deeply into the addon. I extracted the xpi and thats about as far as I got. I'm glad that you are doing the legwork on it! :-D I too should familiarize myself with this xul structure and speaking with Firefox.
I just made a plea for API updates on the LingQApi functionality. While creating the csv is a good workaround, creating new lingqs through the api as the user creates them would be much preferred of course, and a much more attractive system for members and possibly new users.
I just made a plea for API updates on the LingQApi functionality. While creating the csv is a good workaround, creating new lingqs through the api as the user creates them would be much preferred of course, and a much more attractive system for members and possibly new users.
Dominick, I've tested your tool and it worked quickly with no problems on the three languages I am studying. Thank you very much. I am truly impressed with the Highlighter too, I did not know that kind of things existed.
Having Lingq features on any website would be fantastic, I believe it would be a huge step forward for Lingq.
Having Lingq features on any website would be fantastic, I believe it would be a huge step forward for Lingq.
@odiernod - Wow! This works great, as does the Vocabulary Highlighter add-on. I tried it for French in which I have thousands of LingQs and it works well. Obviously, to figure out a way to incrementally update new LingQs both in the the LingQ database and in the highlighter app db would be great. We will take a look at the API and see what we can do to support your efforts!
@mark, thanks for the help and encouragement. I'm excited about what we'll be able to produce as well, it will really turn LingQing into a powerhouse.
Updates made to the tool import page, the lang code is no longer case sensitive, I increased the wait timeout to the LingQAPI for those with a crap ton of LingQs, so it should no longer time out on you guys.
I changed the encoding of the xml file to UTF-8, so the file sizes it produces are much smaller now, it should still support the asian character sets, please let me know if it no longer does.
Updates made to the tool import page, the lang code is no longer case sensitive, I increased the wait timeout to the LingQAPI for those with a crap ton of LingQs, so it should no longer time out on you guys.
I changed the encoding of the xml file to UTF-8, so the file sizes it produces are much smaller now, it should still support the asian character sets, please let me know if it no longer does.
Before the current latest updates, it did my Dutch lingqs and it took less than 30 seconds. Around 20,000 of them - so, the performance isn't too bad at all.
@Odiernod Ok, I successfully escaped the import process without needing to restart Firefox (wasn't actually aware that I could). Thank you so much for that hint, and also for making your conversion tool so generously available to us all.
BTW, on reopening the VH options panel, my previous database had vanished. I get the impression the database merge process stalled and failed because my existing database and the one created by your tool somehow didn't like each other, maybe because my database had definitions for pens and yours hadn't. LingQ'd words now get properly highlighted by VH. Best of luck and thanks again!
BTW, on reopening the VH options panel, my previous database had vanished. I get the impression the database merge process stalled and failed because my existing database and the one created by your tool somehow didn't like each other, maybe because my database had definitions for pens and yours hadn't. LingQ'd words now get properly highlighted by VH. Best of luck and thanks again!
Let me know how urgent everybody feels is it that we get the ability to export your LingQs created in Vocabulary Highlighter. I was planning on waiting until the LingQ API was updated to do something like that, but its already caught me a couple times where I started to create a "lingq" on another page through VH and went "oh crap, I'm not in LingQ right now" so I was wondering if anyone else was making any use of this or not.
I'd personally wait too (if I was coding it) and as a user, I AM waiting for it (for that functionality to arrive). Looks like you're doing great work there Odiernod.
Hey, I wonder if it would be able to have a word count displayed somewhere. Like this - 100/1000 (10%) - which could be added to toolbars. Just an idea.
Hey, I wonder if it would be able to have a word count displayed somewhere. Like this - 100/1000 (10%) - which could be added to toolbars. Just an idea.
Thanks as well.
Just wondering "we get the ability to export your LingQs created in Vocabulary Highlighter" means import from VH to LingQ. right?
Just wondering "we get the ability to export your LingQs created in Vocabulary Highlighter" means import from VH to LingQ. right?
Meanwhile, such addon is already out for one of LingQ's clones http://habrahabr.ru/company/lingualeo/blog/127854/ (rus)
For those interested in making the most of the Pen feature of Vocabulary Highlighter, I jotted down a description on Google Docs: https://docs.google.com/document/d/15J8AsmGCevD... (anyone with the link can view, comments are allowed).
Thanks odiernod for all your effort!
The xml.-File works fine. Would it also be possible to import the status 4 words?
About 95 % of my words have the status 4, as I tend to switch them to "known words" as soon as I remember them without any help. But after some time I forget a lot of them again, at least if I don't encounter those words for several times. So it would be nice to have the status 4 words in the list, too.
The xml.-File works fine. Would it also be possible to import the status 4 words?
About 95 % of my words have the status 4, as I tend to switch them to "known words" as soon as I remember them without any help. But after some time I forget a lot of them again, at least if I don't encounter those words for several times. So it would be nice to have the status 4 words in the list, too.
@il melomane, sure, when I get the time this weekend I will add the option to also import status 4 words if you wish.
General update: the author of Vocabulary Highlighter has gotten back to me and we have permission to adapt his code within the limits of his software license - which states that it can't be used for commercial purposes and can't be re-branded with a commercial name; are working through the aspects of his software to license to make sure that the add-on will comply to the license and be satisfactory to all parties.
General update: the author of Vocabulary Highlighter has gotten back to me and we have permission to adapt his code within the limits of his software license - which states that it can't be used for commercial purposes and can't be re-branded with a commercial name; are working through the aspects of his software to license to make sure that the add-on will comply to the license and be satisfactory to all parties.
Yes, that would be great. Thanks!
The words which are - in the meantime - much too easy, I'll remove manually from the list (mainly the first 1000-2000 Lingqs I created) afterwards.
Have a nice weekend (hopefully with not too much work :))!
The words which are - in the meantime - much too easy, I'll remove manually from the list (mainly the first 1000-2000 Lingqs I created) afterwards.
Have a nice weekend (hopefully with not too much work :))!
@odiernod I've started to make some headway on a re-write from scratch, so I might see how that goes for a bit longer as it would avoid any potential problems on that line. If it seems like it'll take too much longer to re-write I'll kill this side of things, though.
Its good that we can do this sort of parallel development, if the "license talks" don't go well it will give us another plan. And if we do wind up using the Vocabulary highlighter, you'll be up to snuff on the add-on and able to make contributions immediately. I am am currently fighting with javascript on interfacing with the lingqapi, I'm pretty sure firefox is squelching my requests due to the "same origin" enforcement. Otherwise, I have plans drawn up on how to do the language database switching without forcing the user to manually export and import their language lingq files. We might want to start a LingQ add-on thread in the development section since we are starting to talk specifics
I initially posted this in the programming thread but I guess it makes more sense to post it here:
@odiernod - I didn't realize that the Firefox add-on would require Javascript, how exactly does that language come into play? I just assumed the Firefox add-on would require a compiled language of some sort instead. I might be able to help if Javascript is used... while my experience is just limited to school, (currently working on a BS in IT) the programming experience that I do have tends to be with scripting languages such as Javascript. Anyway, if you give me an idea of what you need done in that language I can at least take a crack at it and see what I come up with.
@odiernod - I didn't realize that the Firefox add-on would require Javascript, how exactly does that language come into play? I just assumed the Firefox add-on would require a compiled language of some sort instead. I might be able to help if Javascript is used... while my experience is just limited to school, (currently working on a BS in IT) the programming experience that I do have tends to be with scripting languages such as Javascript. Anyway, if you give me an idea of what you need done in that language I can at least take a crack at it and see what I come up with.
Hey there cgreen, firefox addons are nothing more than a collection of javascipt files with specially formatted xml files (called xul files) to make the web forms and context menu hooks. Its done this way so that all code can be run within the browser to keep the addons platform independent (and secondly so web designers can make them without knowledge of low level languages). Accessing a compiled language is possible, but discouraged since there is no truly platform agnostic compiled language (not even java, though they market it as such).
If you want to help out, that'd be great, there is a link to the project page on my profile. There is no code yet but I put up a precursory list of requirements in thd issues section. You can also familiarize yourself with the structure of firefox addons.
If you want to help out, that'd be great, there is a link to the project page on my profile. There is no code yet but I put up a precursory list of requirements in thd issues section. You can also familiarize yourself with the structure of firefox addons.
Thanks to Odiernod, to the other programmers working on this and to Dooo for getting things started by bumping up this thread.
Interesting to note that Vocabulary Highlighter works on the LingQ site, too. It highlights items in the My LingQs list--is that a good thing? (just asking)--and on the QuickLingQ tab of the lesson page.
Interesting to note that Vocabulary Highlighter works on the LingQ site, too. It highlights items in the My LingQs list--is that a good thing? (just asking)--and on the QuickLingQ tab of the lesson page.
I recommend to deactivate the highlighter for the time you're working with Lingq (it's only one click on the pencil). Otherwise you can't see the highlights created by Lingq.
Hello odiernod!
I don't have access to your website. I only get the message "Server is too busy".
I don't have access to your website. I only get the message "Server is too busy".








