Difference between revisions of "Frontends:Tyndale STEP"

From CrossWire Bible Society
Jump to: navigation, search
m (Reverted edits by David Haslam (Talk) to last revision by Chrisburrell)
 
(53 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
The STEP project (Scripture Tools for Every Pastor) aims to build a study tool for pastors around the world. The software will be available on-line as well as distributed to pastors in poorer countries who, usually, would not be able to afford commercial software.  
+
([http://www.stepbible.org/ STEP Bible] (Scripture Tools for Every Person) aims to build a study tool for Christians around the world. The software will be available on-line as well as distributed to pastors in poorer countries who would usually not be able to afford commercial software.  
  
 +
An introduction to the project can be found on the [http://www.tyndale.cam.ac.uk/index.php?page=STEP Tyndale House STEP home page] website. An independent review can be found [http://www.theologyontheweb.org.uk/step.html here].
  
−
== Aims & Architecture Architecture ==
+
Click the following link for the [https://stepweb.atlassian.net/wiki/ Developer's STEP technical home page].
−
=== Aim of the STEP project ===
 
−
The intention of the STEP project is to have a bible tool that will be available for a wide number of platforms:
 
−
* multiple platforms: including off line and online
 
−
* multiple operating systems, including mobile O/S
 
−
It is accepted that the mobile versions of the STEP project will access a web-based version, due to the variety of platforms and restrictions in development capabilities (for e.g. no Java platform on iPhones).
 
  
−
=== Intended features ===
+
== Aim of the STEP project ==
−
==== Data ====
+
The intention of the STEP Bible project is to have a Bible study tool that will be available for a wide number of platforms:
−
The data produced by Tyndale House, Cambridge, UK will be the main driving factor of development of this front-end. This new project offers a lot of development opportunities:
+
* multiple platforms: including an online version, a desktop version and multiple mobile apps.
−
* developing in writing a web-based front-end to JSword;
+
* multiple operating systems, including mobile OS
−
* working with Tyndale House to help them produce and publish their data; and  
 
−
* enhancing the main Sword and JSword engines to cope with the new types of datasets.
 
  
−
==== Range of features ====
+
The motivation is to help believers who have limited access to the internet, by providing tools which can be distributed on flash memory, which are expandable online when access is available.
 +
 
 +
== Range of features ==
 +
The following features are just a sample list of the intended feature set:
 
* History modules (including genealogies, timelines, articles, etc.)
 
* History modules (including genealogies, timelines, articles, etc.)
−
* Geography modules (maps, integration with Google Maps, Google Earth, overlay of historical maps onto)
+
* Geography modules (maps, integration with Google Maps, Google Earth, overlay of historical maps)
−
* Linguistics
+
* Linguistics (interlinears, lexicons, parsing help)
−
* Parallels
+
* Parallels (searching extra-Biblical literature from the same time & culture)
−
* Translations (transliterations, interlinears...)
+
* Translations (alternative transliterations, variants & manuscript evidence)
−
 
+
* Modern publications (links to commentaries, journal articles and books)
−
The above features are just a sample list of the intended feature set.
 
  
−
=== Overall Architecture ===
+
== Development of Datasets ==
−
To further the aim outlined above, the choice of technologies is as follows:
+
* Bibles - mainly PD versions with interlinear based on tagging
−
* Embedded Jetty (for the stand-alone applications)
+
* Dictionaries - merging and editing of PD dictionaries & encyclopaedias
−
* Embedded JavaDB* (for web and standalone) ensuring common data access throughout.
+
* Maps - 1:20,000 scale maps scanned for overlay with Google Maps; gazetteer with co-ordinates
−
* JSword for Bible and Module access
+
* Translations - analysis of differences in translations, and interpreting variant data
−
* GWT (Google Web Toolkit to faciliate the UI development for Java developers)
+
* Modern literature - gaining copyright permissions; links to Bible refs; develop specialist search
 +
* Parallels - collecting parallel literature; create search by linguistic domains
  
−
As a result of the above choice, we have a 100% Java application, and are able to run it as an online and offline application.
+
==Volunteers==
 +
If you are interested to become a volunteer, please visit the facebook page below, or contact the STEP team by email. You can also contact David Instone-Brewer via Facebook.
  
−
<nowiki>*</nowiki> If possible, the Embedded JavaDB module dependency will be removed in time.
+
== External links ==
 +
'''Historical  Tyndale STEP blogs'''
  
−
=== Description of the external libraries ===
+
* [http://tyndalestep-prog.blogspot.com/ Tyndale STEP blog for Programming]
−
* [http://jetty.codehaus.org/jetty/ Jetty] is a java container that will be used in the embedded mode for serving local web pages. On a server, STEP can be deployed to a Tomcat or Jetty server
+
* [http://tyndalestep-hist.blogspot.com/ Tyndale STEP blog for History]
−
* [http://db.apache.org/derby/ JavaDB] or Apache Derby is an RDBMS written in Java, that can be run in server mode as well as embdeded in the VM. If used in the embedded mode it starts up upon the first request
+
* [http://tyndalestep-tran.blogspot.com/ Tyndale STEP blog for Translations]
−
* [http://www.crosswire.org/jsword/ JSword] needs no introduction - see {link} instead
+
* [http://tyndalestep-publ.blogspot.com/ Tyndale STEP blog for Publications]
−
* [http://code.google.com/webtoolkit/ GWT] allows developers to code the UI in Java (and XML - GWT 2.0) and at compile time the UI components are compiled into javascript, which is specific to browsers and languages)
+
* [http://tyndalestep-geog.blogspot.com/ Tyndale STEP blog for Geography]
−
* Dependency Injection
+
* [http://tyndalestep-lang.blogspot.com/ Tyndale STEP blog for Languages]
−
** Server-side: [http://code.google.com/p/google-guice/ Guice] (on the server)
+
* [http://tyndalestep-pres.blogspot.com/ Tyndale STEP blog for Presentations]
−
** Client-side: [http://code.google.com/p/google-gin/ Gin] (similar to Guice but for client-side code)
 
  
−
== Development environment ==
+
'''Facebook'''
−
=== Software packages ===
+
* [https://www.facebook.com/TyndaleStep Tyndale Step Development-Team (Scripture Tools)]
−
* JavaDB (included in Java 1.6)
 
−
* JSword project checked-out (at the moment)
 
  
−
=== Eclipse ===
+
[[Category:SWORD Frontends|TyndaleStep]]
−
* Subversion eclipse plugin
+
[[Category:JSword|TyndaleStep]]
−
* GWT eclipse plugin
 
−
* Emma code coverage plugin
 
−
* A JDBC client for querying (for e.g. SQL Squirrel)
 

Latest revision as of 17:53, 10 August 2013

(STEP Bible (Scripture Tools for Every Person) aims to build a study tool for Christians around the world. The software will be available on-line as well as distributed to pastors in poorer countries who would usually not be able to afford commercial software.

An introduction to the project can be found on the Tyndale House STEP home page website. An independent review can be found here.

Click the following link for the Developer's STEP technical home page.

Aim of the STEP project

The intention of the STEP Bible project is to have a Bible study tool that will be available for a wide number of platforms:

  • multiple platforms: including an online version, a desktop version and multiple mobile apps.
  • multiple operating systems, including mobile OS

The motivation is to help believers who have limited access to the internet, by providing tools which can be distributed on flash memory, which are expandable online when access is available.

Range of features

The following features are just a sample list of the intended feature set:

  • History modules (including genealogies, timelines, articles, etc.)
  • Geography modules (maps, integration with Google Maps, Google Earth, overlay of historical maps)
  • Linguistics (interlinears, lexicons, parsing help)
  • Parallels (searching extra-Biblical literature from the same time & culture)
  • Translations (alternative transliterations, variants & manuscript evidence)
  • Modern publications (links to commentaries, journal articles and books)

Development of Datasets

  • Bibles - mainly PD versions with interlinear based on tagging
  • Dictionaries - merging and editing of PD dictionaries & encyclopaedias
  • Maps - 1:20,000 scale maps scanned for overlay with Google Maps; gazetteer with co-ordinates
  • Translations - analysis of differences in translations, and interpreting variant data
  • Modern literature - gaining copyright permissions; links to Bible refs; develop specialist search
  • Parallels - collecting parallel literature; create search by linguistic domains

Volunteers

If you are interested to become a volunteer, please visit the facebook page below, or contact the STEP team by email. You can also contact David Instone-Brewer via Facebook.

External links

Historical Tyndale STEP blogs

Facebook

Retrieved from "https://wiki.crosswire.org/index.php?title=Frontends:Tyndale_STEP&oldid=12808"