Dear Troy & Chris
Troy - thanks for explaining the mixed history of JSword, and the data types used in the lucene-indexed database. This database sounds ideal for large texts.
We will be needing various databases for STEP. Eg the History module will need a database with fields such as Date, span, Person/Event name, Scripture refs, notes, flags for accuracy of dating, type of person/event etc. The Geography module database will need fields such as Places, co-ordinates, notes etc. The Languages module will include a database of Greek texts, with bibliography of Greek and English eds, parameters for the limits of references, number of levels used for divisions (eg books/chaps/verses), the total number of chapters etc. In other words, we'll need something fairly flexible.
It sounds like the database in JSword is fairly constrained in the formats of data it is ready for - that is, the database is designed for containing large texts and for searching them quickly, which is very useful. But it may not be suitable for providing all the fields we need, such as dates and co-ordinates.
Chris -The HSQLDB sounds good. I guess we can assume that all platforms will have Java available, though it may not be installed by default. Thanks for making good headway with this.
BTW, Have you come across any good javascript databases? Most browsers now run javascript very fast, and this adds much less to the resources demands because the browser will be running in any case. I understand that TiddlyWiki (a wiki built entirely in a single html file) has data import and export capability - using nothing but javascript (ah - and a java applet for Safari, Chrome and Opera). Of course, if we need Java anyway, then a javascript database may not give any advantage.
The other big question in my mind: If we are going to use JSword (which would save us a lot of time) we also need to find a way to get a browser to address it.
I'm hoping that Google Gears may be the answer, but I don't have a clue about how to go about connecting the two.
David IB
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment