Re: [Tyndale STEP - Programming] Sword modules

I came across them for the Firefox plugin to JSword.I think it's as pictures though.

About 1:30 in of http://thegoan.com/firebible/screencasts/#misc (FireBible Core Features Part 2: General Books, Daily Devotionals, Maps, Dictionaries & Preferences)

I just found that there might be a Easton module too (i remember that being mentioned in some previous posts).

Cheers

Chris

On 15 April 2010 12:01, Tyndale STEP Project <tyndalestep@googlemail.com> wrote:

Do you know where Sword modules are listed?
As you say, Chris, there may be a genealogy module which just needs updating+checking.

David IB

At 23:22 14/04/2010, Tyndale STEP Project wrote:

On the note of data, I know that there are already some sword modules, so perhaps we can hook into some of that. Not sure how complete they are or, if they are in a suitable format for us to use...
Chris

On 14 April 2010 23:18, TyndaleSTEP < tyndalestep@googlemail.com> wrote:

Yes, genealogies in v.2 sounds right. I need to find someone to do data for that.

David IB

At 20:38 14/04/2010, Chris Burrell wrote:

Hi David

Thanks for that. I've classified the features by release. If you want to have a look on the crosswire JIRA, then you can let me know if it looks roughly right. I wasn't sure where you wanted genealogies...

Chris

On 13 April 2010 18:39, Tyndale STEP Project < tyndalestep@googlemail.com> wrote:

Chris, I'm sorry I have taken so long to get back to the Crosswire admin

You'll have to be patient with me. This kind of collaborative project is very new to me.

I'm copying in David Haslam who is a Project Leader on the Go Bible project at Crosswire.

He popped into Tyndale House yesterday, and he sounds like he could offer some very useful advice

to help us get started in the community.

Re the project components on Jira at http://crosswire.org/bugs/browse/TYNSTEP

- I think you have a very good handle on this. Could you take care of it?

- I've added a couple of items

As you say, we should work towards a specific release.

In terms of project and data, it is realistic to work towards a utility which includes:

* Bibles, with interlinear on tagged versions

* Expanded Strong's lexicons for Greek & Hebrew linked to interlinear and tagged English

* Bible dictionary, incl names and places, linked by scripture ref

* Dateline, linked by scripture ref.

If this was called Phase 1, it would indicate that we are aiming very high,

because this already includes most of what is found in current free software.

Re the Wiki at http://crosswire.org/wiki/Frontends:TyndaleStep

- the page you made almost says it all!

- I've added a summary on the development of datasets

Re the email inviting involvement

I don't know what kind of email will work. Is it one which majors on the purposes and need for the software,

or one which indicates details about the kind of work which is needed?

I'm had a go at writing the former, but it doesn't have much of the latter.

Feel free to add details which you think people would want or need to see.

Tyndale STEP - Scripture Tools for Every Pastor

===================================

Aim: To link the Bible to ancient history and geography which confirms and illuminates it.

Ancient texts confirm and illuminate the Bible, but they are inaccessible to most readers.

Scholars tend to write about problems rather than the facts which confirm the text,

so that the overwhelming historical and geographical verification of the text is overlooked.

This project will make ancient texts and maps accessible to everyone, scholar and non-scholar alike,

so that the Bible is illuminated by its full ancient context.

1st phase: build a multi-platform structure for standard Bible-study tools:

* Bible texts, including original languages, translations and interlinears

* Language aids, including lookup-dictionaries concordance searches

* History tools, including an expandable timeline with scripture links

* Dictionary articles, culled from various sources and edited

2nd phase: add detailed geographic, historic & linguistic data

* Gazetteer of all named places, with short articles and links to pictures

* Co-ordinates of identifiable places to GoogleEarth

* Map overlays of high-ref 1:20,000 maps of pre-urbanised Palestine

* Flexible timelines which can be altered at key points of uncertainty

* Full-text lexicons linked to the lookup dictionaries in tagged texts

3rd phase: add translation aids and links to modern publications

* different possible translations for words and passages

* differences in manuscripts, with evidence for each variant

* expositions in modern and older commentaries, articles and books

4th phase: adds link to extra-biblical literature with searching

* search other ancient literature for similar passages in a similar context

* look up Greek and Hebrew words in other ancient literature

* view ancient texts with translations where possible

These tools will put centuries of research into the hands of non-scholars.

When the information is laid open like this, it is easy to see that the Bible is

well preserved and translated, reflecting historical events in real places,

and dealing with issues current in the ancient and modern work alike.

(Feel free to tone down the language if you think it sounds too much like a salesman.)

David IB

At 09:44 31/03/2010, David Instone-Brewer wrote:

http://crosswire.org/bugs/browse/TYNSTEP

Looking good!

Won't get to it today - sorry!

David IB

At 22:29 30/03/2010, Chris Burrell wrote:

Righto, well I've added all the issues to Jira, and you should now be a project administrator. Not sure what you want to do next, what there seems to be 2 things I can think of:

1 - updating the priority of each feature

2- creating a release and deciding what goes in each release.

I guess we could call a release a milestone, and then have a proper online version for each milestone...

We probably also want to create a bunch of issues with creating data at some point.

Let me know what you think

Chris

I wasn't thinking of putting the maintenance sign on the wiki, but at http://crosswire.org:8080/~chrisburrell/Step.html

That way, anyone who stumbles on it will realise immediately that it is a construction site.

DavidIB

At 13:16 29/03/2010, Chris Burrell wrote:

Hi David

We'll able track the in-progress status of things with Jira. I think the wiki should be a description of where we're heading, and how we're heading there. Hopefully that will limit the maintenance tasks around it.

Chris

Dear Chris

I'm impressed at how far you've got so quickly.

Do you think we should put a link on the Wiki - along with a warning that this is 'work in progress'

(it might look a bit naff, but a "men at work" warning gif sign might say more than a written disclaimer)

David IB

At 12:34 29/03/2010, Tyndale STEP Project wrote:

Yup, that is still the address. Was it not working? Thanks for the feedback. At some point, I want to go through all the UI and bring it up to scratch. I guess at the moment you could see it as a presentation of services rather than a usable user interface.

Chris

On 29 March 2010 12:14, Tyndale STEP Project < tyndalestep@googlemail.com> wrote:

>Got it up and running for NT passages... The presentation doesn't

>look great, but shows that at least we can do it.

Well done with the interlinear so far.

I expect you already know the following probs, but just in case:

* The verse ref is overlapping with the first words of each verse

* the verbs are missing in the Greek

* Greek words which aren't tagged (mostly articles) accumulate at the start

It looks like some of these problems are caused by the tagging.

If you tell me what the problems are, I'll have a go at correcting them.

(or find someone else to do it)

One fix which springs to mind is to extend the tags around any

preceding article.

(BTW is the address http://crosswire.org:8080/~chrisburrell/Step.html

still correct?)

David IB

--

Posted By Tyndale STEP Project to Tyndale STEP - Programming on 3/29/2010 04:10:00 AM