Welcome to JLDrill

JLDrill is a program for helping people drill various aspects of the Japanese language. Current features include a kana drill, a vocabulary drill, a dictionary cross reference tool, a popup-kanji reference with stroke order diagrams, example sentences from the Tanaka corpus and the ability to do dictionary lookups (with deinflection) by hovering the mouse over a word in the quiz or examples.

The current version is 0.5.1.

Screenshots

JLDrill screenshot #1 JLDrill screenshot #2

What’s New for 0.5.1

Version 0.5.1 is primarily a packaging release. Apart from packaging there is one minor feature. Sometime if you have been away from studying for a long time you get into a situation where you can’t review all your items in a day or two. In this case, short term items suffer because it takes them a long time to come to the front of the queue. Version 0.5.1 allows you to “forget” old items in a structured way. You can set which items to forget from the Options window.

The main feature of this release is packaging. JLDrill has finally been added to the main gem repository. This means that you can install JLDrill on any machine with Ruby and Gnome simply by typing “gem install jldrill”. The latest version will be downloaded from the internet and installed. On Windows, Gnome will even be installed for you. “gem update jldrill” will also upgrade you to the latest version of jldrill. For most people this will be the simplest way to install JLDrill.

Work has once again halted on a simplified Windows installer. The current installation instructions are quite simple and I haven’t found anyone having problems. If have problems installing JLDrill, please contact me.

JLDrill is Beta Software

I consider JLDrill to be in beta. Most of the important features are present. There may still be bugs, but I have been using the software myself for several years and I think I’ve gotten rid of most of the big problems. Please be considerate of the beta status, though. Keep your eyes open for problems and report them. Poor usability issues are especially welcome. Usability problem reports should describe the difficult work flow and give a suggestion for a new work flow that will improve the problem. I am a programmer, not a UI designer, so I welcome any and all advice on this front.

News

Monday, May 23 2011

Wednesday, March 9 2011

Monday, January 17 2011

Thursday, August 26 2010.

Friday, March 15 2010

Thursday, October 8 2009.

Friday, April 3 2009.

Thursday, Dec 25 2008.

Friday, Dec 19 2008.

Saturday, Dec 13 2008.

Tuesday, Dec 9 2008.

Friday, Aug 29 2008.

Sunday, Nov 11 2007.

Friday, Nov 2 2007.

Tuesday, Jan 29 2006.

Monday, Dec 19 2005.

Saturday, Dec 17 2005.

Friday, Dec 16 2005.

Monday, Dec 5 2005.

site info

© 2005-2011 Mike Charlton | Generated by webgen | Design by Andreas Viklund modified by Mike Charlton.