- Add sorting of output.
- Problems:
- sometimes server block the request and incoming responses has 403 Forbidden Error. I think that this is a ddos protection of cologne http://www.sanskrit-lexicon.uni-koeln.de host server.
- if you try test it on localhost please remember, that for correct work chrome plugin can be switched on, but for correct work others internet resources (youtube for instance) it can be switched off.
- TODO:
- manual test, or it will be batter write auto tests.
- bug fixing
- The settings.html page has been added. All properties now are stored in localStorage. It means that we may change it in one place and it will affect in all anothers one.
- Bugfix word.frequency null value. If the word is absence on the frequency table, then word value is set to null. But in this case we may order by length.
- TODO:
- word list ordering by desc word.frequency. Now it's display in parentheses before word name.
-
Store word frequency usage to localStorage. It was implemented by word_frequency.js which is converted from text data file by java program. Once it prepared it may be used till time when frequency data will be changed. Java converter is in https://github.com/juhnowski/FreqWordList url.
-
add server.js - this is node.js simple http server for testing. LocalStorage is working only with domains.When I opened fetching.html as file, localStorage was inaccessible.
-
run local http server:
- install node.js https://nodejs.org/en/
- install http-server https://www.npmjs.com/package/http-server via npm: npm install http-server -g
- run server: node server.js
- test url in CHROME: http://localhost:8080/fetching.html and don't forget switch on CORS plugin
-
TODO:
- word list ordering by desc word.frequency. Now it's display in parentheses before word name.
- changes test.filter = "roman"; test.noLit = "off"; test.transLit="slp1"; which are now hardcoded.
Add fetching.html - yet another iteration of search UI component
Please pay attention: 1)It will work correct from http://www.sanskrit-lexicon.uni-koeln.de site. 2)For correct work in local browser it's needed to install Google chrome plugin: https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi/related?hl=en-US
Previously we talk about getting data from server in JSON format, but I stay on parsing incoming html, becouse:
- to keep the backward compatibility
- not to spend time and forces on changes in a backend and then support two version of server responses: html and json