On 02/05/2016 01:01 PM, Richard Gaskin wrote:
> Another way is to set the visible of the stack to false. Another way
> is to set the location of the stack to somewhere off screen.
With all due respect to Mr. Wieder, I never use that option. One of the
great things about running LC facelessly
Dr. Hawkins wrote:
> I've seen a couple of references to "script only stacks".
>
> Are these just pieces of code? Outside of a standalone, would they
> be used as library stacks, or
They were introduced in the v6.7 series (6.7.4?), allowing a plain text
file that begins with a specific de
Good to know, thanks Ali!
Sent from my iPhone
> On 5 Feb 2016, at 7:00 PM, Ali Lloyd wrote:
>
> When you deploy a script-only stack as a standalone it is re-saved as a
> normal stack. Not doing so at the moment results in the standalone crashing
> on startup.
__
That all sounds right. Another method is to do everything in the startup
handler then quit at the end. Startup happens before the window is created.
Sent from my iPhone
> On 6 Feb 2016, at 7:23 AM, Matt Maier wrote:
>
> Please correct me if any of the following is wrong.
>
> So in general we
On Fri, Feb 5, 2016 at 12:00 AM, Ali Lloyd wrote:
> When you deploy a script-only stack as a standalone it is re-saved as a
> normal stack. Not doing so at the moment results in the standalone crashing
> on startup.
>
> On Fri, Feb 5, 2016 at 6:28 AM Monte Goulding wrote:
>
> >
> > > On 5 Feb 20
Matt Maier wrote:
> Please correct me if any of the following is wrong.
>
> So in general we can run a standalone executable from the command
> line. It will fire up in whatever way it knows how. Normally that
> means the GUI will appear and the program will read/write visually.
> But if the code
On Fri, Feb 5, 2016 at 12:00 AM, Ali Lloyd wrote:
> When you deploy a script-only stack as a standalone it is re-saved as a
> normal stack.
>
I've seen a couple of references to "script only stacks".
Are these just pieces of code? Outside of a standalone, would they be used
as library stacks,
Please correct me if any of the following is wrong.
So in general we can run a standalone executable from the command line. It
will fire up in whatever way it knows how. Normally that means the GUI will
appear and the program will read/write visually. But if the code knows to
listen on STDIN and r
On 02/04/2016 10:28 PM, Monte Goulding wrote:
The way to get rid of the GUI is use the -ui command line option.
Alternately, what I do is hide the stack in the startup handler. Or just
move it to an offscreen location. That way you don't have to deal with
any special command line options.
When you deploy a script-only stack as a standalone it is re-saved as a
normal stack. Not doing so at the moment results in the standalone crashing
on startup.
On Fri, Feb 5, 2016 at 6:28 AM Monte Goulding wrote:
>
> > On 5 Feb 2016, at 5:20 PM, Matt Maier wrote:
> >
> > So there isn't any spec
> On 5 Feb 2016, at 5:20 PM, Matt Maier wrote:
>
> So there isn't any special standalone option to compile a *.livecode file
> into a command line app like *.exe. I just compile a standalone for the
> appropriate system, somehow get rid of the GUI, and tell it how to
> read/write STDIN/STDOUT?
>
So there isn't any special standalone option to compile a *.livecode file
into a command line app like *.exe. I just compile a standalone for the
appropriate system, somehow get rid of the GUI, and tell it how to
read/write STDIN/STDOUT?
Is that as simple as compiling a script-only stack into a st
On 02/04/2016 09:02 PM, Matt Maier wrote:
Is there a way to write a Python file (or whatever) that reaches out to
Livecode, uses its text processing, or maybe hands it a livecode script,
then returns the result to be used by the Python file?
Indeed. I have a commercial middleware layer where a
> On 5 Feb 2016, at 4:02 PM, Matt Maier wrote:
>
> Can I call Livecode from other languages?
>
> I found this, which if I'm following it is a proof of concept that you can
> install livecode server, then tell it to turn on from the shell, then have
> it run scripts and return the output. That d
14 matches
Mail list logo
