Frontends:BibleDesktop - Revision history

Refdoc at 08:30, 8 January 2018

2018-01-08T08:30:10Z

Refdoc: Replaced content with "'''Bible Desktop''', JSWORD based, runs on Windows, MacOS and Linux Project Website: http://www.crosswire.org/bibledesktop Bible Desktop home page] Category:SWORD Fron..."

2018-01-08T08:29:47Z

Replaced content with "'''Bible Desktop''', JSWORD based, runs on Windows, MacOS and Linux Project Website: http://www.crosswire.org/bibledesktop Bible Desktop home page] Category:SWORD Fron..."

David Haslam: /* Java 7 64-bit */ Java 8

2017-03-21T18:29:55Z

‎Java 7 64-bit: Java 8

David Haslam: /* Java 7 64-bit */ added details

2011-12-23T11:23:41Z

‎Java 7 64-bit: added details

David Haslam: /* Web Start Bible Desktop */ == Java 7 64-bit ==

2011-12-23T11:10:13Z

‎Web Start Bible Desktop: == Java 7 64-bit ==

David Haslam: /* Shortcut properties */ removed section (better to use Tools | Options | Sword books

2010-11-18T17:50:33Z

‎Shortcut properties: removed section (better to use Tools | Options | Sword books

David Haslam: Undo revision 8781 by David Haslam (Talk)

2010-11-18T17:48:02Z

Undo revision 8781 by David Haslam (Talk)

David Haslam: /* Shortcut properties */ Windows s

2010-11-18T16:54:46Z

‎Shortcut properties: Windows s

David Haslam: /* Shortcut properties */ N.B. Java SE does not recognize Windows environment variables, so using %appdata% cannot be used successfully here.

2010-11-18T15:39:44Z

‎Shortcut properties: N.B. Java SE does not recognize Windows environment variables, so using %appdata% cannot be used successfully here.

David Haslam: /* Web Start Bible Desktop */ == Shortcut properties ==

2010-11-18T15:31:00Z

‎Web Start Bible Desktop: == Shortcut properties ==

@@ Line 1: / Line 1: @@
-'''Bible Desktop''' is free Bible Study software. It is actively improved with releases every few months.
+'''Bible Desktop''', JSWORD based, runs on Windows, MacOS and Linux
-Bible Desktop is based upon [[DevTools:JSword|JSword]], a Java implementation of the [[DevTools:SWORD|SWORD C++ Engine]]. As such Bible Desktop works with all SWORD Modules.
+Project Website: http://www.crosswire.org/bibledesktop Bible Desktop home page]
 [[Category:SWORD Frontends|BibleDesktop]]
 [[Category:JSword|BibleDesktop]]

@@ Line 19: / Line 19: @@
 Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe
-== Java 7 64-bit ==
+== Java 8 64-bit ==
 The wrapper that runs BD insists on a 32-bit Java and if it's not present, currently it will offer to download and install it. Yet BD itself doesn't care whether it uses 32-bit or 64-bit Java. A workaround for Windows 7 users to run BD when you have ''only'' the 64-bit version installed is described below:
@@ Line 25: / Line 25: @@
 * Create a Windows CMD file containing the following ''single line'', and save it as '''BD.cmd''' into the same folder where BD is installed,
-::<tt>@"C:\Program Files\Java\jre7\bin\javaw.exe" -classpath "bibledesktop-1.6.jar;commons-codec-1.3.jar;commons-httpclient-3.1.jar;commons-logging-1.1.1.jar;commons-net-1.4.1.jar;javatar-2.5.jar;jdom-1.0.jar;jlfgr-1_0.jar;jsword-1.6.jar;jsword-common-1.6.jar;jsword-common-aqua-1.0.6.jar;jsword-common-swing-1.6.jar;lucene-analyzers-2.3.2.jar;lucene-core-2.3.2.jar;lucene-snowball-2.3.2.jar" org.crosswire.bibledesktop.desktop.Desktop</tt>
+::<tt>@"C:\Program Files\Java\jre8\bin\javaw.exe" -classpath "bibledesktop-1.6.jar;commons-codec-1.3.jar;commons-httpclient-3.1.jar;commons-logging-1.1.1.jar;commons-net-1.4.1.jar;javatar-2.5.jar;jdom-1.0.jar;jlfgr-1_0.jar;jsword-1.6.jar;jsword-common-1.6.jar;jsword-common-aqua-1.0.6.jar;jsword-common-swing-1.6.jar;lucene-analyzers-2.3.2.jar;lucene-core-2.3.2.jar;lucene-snowball-2.3.2.jar" org.crosswire.bibledesktop.desktop.Desktop</tt>
-* Create a shortcut to BD.cmd and save it to your desktop, and rename it to whatever you like, e.g. '''BibleDesktop (Java 7 x64)'''.
+* Create a shortcut to BD.cmd and save it to your desktop, and rename it to whatever you like, e.g. '''BibleDesktop (Java 8 x64)'''.
 * Edit the shortcut properties to run Minimized, and optionally change the Icon to the one in BibleDesktop.exe

← Older revision		Revision as of 11:23, 23 December 2011
Line 20:		Line 20:

	== Java 7 64-bit ==		== Java 7 64-bit ==
		+
		+	The wrapper that runs BD insists on a 32-bit Java and if it's not present, currently it will offer to download and install it. Yet BD itself doesn't care whether it uses 32-bit or 64-bit Java. A workaround for Windows 7 users to run BD when you have ''only'' the 64-bit version installed is described below:
		+
		+	* Create a Windows CMD file containing the following ''single line'', and save it as '''BD.cmd''' into the same folder where BD is installed,
		+
		+	::<tt>@"C:\Program Files\Java\jre7\bin\javaw.exe" -classpath "bibledesktop-1.6.jar;commons-codec-1.3.jar;commons-httpclient-3.1.jar;commons-logging-1.1.1.jar;commons-net-1.4.1.jar;javatar-2.5.jar;jdom-1.0.jar;jlfgr-1_0.jar;jsword-1.6.jar;jsword-common-1.6.jar;jsword-common-aqua-1.0.6.jar;jsword-common-swing-1.6.jar;lucene-analyzers-2.3.2.jar;lucene-core-2.3.2.jar;lucene-snowball-2.3.2.jar" org.crosswire.bibledesktop.desktop.Desktop</tt>
		+
		+	* Create a shortcut to BD.cmd and save it to your desktop, and rename it to whatever you like, e.g. '''BibleDesktop (Java 7 x64)'''.
		+	* Edit the shortcut properties to run Minimized, and optionally change the Icon to the one in BibleDesktop.exe
		+
		+	'''Note:'''
		+	# DM plans to look into the wrapper problem when he does the next release.

	== External links ==		== External links ==

← Older revision		Revision as of 11:10, 23 December 2011
Line 18:		Line 18:

	Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe		Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe
		+
		+	== Java 7 64-bit ==

	== External links ==		== External links ==

← Older revision		Revision as of 17:50, 18 November 2010
Line 18:		Line 18:

	Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe		Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe
−
−	~~== Shortcut properties ==~~
−
−	~~If you have already a set of modules installed from another front-end application, the Bible Desktop shortcut may be edited such that it starts in the appropriate directory. Example: (Windows 7)~~
−
−	~~C:\Users\''username''\AppData\Roaming\Sword~~
−
−	~~N.B. Java SE does not recognize Windows environment variables, so using %appdata% cannot be used successfully here.~~

	== External links ==		== External links ==

@@ Line 19: / Line 19: @@
 Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe
-== Windows shortcut properties ==
+== Shortcut properties ==
 If you have already a set of modules installed from another front-end application, the Bible Desktop shortcut may be edited such that it starts in the appropriate directory. Example: (Windows 7)

@@ Line 23: / Line 23: @@
 If you have already a set of modules installed from another front-end application, the Bible Desktop shortcut may be edited such that it starts in the appropriate directory. Example: (Windows 7)
-  %AppData%\Roaming\Sword
+  C:\Users\''username''\AppData\Roaming\Sword
 == External links ==

← Older revision		Revision as of 15:31, 18 November 2010
Line 18:		Line 18:

	Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe		Save this with a suitable filename, such as BD_WS.cmd and then create a Windows shortcut to it. To go the whole hog, you may wish to optionally change the shortcut properties, such that the command window starts minimized, and even apply a suitable icon, such as the one found in BibleDesktop.exe
		+
		+	== Shortcut properties ==
		+
		+	If you have already a set of modules installed from another front-end application, the Bible Desktop shortcut may be edited such that it starts in the appropriate directory. Example: (Windows 7)
		+
		+	%AppData%\Roaming\Sword

	== External links ==		== External links ==