[jsword-devel] Bundling JSword with FireBible

[Brian Fernandes]

Joe,

1) Yes, those version numbers are now hard to keep up with. This is one 
of the reasons I need to update FireBible right now and will be upping 
the maxVersion to 15 or maybe even "*". I thought I'd also do the 
library inclusion at the same time. I have started receiving user 
complaints about this.

2) Any directory containing the jsword-*.jar or bibledesktop-*.jar files 
should do. Or you can simply use the 3MB JSword 1.6 download.

3) Automatically downloading files - I have thought of this and it does 
remain a valid option. It still won't be as easy to use as the case 
where the JARs are bundled, but I like the efficiency of this solution. 
I wonder if using some utility like fatJAR to create a single JAR would 
make it easier still (as opposed to having to download a ZIP and unzip 
that *somewhere*, then take care of multiple versions, etc.).

Thanks,
Brian.

On 11/10/2011 4:27 PM, Joe Walker wrote:
>
> I tried the xpi of FireBible from thegoan - I had a couple of issues:
> - I had to hack the xpi to point at versions of Firefox greater than 
> 6.*. I used max version of '*' because the max version field is fairly 
> useless these days - you have to be very dedicated to keep up.
> - My local install of BibleDesktop is from the jnlp download, so there 
> is no JSword install directory :( and it didn't seem to like me 
> pointing to module directories without a JSword directory.
>
> It might be possible to have FireBible automagically download the 
> requisit jar files if they are not present in the system.
>
> Joe.
>
> On 10/11/2011 10:14, Brian Fernandes wrote:
>> Currently when you install FireBible you are expected to point it to 
>> a JSword installation on your system, the FireBible extension is 
>> small and does not include JSword.
>> When I submitted this for inclusion in the Firefox add-ons list, they 
>> told me that the whole installation process was just too complicated; 
>> besides the fact that you must have Java installed, you also need to 
>> download JSword, unzip, point to this location in FireBible. I can 
>> see their point, especially for non dev types. FireBible is currently 
>> listed (but hidden from most public) in their extension registry for 
>> this reason and I intend to correct this now, at least the JSword 
>> installation bit.
>>
>> I intend to include the JSword binaries in the extension, but 
>> continue to give users the ability to specify an external JSword 
>> installation if they wish. This takes the extension size up from 
>> 300KB to nearly 4MB. But that is with JSword 1.6. With the latest 
>> nightly builds, the sizes of JARs are significantly higher and I have 
>> a few questions:
>>
>> a) I assume a large number of fixes and enhancements (like 
>> faster/better searching) have been made since 1.6 and they are in the 
>> nightly builds. Does it make sense to include a nightly build in the 
>> extension or should I stick to 1.6 for now? Is there a more recent 
>> stable build that I could use?
>>
>> b) In the nightly binary, there are multiple versions of Lucene - 
>> 2.9.1, 3.0.2 and 3.0.3. Is this intentional or can I stick with 
>> Lucene 3.0.3?
>>
>> c) I know the newest version of Lucene, Lucene 3, will not work with 
>> indices created with Lucene 1. Some time ago DM mentioned that the 
>> code to detect that the index present was a Lucene 1 index and thus 
>> invalid was not complete. Has any work been done on that front or 
>> will users still have to manually delete their indices?
>>
>> d) What is lucene-smartcn? That JAR is 3.5MB in size and almost 
>> equals the size of all the other JARs that make up JSword. From what 
>> I could find online, it adds better Chinese indexing but I would like 
>> to avoid including this as it has a very significant impact on the 
>> size of the extension.
>> i) Will Lucene / JSword still work if this file is absent?
>> ii) If yes, will indexing of Chinenese modules be completely broken 
>> or just not as "smart" if I remove the library from the distribution?
>>
>> Thanks,
>> Brian.
>>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>