My need for external editors is mostly for Windows (again, the Windows
machines I use are very very old).
I also like reviewing and editing code on my iPad when I am on the go, so
having external scripts is useful even when I don't have LC running. What
else am I going to do at a red light?
but I
I'll pitch in for lunch but I can't fund the whole project.
Bob S
> On Jan 14, 2020, at 14:08 , Richard Gaskin via use-livecode
> wrote:
>
> Bob Sneidar wrote:
>
> > Let's remember this is just Windows we are talking about. I have no
> > issues whatsoever with the OS X version of LC Script
Bob Sneidar wrote:
> Let's remember this is just Windows we are talking about. I have no
> issues whatsoever with the OS X version of LC Script Editor...
While performance issues are most evident on Windows, there's some
noticeable lag on Mac too. Most who use external editors here are on Mac.
Let's remember this is just Windows we are talking about. I have no issues
whatsoever with the OS X version of LC Script Editor, but the few times I
really needed to code and debug in Windows it was like scratching my eyes out
with a toothpick.
Bob S
> On Jan 14, 2020, at 12:09 , Kaveh Bazar
The slow editing in LiveCode is a big drawback for me. It is slow, spacing
is usually off till you hit tab, and generally not efficient.
On Tue, 14 Jan 2020 at 20:06, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Brian Milby wrote:
> > I would offer a clarification fo
Brian Milby wrote:
> I would offer a clarification for ScriptTracker...
I didn't mean to imply your fine tool's only purpose was to help people
get around a slow Script Editor. It is indeed very useful for its
intended purposes.
But when we start using tools intended for all sorts of things
I would offer a clarification for ScriptTracker: while the files it exports
could be used as-is for SoS behaviors, that is not the goal of the tool. One
goal is to allow editing of scripts in external editors (performance is one
reason, but there are others too). A larger goal is to allow Git
Greg (Pink) Miller wrote:
ScriptTracker was definitely the tool I needed. I didn't need an external
script for any reason other than faster editing.
If people are use SoS solely to get away from performance issues in the
Script Editor, rather than add a pile of other tools to make SoS
develop
ScriptTracker was definitely the tool I needed. I didn't need an external
script for any reason other than faster editing.
On Sat, Jan 11, 2020 at 10:43 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:
> And if you want to edit scripts in an external editor, my tool may be
And if you want to edit scripts in an external editor, my tool may be useful to
you:
https://github.com/bwmilby/scriptTracker
It would support putting the scripts themselves into a repository so you could
track changes. It generates a consolidated diff every time it exports scripts.
Thanks,
Br
No revision control. For people working in a "1 human silo"
Is there a reason not to just put the script into a button and set the
stack behavior to that? That's what I do when I don't want extra files in
my build.
___
use-livecode mailing list
use-livec
Aha. You old edge-case, you.
:)
On 1/8/20 2:16 PM, Greg (Pink) Miller via use-livecode wrote:
I could just copy the script into the stack script at build time, but I was
hoping not to.
Here's the story... this particular program is being developed on a
painfully old and slow machine. Livecode'
I could just copy the script into the stack script at build time, but I was
hoping not to.
Here's the story... this particular program is being developed on a
painfully old and slow machine. Livecode's script editor works horribly on
this machine, there is a horrible lag in typing and cutting, cop
+1 from an old guy. :-)
Bob S
> On Jan 8, 2020, at 10:37 , J. Landman Gay via use-livecode
> wrote:
>
> Is there a reason not to just put the script into a button and set the stack
> behavior to that? That's what I do when I don't want extra files in my build.
>
> Sometimes the old ways are
Is there a reason not to just put the script into a button and set the
stack behavior to that? That's what I do when I don't want extra files in
my build.
Sometimes the old ways are best.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On
On 1/8/20 7:58 AM, Brian Milby via use-livecode wrote:
One option to eliminate the external file altogether would be to make it a
substack prior to building.
I have a PR in progress to allow script-only stacks to be substacks.
It's currently partially working.
--
Mark Wieder
ahsoftw...@gm
One option to eliminate the external file altogether would be to make it a
substack prior to building.
Thanks,
Brian
On Jan 8, 2020, 10:52 AM -0500, Greg (Pink) Miller via use-livecode
, wrote:
> I have my main stack "PanelManager.livecode" with a behavior script with a
> file name "panamana.lcs
Get the properties of the file and change them there. The issue is that you
have extensions hidden so Windows always assumes you want the default extension
appended to whatever you type. In the MacOS it asks you if you want to change
the dot extension.
Bob S
> On Jan 7, 2020, at 18:25 , Greg
I have my main stack "PanelManager.livecode" with a behavior script with a
file name "panamana.lcs"
Upon compiling for Windows, the script file gets included in the folder
with the program but is renamed "panamana.lcs.livecode"
I would prefer not to have ".livecode" appended onto it.
> I have a
Greg (Pink) Miller wrote:
> I have a script only stack that is the behavior of a stack that
> i wish to compile. When I compile it for Windows, I have a
.livecodescript file in the folder. Is it possible to change that
> extension to .lcs
>
> So far all the shots at this I've taken end up appen
I have a script only stack that is the behavior of a stack that i wish to
compile. When I compile it for Windows, I have a .livecodescript file in
the folder. Is it possible to change that extension to .lcs
So far all the shots at this I've taken end up appending .livecode to the
end.
Can this be
21 matches
Mail list logo
