Be aware that having a console version is very different to opening the GUI with an option.
The console execution (IE. using the java.exe command) in windows will result in a console window being opened, nearly always what you do not want when using a GUI application.
The options in a context menu will normally result in the GUI being opened, may be with the application performing an operation (eg. If it were a context menu option for "Translate with BrailleBlaster" it may be that the GUI will open, the document will be opened and translated, all done automatically by selecting that context menu option in windows explorer. In such a case, no console window would be desired.
Michael Whapples On 01/10/2012 13:07, John J. Boyer wrote:
Yes, we do need a shortcut so BrailloeBlaster can be used from the console. People are using it with the Send option onn the context menu to just translate a file and in other ways.. These are minor adjustments. We're getting there. John On Mon, Oct 01, 2012 at 07:51:36AM +0100, Michael Whapples wrote:Yes the brailleblasterw shortcut in the install directory should be there, it is the shortcut pointing at the correct javaw command and giving it the correct parameters to start brailleblaster. The w indicates its the GUI version (IE. uses javaw), I probably should also create a commandline version which launches using the java command and so will work from the console. I decided to do it with a shortcut inside the installation directory because then I can have it any other shortcut just points to that, IE. there is only one shortcut which would need changing should the Java installation directory change. Michael Whapples On 01/10/2012 01:44, Vic Beckley wrote:Michael, I noticed there is a shortcut in the BB main folder called brailleblasterw. What is this for? Is it supposed to be there? I created a new installer after placing the DLLs back in the dist/native/lib folder and it worked on all three of my tests. Things look right now. Thanks for all your hard work on this. It will be a big improvement over the Inno setup routine. Best regards from Ohio, U.S.A., Vic E-mail: vic.beckley3@xxxxxxxxx -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples Sent: Sunday, September 30, 2012 7:41 PM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: My installer is working Hello, The stuff about launching with NSIS, its that currently the shortcuts will show no error messages should the path to Java change, should the user remove Java, etc. NSIS could be used to create a executable (just another installer which does no installation), could do a JVM check like the installer does, and execute the correct command. In fact, such a system could even adapt to a situation where the user has a 64-bit system, only has a 32-bit JRE to start with but later adds a 64-bit JRE and uninstalls the 32-bit JRE. For that to work, of course both sets of binaries would need to be installed. I think my usual idea is the user should find it just works. The above issues may be acceptable to some people, they may feel the user should have freedom/responsibility. May be I have spent too long with Apple stuff. However all that is probably lower priority, the cases where shortcuts would be broken are probably fairly rare. Michael Whapples On 01/10/2012 00:22, Vic Beckley wrote:Michael, Personally, I don't see any need for the Launch4j stuff either. I don't quite see the significance of what you mention about the NSIS launcher. I don't really understand exactly what you mean. I will update and give it a try a little later and report back. Thanks. Best regards from Ohio, U.S.A., Vic E-mail: vic.beckley3@xxxxxxxxx -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples Sent: Sunday, September 30, 2012 6:48 PM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: My installer is working The answer to why the SWT.jar file was correct, well I had an exclude clause preventing it being picked up from the dist/lib folder. I forgot about a suitable exclude for the native/lib folder (its to do with how NSIS searches for files when using the recursive option), I have now added a suitable exclude (well improved actually what its searching for). I will look at removing the innosetup stuff. Also, as this installer is creating suitable shortcuts, shall I look at removing the launch4j stuff? I still sort of feel a launcher may be a good idea but launch4j did not work for the 64-bit windows with 32-bit jre so its actually less functional than what the installer now does. Interestingly, NSIS can be used as an launcher, it need not show any installer pages, need not create uninstallers, etc, it can just build an executable which will do some operation like execute a command, depending on what it finds this command could be modified. Michael Whapples On 30/09/2012 21:09, Vic Beckley wrote:Michael, After I deleted the liblouis.dll and liblouisutdml.dll files in the BrailleBlaster\native\lib folder and created an installer, everything is working fine on all three of my tests. Did you delete these and forget to mention it? Why don't I have to delete the SWT.jar file in the BrailleBlaster\lib folder as well? I'm a little confused, but regardless, everything is working now for me. The installer really does look verygood.I think all the Inno stuff probably should be removed from therepository.Idon't ever see going back to it. Best regards from Ohio, U.S.A., Vic E-mail: vic.beckley3@xxxxxxxxx
