"Greg Hellings" <[EMAIL PROTECTED]> writes: > Resolving issues into specific other modules is also a portion of code > that has been much talked about, but needs to be resolved in parallel > with this
For the record, GnomeSword handles this in (what can be) a general way: GS handles "sword://" URLs as clickable references. GS understands "sword://ModuleName/KeyIntoThatModule" where the key is obviously a verse reference for Bibles and commentaries, but just as easily is a treekey for genbooks and lexdicts. I have modules that link directly to Josephus, for example: <a href="sword://Josephus/%2FThe+Antiquities+of+the+Jews%2FBook+17%2FChapter+2%2FSection+4"><i>Ant.</i> 17.2.4</a> I don't believe that the full URL encoding (`/' => "%2F") is required, but I implemented that way just to be pedantic. Obviously, in UIs which don't target HTML as their final display motif, these links are just NOPs. GS installs itself as the GConf handler for sword:// URLs, which means that sword:// URLs can appear in web pages, and Firefox knows how to get to them. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
