Difference between revisions of "Frontends:Tyndale STEP"

From CrossWire Bible Society
Jump to: navigation, search
(→‎Intended features: [https://stepweb.atlassian.net/browse/TYNSTEP Atlassian JIRA])
Line 1: Line 1:
 
The '''STEP Project''' ([http://www.theologyontheweb.org.uk/step.html 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.  
 
The '''STEP Project''' ([http://www.theologyontheweb.org.uk/step.html 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.  
  
−
Click the following link for the [[Frontends:TyndaleStep_Tech_Home_Page | Developer's STEP technical home page]].
+
Click the following link for the [https://stepweb.atlassian.net/wiki/ | Developer's STEP technical home page].
  
−
== Aims & Architecture ==
+
== Aim of the STEP project ==
−
=== Aim of the STEP project ===
+
The intention of the STEP project is to have a Bible study tool that will be available for a wide number of platforms:
−
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 platforms: including off line and online
 
 
* multiple operating systems, including mobile OS
 
* multiple operating systems, including mobile OS
−
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). Note: It is possible that offline access would be available for Android devices.
+
 
 +
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). A native Android application will also be built.
  
 
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.
 
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.
Line 30: Line 30:
 
* Modern publications (links to commentaries, journal articles and books)
 
* Modern publications (links to commentaries, journal articles and books)
  
−
=== Overall Architecture ===
 
−
To further the aim outlined above, the choice of technologies is as follows:
 
−
* Embedded [http://en.wikipedia.org/wiki/Jetty_%28web_server%29 Jetty] (for the stand-alone applications)
 
−
* Embedded JavaDB<ref>If possible, the Embedded JavaDB module dependency will be removed in time.</ref> (for web and standalone) ensuring common data access throughout.
 
−
* JSword for Bible and Module access
 
−
 
−
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.
 
−
 
−
Go to the [[Tyndale Step High Level Design]] for more information
 
−
 
−
=== Description of the external libraries ===
 
−
* [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://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://www.crosswire.org/jsword/ JSword] needs no introduction - see {link} instead
 
−
* Dependency Injection
 
−
** Server-side: [http://code.google.com/p/google-guice/ Guice] (on the server)
 
−
** Client-side: [http://code.google.com/p/google-gin/ Gin] (similar to Guice but for client-side code)
 
  
 
== Development of Datasets ==
 
== Development of Datasets ==
Line 78: Line 61:
 
[[Category:SWORD Frontends|TyndaleStep]]
 
[[Category:SWORD Frontends|TyndaleStep]]
 
[[Category:JSword|TyndaleStep]]
 
[[Category:JSword|TyndaleStep]]
−
[[Category:TyndaleStep|TyndaleStep]]
 

Revision as of 17:16, 8 February 2013

The STEP Project (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.

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

Aim of the STEP project

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

  • multiple platforms: including off-line and online
  • multiple operating systems, including mobile OS

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). A native Android application will also be built.

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.

Intended features

The roadmap, features and bugs are in the Atlassian JIRA. Our roadmap strategy can be found here.

Data

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:

  • developing in writing a web-based front-end to JSword;
  • 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 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 GoogleMaps; 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.

References


External links

Historical Tyndale STEP blogs

Facebook

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