jay7n/linwords

linwords's Issues

add 'phonetic symbol' as one of the basic explanation items

server side: make 'word' object sharable between GET and POST method in the same session

make it an asynchronous tornado server to respond to clients

make liwords supports two modes: local mode and server mode

serve side: make a ranking policy interface

There is a ranking system needed, which should act like such:

• when searching a word in a store and if it exists there, a statistic way is needed to rank the priority value for this word and store it in the store.
• when running the program under the query-anyone mode, a specific word calculated in this statistic way should be given back, and continually it asks the user whether he/she has remembered the word. The word's priority value will be recalculated according to the user's answer.
• the ranking policy should be extensive. A simplest ranking policy will be provided but the program supports a configurable ranking policy system (just like the "word scheme" and the "store")

server side: refine interfaces to connect "wordStore" and "Schemes" elegantly

By design "wordStore"e should only care about how to store word data and ignore the details of it, and "Schemes" define an interface to select what type of dictionaries to use for searching the word.

But there's a problem in the between. for retrieving a word from "wordStore" we have to know which "scheme" would be used so that we can get the word from the correct dictionaries exactly. By this reason there's a cross-point between them. That means, "wordStore" has to know some details about the word to some extent.

Let me figure this out.

client side: make client tool more like a command-line tool (support various opts)

defect: "ICiBaCollinsDictScheme" doesn't support complicated styles of explanations other than the expected simple case

For example when searching the word "lay", there is a dedicated section explaining "Usage Note", which is not covered in the "ICiBaCollinsDictScheme" parser, hence leading to an exception and returning a 404 page not found result.

code refactor phase 1

• convert all 'print msg' for debugging purpose to logging.debug()
• handle the every margin cases properly
• read the popular python coding convention and apply them to this project - used autopep8
• split interfaces and implementations well

client side: allow users pick up different dict schemes