It places the qt dlls in the bin folder, and so doesn't need to "find them", and leaves the qt folder nearly blank. The other version puts them in qt folder, and the only purpose of jqt.cmd is to update the path to include that folder. Is there a possibility of standardizing the other version to use the same folder structure as the AIO installer? It might solve inconsistencies with install 'qtide'.
If that is not possible, could jqt.cmd be updated so that last line adds %* or %1 %2 %3 %4 %5 %6 %7 %8 %9 for compatibility with ancient windows versions. ----- Original Message ----- From: bill lam <[email protected]> To: "[email protected]" <[email protected]> Cc: Sent: Sunday, April 6, 2014 9:03:51 AM Subject: Re: [Jprogramming] jqt command line I suggest you install (if not yet) to see how it works. 06.04.2014, в 21:57, Pascal Jasmin <[email protected]> написал(а): > If I understand then, the AIO installer will "permanently" set the path to > QT? If a user updates his QT system to a version that is incompatible with > current installed J, will that cause the AIO installation to fail where the > jqt.cmd version would keep working (because it sets the QT path as the first > item in path list)? > > > ----- Original Message ----- > From: bill lam <[email protected]> > To: [email protected] > Cc: > Sent: Saturday, April 5, 2014 11:10:29 PM > Subject: Re: [Jprogramming] jqt command line > > sorry typo! s/I can answer/I cannot answer/ > > Вс, 06 апр 2014, bill lam писал(а): >> I don't use jqt.cmd so that I can answer if it needs another >> version. since jqt.cmd set up environment, so that fork_jtask >> can inherent that enviornment. >> >> I use the windows AIO installer, then there is no jqt.cmd, >> clicking on jqt.exe launch directly. And I guess >> the cmdline parameters should agree with the documentation. >> >> IMO AIO installer is more suitable for idiotic windows users >> like myself. ymmv. >> >> Сб, 05 апр 2014, Pascal Jasmin писал(а): >>> Without the change to jqt.cmd (adding %*) jqt doesn't see any ARGV. >>> >>> I notice that you cannot launch jqt.exe directly (needs to set path to QT), >>> but you can call jqt from Jqt >>> >>> fork_jtask_ jpath '~bin/jqt.exe filename2load' >>> >>> >>> and this also works: >>> >>> fork_jtask_ jpath '~bin/jqt.exe -js a=:2+2' NB. no spaces inside >>> expressions. >>> >>> >>> >>> My question though, >>> >>> could the official distribution ship with a version of the .cmd file that >>> does allow arguments to be passed? >>> >>> >>> >>> ----- Original Message ----- >>> From: bill lam <[email protected]> >>> To: "[email protected]" <[email protected]> >>> Cc: >>> Sent: Saturday, April 5, 2014 7:30:23 PM >>> Subject: Re: [Jprogramming] jqt command line >>> >>> It is the responsibility of your script file to handle arguments in ARGV. >>> >>> >>> In linux, it should be something like (untested) >>> >>> #!/bin/sh >>> jqt "$@" >>> >>> >>> 05.04.2014, в 22:48, Pascal Jasmin <[email protected]> написал(а): >>> >>>> if I modify the windows jqt.cmd file last line to: >>>> >>>> start bin\jqt.exe %* (adding %*) (saving to jqt2.cmd) >>>> >>>> >>>> trying to get consistent behaviour with >>>> http://jsoftware.com/help/user/cmdline.htm >>>> >>>> the line: >>>> >>>> jqt2 "D:\j64-801\addons\demos\gldemo\basic1.ijs" >>>> >>>> >>>> will correctly load the file after profile >>>> >>>> but the lines: >>>> >>>> jqt2 "D:\j64-801\addons\demos\gldemo\basic1.ijs" "a=: i.4" or >>>> >>>> jqt2 "D:\j64-801\addons\demos\gldemo\basic1.ijs" "-js a=: i.4" >>>> >>>> >>>> do not execute a, though ARGV is correctly set (in first example, could be >>>> run with ".) >>>> >>>> It does not appear to be possible to pass a -js command line without a >>>> "profile" (startup script) >>>> >>>> The above might hopefully be improved, but is good enough. >>>> >>>> Could the J distribution be updated such that jqt.cmd has %* appended to >>>> the last line? >>>> What modifications need be made to unix/osx such that Jqt (with default >>>> installation) can at least load a script at startup? >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>> >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> -- >> regards, >> ==================================================== >> GPG key 1024D/4434BAB3 2008-08-24 >> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >> gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 > > > -- > regards, > ==================================================== > GPG key 1024D/4434BAB3 2008-08-24 > gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 > gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
