[sword-devel] FireBible 1.2 Released

2011-06-21 Thread David Haslam
I just obserevd that on May 2, 2011, Brian released FireBible 1.2 See http://thegoan.com/blog/firebible-1-2-released/ This adds support for Firefox versions 4 through 6 (yes, 6); so overall it is compatible with Firefox 3 and above. In this version, he also added the ability to view Bibles side

Re: [sword-devel] FireBible 1.2 Released

2011-06-21 Thread Brian J Dumont
Doesn't seem to run for me. I have a working BibleDesktop installation, the java test passes, I've pointed the jsword folder and module folders correctly, but when I try to pick a Bible in FireBible, I get a dialog box: JSword could not be loaded from the specified directory. Please correct

Re: [sword-devel] BREW Development?

2011-06-21 Thread David (Mailing List Addy)
On Thursday, June 16, 2011 10:00:45 PM Greg Hellings wrote: As I understood it the FSF had (at least in the past) declared that there was an incompatibility. But IIRC, the incompatibility was actually that Apple is always violating the GPL with its distribution. Since the GPL states that the

Re: [sword-devel] BREW Development?

2011-06-21 Thread Greg Hellings
On Tue, Jun 21, 2011 at 10:39 AM, David (Mailing List Addy) davidsli...@gmx.net wrote: On Thursday, June 16, 2011 10:00:45 PM Greg Hellings wrote: As I understood it the FSF had (at least in the past) declared that there was an incompatibility.  But IIRC, the incompatibility was actually that

Re: [sword-devel] BREW Development?

2011-06-21 Thread Peter von Kaehne
That is in line with my understanding also. However, if the copyright holder does not bring the case against Apple, I am doubtful anyone else would be able to legitimately bring suit. So just don't go screaming to or at Apple about the GPL nature of the App and you can probably slip in

Re: [sword-devel] BREW Development?

2011-06-21 Thread David (Mailing List Addy)
On Tuesday, June 21, 2011 10:48:24 AM Greg Hellings wrote: So just don't go screaming to or at Apple about the GPL nature of the App and you can probably slip in under the radar. It may not be technically compliant on Apple's part, but we're the ones who get to make a fuss about it, not