[sword-devel] Getting stuff done (Re: External links)

[Ben Morgan]

Here is how I would do it/it should be done:

For internal links in OSIS:
In:
<reference osisRef="module:encoded_key">Text</reference>
Out (For osishtmlhref):
<a
href="passagestudy.jsp?action=moduleRef&value=encoded_key&module=module">Text</a>

Vary the passagestudy string according to taste - especially moduleRef
If module == "self", use the current module.

If a link starts with Bible: or has no : in it, the existing reference code
should be used.

I see no reason to give an option for sword:// style of URLs - if anyone
wants them, they should write their own filters - there is no easy way to
allow user customization of them. The way above is consistent with the
similar functionality in the filters.

God Bless,
Ben
-------------------------------------------------------------------------------------------
Multitudes, multitudes,
   in the valley of decision!
For the day of the LORD is near
   in the valley of decision.

Giôên 3:14 (ESV)



On Thu, Nov 27, 2008 at 3:16 AM, Matthew Talbert <ransom1982 at gmail.com>wrote:

> On Wed, Nov 26, 2008 at 5:11 AM, Eeli Kaikkonen
> <eekaikko at mail.student.oulu.fi> wrote:
> > Quoting Greg Hellings <greg.hellings at gmail.com>:
> >
> >
> >>
> >> Likewise.  People (I think Chris is one of the leading people, but I
> >> might be mistaken on that) ought to stop advocating usage of OSIS
> >> references for the time being.  They accomplish nothing, since they
> >> produce nonsense out the other end, being that they're not supported.
> >> Why BibleDesktop or BibleTime or BPBible don't support sword:// is
> >> probably because they're all working on other issues right now.  DM
> >> already mentioned some things BibleDesktop is trying to figure out
> >> first, the BibleTime guys are actively working on achieving
> >> independence of the KDE libraries, Ben just explained why he can't get
> >> support into the current version of BPBible.
> >
> > Actually BibleTime uses sword:// internally but the rest of the link
> > specification may be a bit different from other implementations. I
> > have thought about changing it if necessary. This whole issue is
> > important enough to be resolved as soon as possible. Linking inside
> > and between modules should be self-evident feature in Bible software.
>
> Greg Helling is working on the filters. His proposal is to use
> sword://module/OSISref links for internal links because that appears
> to be the easiest way to implement. There would be an option when you
> create the renderer to get links in either passagestudy.jsp style or
> sword:// style. So a reference would like like sword://ESV/Gen.1.1 for
> instance.
>
> Comments?
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20081127/aa83decb/attachment-0001.html