[sword-devel] Firefox front-end
dmsmith555 at yahoo.com
Mon Dec 10 17:49:26 MST 2007
Joe Walker, one of the developers of JSword, has authored DWR (Direct
Web Remoting) as a way to interface AJAX to server side java. You can
see a demo of it working with JSword here: http://eireneh.com/studious/
This is a bit stale, using an old release of JSword. You might find it
interesting. I haven't had time to look at your prototype, but once my
work deadlines ease up, I'll be more available to offer help.
But if you have specific questions regarding the JSword library,
please feel free to ask. You can also subscribe to jsword-devel and
some of the others there might like to pitch in.
On Dec 10, 2007, at 6:34 PM, Brian Fernandes wrote:
> I'm pleasantly surprised by the number of replies I've received - and
> all positive to boot. I have never come across such a high volume dev
> list till date. Awesome.
> I will try and respond to all the questions I've received here.
>> Looks nice. Strangely reminiscent of BibleDesktop (I wonder why...)
> Thanks! I'm not sure if your question about the similarity was
> rhetorical, but for the record, this is most likely because I used
> the same XSL sheet used by BibleDesktop to convert the OSIS data to
>> In other Sword applications I think that sword:// tends to be used.
>> This allows support for multiple different types of bible programs.
>> You are welcome to use bible, but I think sword would be more
>> consistent with other sword applications.
> I actually picked bible because the XSL transform actually creates
> links with this format by default. sword seems to be the marginal
> winner, so perhaps I'll just implement both like the other apps seem
> to be doing.
> I noticed that the links did not include the bible version component
> (DRC, ESV, etc.) but perhaps that is because it is implicit (same
> bible you are currently rendering from).
> Would be nice to see the protocol explained in the Wiki though.
> Regarding Sword vs JSword: I prefer (and am more familiar with) Java
> difficult to work with (but takes a while to get used to). For
> Firefox, I believe working with native apps requires more effort.
> Since both Java and the extension binaries (just an archive of XML
> and JS files) would be OS independent, this seems to be the approach
> with the least overall pain.
> I don't know how long it's going to take me to write this, but it's
> not going to be overnight; hopefully by the time I get to the
> advanced bits, DM will have evened the odds :)
>> There was a Bible toolbar for FireFox that relied on Bible Gateway -
>> this probably doesn't affect your proposal at all, but you might as
>> well be aware of it.
> Yes, I did know about this and you're right, this is entirely
> You are just like me, FF is open always and I don't like leaving it.
> After I get it working for bibles (completely), I will definitely
> expand to support more. I have only been using Sword for a week now,
> so not too experienced with it's features.
> Daniel, Karl, Frank & Eeli
> Thanks for the protocol overview. Daniel, you mentioned someone (or
> you?) played around with FF as the display engine. This is really
> the core of what I'm doing. Any idea what happened to this effort?
> Agreed, if the protocol details make it to the wiki, that would be
> Yes, definitely going to add a search capability. But I need to
> spend more time getting the basics right before going there.
> I'm definitely going to take this forward and will keep you guys
> posted as soon as I have anything remotely usable.
> Thanks for your support, much appreciated,
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel