Hi Ryan<div><br></div><div>Great news! There's not a huge amount of documentation apart from the javadocs within the code...</div><div><br></div><div>The page below also details some over-arching themes/design decisions... </div>
<div><a href="http://crosswire.org/wiki/Tyndale_Step_High_Level_Design">http://crosswire.org/wiki/Tyndale_Step_High_Level_Design</a> </div><div><br></div><div>Hopefully I can answer most of the technical questions. The tickets in the <a href="http://crosswire.org/bug">crosswire.org/bug</a> are a kind of repository for discussion of features. Depending on what you're keen to look at, I can point you into various directions:</div>
<div><ul><li>core features</li><li>timeline (the base component is there, but we need add all the user-friendly bits)</li><li>maps (we've only really just got a proof of concept - i.e. a set of locations that match a passage and show up, but could do with more work)</li>
<li>lots of other stuff too.</li></ul><div>David (copied) would be able to give you an outline of the project and what our overall aims are. He'll also be able to give you an idea of the data that Tyndale House have been collating to bring into STEP.</div>
</div><div><br></div><div>One of our aims is to have a passage-centric tool on which all other materials derive:</div><div><ul><li>maps: you click the button, or get some options and you're given a map which centres on a location appropriate to the passage (e.g. if Jerusalem is mentioned in the version, that's what it shows). </li>
<li>timeline: we've already got lots of data on this, so when you search for a passage it zooms on the timeline to show you the context of the passage</li><li>Eventually, we'll probably add something that says "right-click" on such and such an item, and you get all the information about that particular verse (timeline, map, genealogy, cross-references, dictionary items, etc.)</li>
</ul><div>But the main aim is to make the data available through the passage so that it complements your study.</div></div><div>Chris</div><div><br></div><div><br></div><div><br></div><div>By the way, if there's anything that can be made clearer to make it easier for the next person to build STEP, please do feel free to change/add/edit the wiki!</div>
<div><br></div><div>Chris</div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On 22 January 2012 01:38, Ryan Meyer <span dir="ltr"><<a href="mailto:ryan1234@gmail.com">ryan1234@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Cool. Took a bit of work, but got the STEP project building and<br>
running with Jetty. Is there any documentation about the app itself?<br>
I clicked around and saw a few "coming soon" menu items.<br>
<br>
Takes me a bit longer to get things done because I come from a .NET/C#<br>
background. It's been several years since I've worked with Java.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Jan 17, 2012 at 10:06 PM, Ryan Meyer <<a href="mailto:ryan1234@gmail.com">ryan1234@gmail.com</a>> wrote:<br>
> Chris and DM,<br>
><br>
> Thanks for the information! It sounds like a good need to address is<br>
> the STEP front end. Both Chris and DM mentioned it and that's<br>
> probably the best fit for me right now. I'll check out the separate<br>
> repo for STEP soon. I'm guessing it's all JSP with the JSword jar<br>
> file backing it up? Is there any live site or staging site for the<br>
> project now?<br>
><br>
> I did see quite a few open issues for STEP. I'll probably get the<br>
> code, find some minor/low impact issues and then submit patches to get<br>
> going.<br>
><br>
> Let me know!<br>
><br>
> I'm excited to get ramped up!<br>
><br>
> Ryan<br>
<br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</div></div></blockquote></div><br></div>