On Sat, Aug 17, 2013 at 3:49 PM, Mark Schonewille
m.schonewi...@economy-x-talk.com wrote:
On Windows and Linux, you can start a standalone from the command line with
parameteres. The parameters can be found in $0, $1 etc. You can do the same
on Mac OS X, but you will have probems with the
Hi Mike,
In that case, sockets are indeed not the right approach. It should be
possible to use a standalone as a command line utility, with parameters
as I explained before.
Hiding the LiveCode interface would seem more elegant to me. Maybe you
can still use -u to hide the user interface
Mark W. - I'm pretty sure that 4D can capture stderr. Are you saying that
when LC sends output to stderr I won't be able to capture it?
Mark S. - yeah, I was thinking of that. Originally I was going to move the
window offscreen, but -ui is probably better.
Thanks guys! More questions to come,
Mike-
Thursday, August 22, 2013, 5:15:40 AM, you wrote:
Mark W. - I'm pretty sure that 4D can capture stderr. Are you saying that
when LC sends output to stderr I won't be able to capture it?
No, not saying that at all, sorry. Just that it *also* can go to the
console. Capturing the stderr
Mark Wieder wrote:
Mike-
Wednesday, August 21, 2013, 7:56:25 PM, you wrote:
I'm doing this on Windoze
In that case, stderr will go directly to the console, while stdout
needs to be caught with redirection.
Mark, is this inconsistency between the Linux and Win builds a bug in LC
or a bug
Mike Kerner wrote:
Richard,
$# causes the script editor to mark the rest of the line as a comment. $#
still works?
The token works well, so that would be a bug - reported:
http://quality.runrev.com/show_bug.cgi?id=11122
--
Richard Gaskin
Fourth World
LiveCode training and consulting:
See my reply on the bug report.
On Thu, Aug 22, 2013 at 1:45 PM, Richard Gaskin
ambassa...@fourthworld.comwrote:
Mike Kerner wrote:
Richard,
$# causes the script editor to mark the rest of the line as a comment. $#
still works?
The token works well, so that would be a bug - reported:
Richard-
Thursday, August 22, 2013, 10:38:15 AM, you wrote:
Mark, is this inconsistency between the Linux and Win builds a bug in LC
or a bug in Windows?
Microsoft knows what's best for you better than you do.
Who told you you could question authority?
--
-Mark Wieder
Richard,
$# causes the script editor to mark the rest of the line as a comment. $#
still works?
On Mon, Aug 19, 2013 at 9:28 AM, Richard Gaskin
ambassa...@fourthworld.comwrote:
Mike, these tips for implementing CLI support in a standalone may help:
And Mark S., sorry, I wasn't ignoring you, I just didn't see your message.
I have a system that's written in 4D that needs some functionality added to
it. The code to do that is already written in LC. Converting it would
work, but why bother, when I can just create a standalone in LC that I call
And the reason that sockets aren't an option is because they aren't native
in 4D.
On Wed, Aug 21, 2013 at 9:57 PM, Mike Kerner mikeker...@roadrunner.comwrote:
And Mark S., sorry, I wasn't ignoring you, I just didn't see your message.
I have a system that's written in 4D that needs some
And one more thing - similar to writing to stdout, can I write to stderr?
On Wed, Aug 21, 2013 at 10:02 PM, Mike Kerner mikeker...@roadrunner.comwrote:
And the reason that sockets aren't an option is because they aren't native
in 4D.
On Wed, Aug 21, 2013 at 9:57 PM, Mike Kerner
Mike-
Wednesday, August 21, 2013, 7:07:41 PM, you wrote:
And one more thing - similar to writing to stdout, can I write to stderr?
Yes. I've lost track of what platform you're doing this on.
But anyway, yes.
--
-Mark Wieder
mwie...@ahsoftware.net
On 22/08/2013, at 12:07 PM, Mike Kerner wrote:
And one more thing - similar to writing to stdout, can I write to stderr?
I haven't been following this thread but as I've just implemented child process
control via open process for update in the parent and read from STDIN and write
to STDOUT
I'm doing this on Windoze
On Wed, Aug 21, 2013 at 10:47 PM, Monte Goulding
mo...@sweattechnologies.com wrote:
On 22/08/2013, at 12:07 PM, Mike Kerner wrote:
And one more thing - similar to writing to stdout, can I write to stderr?
I haven't been following this thread but as I've just
Mike-
Wednesday, August 21, 2013, 7:56:25 PM, you wrote:
I'm doing this on Windoze
In that case, stderr will go directly to the console, while stdout
needs to be caught with redirection.
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode
Mike, these tips for implementing CLI support in a standalone may help:
http://lists.runrev.com/pipermail/use-livecode/2013-April/186750.html
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers:
How about documentation so I can read up on it? I didn't see anything in
the docs.
On Sat, Aug 17, 2013 at 6:49 PM, Mark Schonewille
m.schonewi...@economy-x-talk.com wrote:
Hi Mike,
On Windows and Linux, you can start a standalone from the command line
with parameteres. The parameters can
applescript will be hard - windows. Sockets are not an option here, but
thanks.
On Sun, Aug 18, 2013 at 4:40 PM, Mark Schonewille
m.schonewi...@economy-x-talk.com wrote:
Hi Mike,
Search the dictionary for:
$
relaunch
socket
appleEvent
Search in the mailing list or on the forum for
Mike,
You still haven't explained what you want to do.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab
I thought there was a way to launch a LC app with parameters, i.e. stdin.
Maybe I'm thinking of another IDE.
Launching the app isn't the problem. It's passing the parameters to it at
launch. I could also create a file somewhere for the app to read.
On Fri, Aug 16, 2013 at 7:31 PM, Mark
Hi Mike,
On Windows and Linux, you can start a standalone from the command line with
parameteres. The parameters can be found in $0, $1 etc. You can do the same on
Mac OS X, but you will have probems with the GUI. On Windows, you can also use
the relaunch message to decide how a standalone
Hi Mike,
On Windows, your best option is probably to use sockets, if you are
trying to communicate between two LiveCode standalones.
If you want to communicate between a LiveCode standalone and another
non-LiveCode application, it depends on the options available in the
other application.
I can't remember how to set up a stack/standalone to respond to calls from
another application. This is on Windows. The other application will be
telling the stack/standalone to do something. There is no two-way
communication necessary.
--
On the first day, God created the heavens and the
24 matches
Mail list logo