Re: Distinguishing CLI from GUI

2011-06-16 Thread Richard Gaskin
Trevor DeVore wrote: On Wed, Jun 15, 2011 at 12:16 PM, Richard Gaskin ambassador at fourthworld.com wrote: @All: Anyone know a way to run facelessly from the command line in Windows and quit after executing without having Windows think it's an error? Shot in the dark. What if you

Re: Distinguishing CLI from GUI

2011-06-16 Thread Richard Gaskin
Warren Samples wrote: Just to point out, although I'm sure you noticed; while I do get the promised $ vars, which appears to be not working for you, the -ui flag is not being stored here, and it seems you're interested in getting that. That the $ values exist at all would indicate

Re: Distinguishing CLI from GUI

2011-06-16 Thread Andre Garzia
On Thu, Jun 16, 2011 at 11:04 AM, Richard Gaskin ambassa...@fourthworld.com wrote: Warren Samples wrote: Just to point out, although I'm sure you noticed; while I do get the promised $ vars, which appears to be not working for you, the -ui flag is not being stored here, and it seems

Re: Distinguishing CLI from GUI

2011-06-16 Thread Richard Gaskin
Mark Wieder wrote: @All: Anyone know a way to run facelessly from the command line in Windows and quit after executing without having Windows think it's an error? I did point out earlier that the way I execute faceless apps in Windows is by hiding the stack in the preOpenStack handler, not by

Re: Distinguishing CLI from GUI

2011-06-16 Thread Mark Wieder
Richard- Thursday, June 16, 2011, 7:45:08 AM, you wrote: I saw that and may try it, but initially I was reluctant to because of the issues with trying to run that way on Linux servers, which don't have GUI support. Forgive my ignorance, but I've never worked with IIS: Do the server

Re: Distinguishing CLI from GUI

2011-06-16 Thread Trevor DeVore
On Thu, Jun 16, 2011 at 9:51 AM, Richard Gaskin ambassa...@fourthworld.comwrote: Thanks for that - I'll give it a try. But I'll admit that I'm now more mystified than before: How did you discover that you can pass arguments to the quit command? I don't believe that's documented. Someone

Re: Distinguishing CLI from GUI

2011-06-15 Thread Richard Gaskin
Warren Samples wrote: This simple script: on openStack put $0 $1 $2 $3 into url file:/home/warren/Documents/launchtestLOG.txt if $3 is -h then get shell(opera) end openStack seems to work as expected with and without -ui. Using this command: ''launchTest -ui -Q some-param -h

Re: Distinguishing CLI from GUI

2011-06-15 Thread Trevor DeVore
On Wed, Jun 15, 2011 at 12:16 PM, Richard Gaskin ambassa...@fourthworld.com wrote: @All: Anyone know a way to run facelessly from the command line in Windows and quit after executing without having Windows think it's an error? Shot in the dark. What if you explicitly an exit code of zero to

Re: Distinguishing CLI from GUI

2011-06-15 Thread Warren Samples
On Wednesday, June 15, 2011 11:16:19 AM Richard Gaskin wrote: seems to work as expected with and without -ui. Using this command: ''launchTest -ui -Q some-param -h launches Opera and creates the file with this line: launchTest -Q some-param -h. Thanks for that info. I've had no such luck

Re: Distinguishing CLI from GUI

2011-06-15 Thread Mark Wieder
Richard- Wednesday, June 15, 2011, 9:16:19 AM, you wrote: @Mark Weider: are you able to get -ui in any of the $ vars in your Fedora setup? I believe the engine eats *all* the commandline arguments it uses itself rather than passing them on. @All: Anyone know a way to run facelessly from

Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
As Todd Geist quoted here earlier, in the Dictionary entry for $ it says: If you start up the application from the command line (on OS X, Unix or Windows systems), the command name is stored in the global variable $0 and any arguments passed on the command line are stored in

Re: Distinguishing CLI from GUI

2011-06-13 Thread Björnke von Gierke
bug On 13 Jun 2011, at 14:41, Richard Gaskin wrote: As Todd Geist quoted here earlier, in the Dictionary entry for $ it says: If you start up the application from the command line (on OS X, Unix or Windows systems), the command name is stored in the global variable $0 and any

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Bug in the documentation, or the implementation? Any workaround to determine if launched facelessly? -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode developers: http://www.LiveCodeJournal.com LiveCode Journal blog:

Re: Distinguishing CLI from GUI

2011-06-13 Thread Mark Schonewille
Hi Richard, What does the environment function return, if launched with -ui? -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Download the Installer Maker

Re: Distinguishing CLI from GUI

2011-06-13 Thread Björnke von Gierke
err, sorry for being unclear. I mean it's a bug as in, it should work as you expected. in addition, there's no workaround that i'd know of. On 13 Jun 2011, at 15:50, Richard Gaskin wrote: Bug in the documentation, or the implementation? Any workaround to determine if launched facelessly?

Re: Distinguishing CLI from GUI

2011-06-13 Thread Andre Garzia
if you can live with a script launches instead of calling the standalone directly then you can set some environment variables by hand and then check the on the startup handler, something along the lines of: standalone.sh: #!/bin/bash export ARGS=$1 ./standalone.x86 And then you check for the

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Mark Schonewille wrote: Hi Richard, What does the environment function return, if launched with -ui? It returns standalone application whether launched with -ui or not. @Andre: Thanks for the suggestion, but I'd really like to keep things simple for the user so I'd prefer not to rely on an

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Thanks for the clarification - logged: http://quality.runrev.com/show_bug.cgi?id=9582 -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode developers: http://www.LiveCodeJournal.com LiveCode Journal blog:

Re: Distinguishing CLI from GUI

2011-06-13 Thread Andre Garzia
On Mon, Jun 13, 2011 at 11:25 AM, Richard Gaskin ambassa...@fourthworld.com wrote: Mark Schonewille wrote: Hi Richard, What does the environment function return, if launched with -ui? It returns standalone application whether launched with -ui or not. @Andre: Thanks for the

Re: Distinguishing CLI from GUI

2011-06-13 Thread J. Landman Gay
On 6/13/11 7:41 AM, Richard Gaskin wrote: 2. If this is indeed a documentation bug and what I see in my tests is what happens for everyone, how can I determine whether the app was launched with -ui or not? Have you tried if there is a window mainstack then... ? -- Jacqueline Landman Gay

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Jacque wrote: On 6/13/11 7:41 AM, Richard Gaskin wrote: 2. If this is indeed a documentation bug and what I see in my tests is what happens for everyone, how can I determine whether the app was launched with -ui or not? Have you tried if there is a window mainstack then... ? Thanks for

Re: Distinguishing CLI from GUI

2011-06-13 Thread Warren Samples
On Monday, June 13, 2011 07:41:32 AM Richard Gaskin wrote: As Todd Geist quoted here earlier, in the Dictionary entry for $ it says: If you start up the application from the command line (on OS X, Unix or Windows systems), the command name is stored in the global variable $0

Re: Distinguishing CLI from GUI

2011-06-13 Thread Björnke von Gierke
ah, so maybe this is not a bug, but a hidden feature... maybe -s saves uhm stacks... or more likely, it specifies a stack to open? is there any documentation about what is accepted besides -ui by LC apps? On 13 Jun 2011, at 18:51, Warren Samples wrote: Richard, It seems to be working here

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Björnke von Gierke wrote: ah, so maybe this is not a bug, but a hidden feature... maybe -s saves uhm stacks... or more likely, it specifies a stack to open? is there any documentation about what is accepted besides -ui by LC apps? If you dive into the engine you can dig up all the old

Re: Distinguishing CLI from GUI

2011-06-13 Thread Richard Gaskin
Warren Samples wrote: It seems to be working here although certain letters seem not to be usable. For example -s does not work. I can get an answer dialog to return -h when used as a cl flag and the app will do something if there is a variable $x which equals -h. as a silly example, this

Re: Distinguishing CLI from GUI

2011-06-13 Thread Phil Davis
On 6/13/11 10:49 AM, Richard Gaskin wrote: Björnke von Gierke wrote: ah, so maybe this is not a bug, but a hidden feature... maybe -s saves uhm stacks... or more likely, it specifies a stack to open? is there any documentation about what is accepted besides -ui by LC apps? If you dive into

Re: Distinguishing CLI from GUI

2011-06-13 Thread Mark Wieder
Richard- Monday, June 13, 2011, 9:53:30 AM, you wrote: On Windows XP, however, I run into an odd issue: I can find a way to have the app quit itself after launching with -ui without generating an OS error. Anyone here have experience using faceless standalones on Windows that might help

Re: Distinguishing CLI from GUI

2011-06-13 Thread Mark Wieder
Warren- Monday, June 13, 2011, 9:51:09 AM, you wrote: using this command: '/myApp -h a-param -o some-param' answers /myApp -h a-param -o some-param and then answers hooboy, it works. Note also that the engine differentiates between upper- and lower-case commandline arguments, so that gives

Re: Distinguishing CLI from GUI

2011-06-13 Thread Warren Samples
On Monday, June 13, 2011 12:54:04 PM Richard Gaskin wrote: Warren Samples wrote: It seems to be working here although certain letters seem not to be usable. For example -s does not work. I can get an answer dialog to return -h when used as a cl flag and the app will do something if there