[sword-devel] Branching subversion and logging (technical questions!)
Peter von Kaehne
refdoc at gmx.net
Wed Jul 29 07:35:36 MST 2009
Jsword has its own separate mailing list onto which I copy this
response. You might get more focussed responses there.
I am only one of the translators of BibleDesktop and Jsword, so can not
really comment on the technical aspects, but my gut feeling reading what
you want to achieve is that linking of passages to relevant info does
not by necessity require any forking, but should be entirely feasible
within the existing framework of jsword and sword. And if not than the
(few) relevant changes will be more than welcome in the trunk of
What you propose seems essentially a form of commentary module(s),
though my understanding might be not complete here.
Maybe you want to expand on your suggestions?
Yours in Christ
Chris Burrell wrote:
> People at Tyndale house in Cambridge, UK and some volunteers are wanting
> to use the Crosswire JSword and in particular Bible Desktop as a basis
> for one of their projects. Tyndale house have a large number of very
> good resources and idea to enrich currently available bible tools, and
> this would be open source as the crosswire projects.
> The approach has not fully been defined, but given we want to tie
> resources to their bible passages (for eg. looking up geographical and
> historical information linked to a passage that the user is currently
> viewing), it would make sense to benefit from the excellent work of
> JSword and all the already written UI framework.
> The development approach will be to make as few changes as possible to
> incorporate the STEP (sorry that's the name of the project - Scripture
> Tools for Every Pastor) project into Bible Desktop and perhaps
> eventually to an online source as well. However the integration with
> Bible Desktop, the common swing project, etc.
> In order to do that, it seems the best option would be to branch off
> version 1.6 and at a later date when the STEP project is ready to be put
> live to merge this back in to the trunk version. Would someone enlighten
> me as to whether this is a good idea? I'm happy to provide more ideas.
> The other thing I was wondering is how one turns debug logging on. I've
> haven't got very far with that so far, but it would be used to find that
> out! Are there any pointers as to how to use the default logger?
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel