Thanks for everyones help on this. I am getting closer. But I am still not
able to get all the way there.
My end goal is a server application that can run without a user logged in to
the machine. The server application should be able to handle requests ether
over HTTP or just plain sockets.
I h
Hello Todd
On 6 May 2011, at 22:52, Todd Geist wrote:
> Hello,
>
> I had nice long chat with Richard Gaskin yesterday. Amongst the myriad of
> topics we discussed was how to build simple apps that could be started from
> the command line and run silently in the back ground. I have been trying t
Just add this key and string to the pList file...
LSUIElement
1
I'm not sure if it matters where in the pList file you put this but I always
put it immediately before the LSGetAppDiedEvents key.
If you want more info then head over to Ken's website...
http://www.sonsothunder.com/devres/live
On 5/6/11 10:44 PM, David C. wrote:
Best I can tell, Todd just wants to be able to launch a LC executable
on the Mac, but with it running as a hidden or background process,
without an icon showing up in the Dock. Is that correct Todd?
On Windows, this really simple sample code seems to do the jo
On Friday, May 06, 2011 03:28:14 PM Todd Geist wrote:
> But it does appear in my Dock, as I
> expected, but don't want.
I believe this can be avoided by setting a key value in the .plist file inside
the app bundle. I think you'll
find this info with a google search.
Good luck!
Warren
__
Best I can tell, Todd just wants to be able to launch a LC executable
on the Mac, but with it running as a hidden or background process,
without an icon showing up in the Dock. Is that correct Todd?
On Windows, this really simple sample code seems to do the job:
on preOpenStack
set the hideCon
On May 6, 2011, at 8:10 AM, Todd Geist wrote:
The current user guide does have the following section on page 146
*Command-line argument variables*
If you start up the application from a command line, the command
name is
stored in the variable $0 and any arguments passed on the command
line
On Fri, 6 May 2011 13:28:14 -0700, Todd Geist
wrote:
thanks Mark
I was able to get the terminal commands to work although you need to
reference the engine inside the OSX package. So I had to type the
following
at the terminal
/Applications/LiveCode\ 4.6.app/Contents/MacOS/LiveCode -h
...ah
thanks Mark
I was able to get the terminal commands to work although you need to
reference the engine inside the OSX package. So I had to type the following
at the terminal
/Applications/LiveCode\ 4.6.app/Contents/MacOS/LiveCode -h
The same also works for standalones. You have to reference the e
On Fri, 6 May 2011 08:10:52 -0700, Todd Geist
wrote:
Is this just left over cruft?
Well, the -h argument is used by the engine, so that's just wrong.
However...
Not only is this *not* just leftover cruft, but I have applications
that *rely* on passing and parsing commandline arguments.
Ty
I used an old engine to run a Linux server process a while ago. It
required Xvfb (virtual frame buffer) to be running so the engine had a
display to write to. I think that's as close as faceless as you can get
with LC - I'll try and dig out the version I was using and get you some
more info
The old engine used to be able to execute scripts. That is, you could
invoke the engine using something like this:
#!/path/to/engine
on startup
put "hello"
end startup
IIRC this functionality was removed at the time that the "on-rev"
product was launched. Perhaps the functionality was rem
Does anybody know if the old engine allowed you to build a standalone that
could be started with no UI and stay running in the background?
Todd
On Fri, May 6, 2011 at 8:45 AM, Matthias Rebbe http://www.geistinteractive.com>
805-419-9382
___
use-livecode
On Friday, May 06, 2011 10:10:52 AM Todd Geist wrote:
> Command-line argument variables
Hi Todd,
It looks as if you have to program your app to respond according to what values
any such variable(s) contain,
such as
'if $1 is "true" then doSomeThing'
It looks af it will take some craft in ord
Ah,
now i understand. You are right, command line mode was possible up to version
3.5.
If you need command line mode and if you have an active maintenance, why not
asking supp...@runrev.com
for a key for v 3.5? I am pretty sure they will help.
Regards,
Matthias
Am 06.05.2011 um 17:20 schrieb
Thanks very much for your response, but I don't think that is actually doing
anything other than starting the application using the OS. It is just as if
you double clicked it. I don't think that is what I am looking for. I
think I am looking for command line mode
Todd
On Fri, May 6, 2011 at 8:
The current user guide does have the following section on page 146
*Command-line argument variables*
If you start up the application from a command line, the command name is
stored in the variable $0 and any arguments passed on the command line are
stored in numbered variables starting with the *
Hi Todd,
you have to use open on Mac os x
E.g. open 'served.app'would open the application served.app.
If your are not in the folder, where the application resides you can use also
paths
open /whateverfolder/served.app
HTH
Matthias
Am 06.05.2011 um 16:56 schrieb Todd Geist:
> I just
I just stumbled on something that would make me sad.
It seems that maybe command line mode has been removed in anything after
version 4. Id this is true then I think it is very sad.
Can anyone confirm this?
Todd
On Fri, May 6, 2011 at 7:52 AM, Todd Geist wrote:
> Hello,
>
> I had nice long ch
Hello,
I had nice long chat with Richard Gaskin yesterday. Amongst the myriad of
topics we discussed was how to build simple apps that could be started from
the command line and run silently in the back ground. I have been trying to
do a little R and D on this idea, but I am stymied by the fact t
20 matches
Mail list logo
