The major changes in the previous change list (I should have put those in the comments) are
- The Strong dictionary lookup which basically means, that any scripture text with Strong numbers (coding in the xml source) can be looked up by a click which will make a call to the server to get the definition. Not all versions have this, so KJV is one example.
- The reverse interlinears, for e.g., again using a strong-numbered , it will lookup the greek/hebrew from the original text and associate it to the english text
- The classic interlinear (similar to above, but more accurate), will take the original text and then map on the english/other language
- Added checkstyle stuff, although we need to go through and eliminate a lot of the warnings!
- Started adding tests to boost our code coverage. A cool plugin called EmmaECL is what I'm using to check this, and my aim is to boost it to 80% or something like that.
- Added an Install Bible version service
When you start on the UI, it would be good to start building test cases too.
I think one of my next moves is going to break up the step project into 3 shared projects
step-web-client
step-web-shared
step-web-server
Possibly also make it so that it uses maven. Have you used maven before?
Partly for compile time to go down, also because it's a logical split-up. Unless you think we should split up according to functionality... and have each of those three if each project...
On the UI-side of things, apart from the obvious main page, we also need to create:
- a user preferences page
- a installer page
- a configuration page
Up to you really, but these pages might be fairly trivial to make and give you a good practice for everything else, or on the other hand, it might be best sticking with the main stuff and redesigning that completely. On the other hand, we can host our step on the web without need for all of those, and with configuration in properties file/hard coded in to java constants
Chris
No comments:
Post a Comment