Re: Script Editor future (was Open Source Kickstarter Report Card)

> On 29 Aug 2015, at 10:22 pm, Peter TB Brett wrote: > > This looks like the sort of thing that's best off being looked at by Mark > Waddingham. Unfortunately my last day before my annual holiday is the day > before he gets back from his annual holiday, so I'm not going to be able to > bring

Re: Script Editor future (was Open Source Kickstarter Report Card)

I'm still in the early days of using the sts plugin but I believe the restriction on not having the script editor window open at the same time is to avoid clashes if edits are made to the same script in both places. On Sat, Aug 29, 2015 at 9:15 AM Richard Gaskin wrote: > Kay C Lan wrote: > > > O

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan wrote: On Fri, Aug 28, 2015 at 10:46 PM, Richard Gaskin wrote: Kay C Lan wrote: a better mechanism to track the changes and transfer those back and forth - that improvement can only be done from the mothership. What's needed? Let's make it so. Love the positive attitude :-) J

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 2015-08-29 08:53, Monte Goulding wrote: Hi Peter Has anyone seen my post on the engine forum about a scriptOnly property for stacks: http://forums.livecode.com/viewtopic.php?f=66&t=25065 Happy to contribute it This looks like the sort of thing that's best off being looked at by Mark Wadd

Re: Script Editor future (was Open Source Kickstarter Report Card)

That URL is not working. Probably should be: http://forums.livecode.com/viewtopic.php?f=66&t=25065&p=130099&hilit=scriptOnly#p130099 Peter On Aug 29, 2015, at 12:53 AM, Monte Goulding wrote: > scriptOnly ___ use-livecode mailing list use-

Re: Script Editor future (was Open Source Kickstarter Report Card)

Hi Peter Has anyone seen my post on the engine forum about a scriptOnly property for stacks: http://forums.livecode.com/viewtopic.php?f=66&t=25065 Happy to contribute it Cheers Monte Sent from my iPhone > On 29 Aug 2015, at 5:00 pm, Peter TB Brett wrote: > > Your assumptions are correct.

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 2015-08-29 04:43, Kay C Lan wrote: Oh, and just a slight tangent. I've seen it mentioned before but it hadn't really registered until I was playing with LC8 yesterday, but the new 'Script only Stack' would seem to be the perfect beast to offer up as a guinea pig for Text Editor integration

Re: Script Editor future (was Open Source Kickstarter Report Card)

Oh, and just a slight tangent. I've seen it mentioned before but it hadn't really registered until I was playing with LC8 yesterday, but the new 'Script only Stack' would seem to be the perfect beast to offer up as a guinea pig for Text Editor integration. If my assumptions* are correct (unlikely)

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Fri, Aug 28, 2015 at 10:46 PM, Richard Gaskin wrote: > Kay C Lan wrote: > > a better mechanism to track the changes and transfer those back and >> forth - that improvement can only be done from the mothership. >> > > What's needed? > > Let's make it so. > Love the positive attitude :-) >From

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan wrote: The problem though, was that stsMLXEditor was a bit of a patch job which needed a better mechanism to track the changes and transfer those back and forth - that improvement can only be done from the mothership. What's needed? Let's make it so. -- Richard Gaskin Fourth Worl

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/28/2015 01:30 PM, Kay C Lan wrote: On Thu, Aug 27, 2015 at 4:47 PM, Richmond wrote: I would be most interested to see a *coherent and numbered list* of these "issues" rather than a chorus of people saying how awful the scriptEditor is. Off the top of my head: 1) copy & paste via ke

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Fri, Aug 28, 2015 at 4:53 PM, Peter TB Brett wrote: I was bored one evening (in my "spare" time) and decided to explore adding > new syntax highlighting rules to Atom. > Now wonder the story isn't more exciting. You really need to get out more ;-) _

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Thu, Aug 27, 2015 at 4:47 PM, Richmond wrote: I would be most interested to see a *coherent and numbered list* of these > "issues" > rather than a chorus of people saying how awful the scriptEditor is. > Off the top of my head: 1) copy & paste via keyboard How many times have you copied

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 28/08/2015 09:17, Kay C Lan wrote: I don't use Atom but from some recent posting it appears that some kind of LC/Atom connection has been made. I wonder if that may have been driven by the amount of time the LC Team spend at Github and Atom is the Github team developed Text Editor? Guess I b

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Thu, Aug 27, 2015 at 3:49 PM, RunRevPlanet wrote: > > One of the promoted strengths of LiveCode is that it is "live coding". In > other > words I can make a change in my script and immediately see the effect. > > Now while I understand the virtues of using the external text editor of > your >

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/27/2015 10:41 PM, Mike Bonner wrote: You did the obvious, and restarted LC after placing the plugin right? If you didn't restart lc, and you don't want to, an easy way to force a re-read of the plugins folder is to go into the plugin settings. You don't have to do anything, just going to

Re: Script Editor future (was Open Source Kickstarter Report Card)

It's showing up for me now, It's in my personal plugins folder but still doesn't show up in the Development Plugins list or the Plugin Settings list, maybe because the stack name begins with "rev"? It's hard to locate stuff in the plugin settings list since they don't seem to be in any particular

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 2015-08-27 21:30, Mike Bonner wrote: I got it to show up finally (7.0.6 on windows) I installed it in my personal plugins folder rather than the 7.0.6 plugins folder. On start of lc, still didn't show up, but went to plugin settings and set it to start when chosen from the plugins menu. Ch

Re: Script Editor future (was Open Source Kickstarter Report Card)

I got it to show up finally (7.0.6 on windows) I installed it in my personal plugins folder rather than the 7.0.6 plugins folder. On start of lc, still didn't show up, but went to plugin settings and set it to start when chosen from the plugins menu. Changed it from "invisible" to modeless. Restar

Re: Script Editor future (was Open Source Kickstarter Report Card)

Peter Haworth wrote: > It would of course be better if this was all built into the IDE script > editor but this is a great substitute until that happens. "Better" is nice, but "now" can be even nicer. :) Plugins are not only easily shared, but also self-contained, so they make a great way to ex

Re: Script Editor future (was Open Source Kickstarter Report Card)

I am having the same problem. The plugin doesn't load and it's not listed in the Plugins menu or in the Configure Plugins menu. This is with LC 6.6, and yes I did restart LC after installing it. I opened the plugin manually from the File Open menu and set it up to use the OSX Textmate editor. I

Re: Script Editor future (was Open Source Kickstarter Report Card)

You did the obvious, and restarted LC after placing the plugin right? If you didn't restart lc, and you don't want to, an easy way to force a re-read of the plugins folder is to go into the plugin settings. You don't have to do anything, just going to the settings dialog forced the re-read. On

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/27/2015 09:02 PM, Richard Gaskin wrote: Kay C Lan wrote: > On Thu, Aug 27, 2015 at 9:03 AM, RunRevPlanet wrote: > >> None of my comments are from the perspective that enabling LiveCode >> to use an external editor is a bad thing. > > So we agree then. As Richard said, choice is a good thin

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan wrote: > On Thu, Aug 27, 2015 at 9:03 AM, RunRevPlanet wrote: > >> None of my comments are from the perspective that enabling LiveCode >> to use an external editor is a bad thing. > > So we agree then. As Richard said, choice is a good thing. > >> More that for a cross platform IDE, wri

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/27/2015 10:49 AM, RunRevPlanet wrote: Kay C Lan said: > take the smart route and build adequate > text handling into their products but allow > integration with the industry leaders. One of the promoted strengths of LiveCode is that it is "live coding". In other words I can make a

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan said: > take the smart route and build adequate > text handling into their products but allow > integration with the industry leaders. One of the promoted strengths of LiveCode is that it is "live coding". In other words I can make a change in my script and immediately see the effect

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Thu, Aug 27, 2015 at 9:03 AM, RunRevPlanet wrote: > > None of my comments are from the perspective that enabling LiveCode to use > an > external editor is a bad thing. > > So we agree then. As Richard said, choice is a good thing. > More that for a cross platform IDE, written in it's support

Re: Script Editor future (was Open Source Kickstarter Report Card)

So has anyone looked at dp3 to see if the script editor is strapped, yet, or are we still a ways off from that? Once it's more workable (because you oughta try working on that code, now. Ugh), hopefully we can all make it better. On Wed, Aug 26, 2015 at 9:03 PM, RunRevPlanet wrote: > Kay C Lan

Re: Script Editor future (was Open Source Kickstarter Report Card)

Thierry Douez said: > If you are interested to this project, > do you have some knowledge or links about > adding a language, compilation tools,.. > to geany? No I don't know of any links and haven't done that sort of work before, so I am afraid I can't be much help. I will have a look arou

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan wrote: On Wed, Aug 26, 2015 at 5:42 AM, RunRevPlanet wrote: For all three I use Geany. It's not clear to me what integration Geany and Webstorm have built in, but let's dream and say LiveCode allowed you to use Geany as it'

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Wed, Aug 26, 2015 at 5:42 AM, RunRevPlanet wrote: > > For all three I use Geany. > > > It's not clear to me what integration Geany and Webstorm have built in, but let's dream and say LiveCode allowed you to use Geany as it's Script Editio

Re: Script Editor future (was Open Source Kickstarter Report Card)

Kay C Lan said: > which IDE/Text Editor do you use on Linux, > which one on Win and which one on OS X. For all three I use Geany. http://www.geany.org/ Same IDE on all platforms. Same features on all platforms, same keyboard shortcuts. I can jump from one machine/OS to another and simply keep

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Mon, Aug 24, 2015 at 8:40 PM, RunRevPlanet wrote: > > I care because when typing code, I don't want to have to think about what > machine I am using and adjust my fingers to suits. > Sorry I missed it, excluding LC, which IDE/Text Editor do you use on Linux, which one on Win and which one on

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 8/24/2015 3:38 PM, Richard Gaskin wrote: Also performance: I do most of my scripting on a 3 GHz Haswell, and even with colorization off it struggles to keep up with even my own modest typing speed. So you notice a difference then? I still haven't worked with my humongous script in LC 7 so

Re: Script Editor future (was Open Source Kickstarter Report Card)

J. Landman Gay wrote: > I am likely the only person who has always kept coloRizing turned > off. Coming from HyperCard, I was used to it and the rainbow hues > of a colorized script distracted me. I couldn't concentrate > on the content, I kept seeing the colors. There are at least two of us. On

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 8/23/2015 11:46 PM, Dr. Hawkins wrote: On Sun, Aug 23, 2015 at 8:44 AM, J. Landman Gay wrote: Just out of curiosity, does it get better if you turn off script colonizing? As others have already made the cheap (and funny) one, I'll pass. Until the last pun, I wasn't reading the first sy

Re: Script Editor future (was Open Source Kickstarter Report Card)

> On Aug 24, 2015, at 3:14 AM, Charles Warwick > wrote: > > I recently modified the script editor to do exactly that, as a long list of > handlers was getting very annoying, and it has been working very well. > > Here are two screenshots of the modified script editor: > > https://www.dropbox

Re: Script Editor future (was Open Source Kickstarter Report Card)

Charles Warwick said: > I am happy to submit the changes to the > git repository if it is of any interest > to the LC team. Not the bookmarks I am hoping for, but a handler filter is definitely a great feature to have. Please do submit your work. Kay C Lan said: > I don't care if the LC Sc

Re: Script Editor future (was Open Source Kickstarter Report Card)

I recently modified the script editor to do exactly that, as a long list of handlers was getting very annoying, and it has been working very well. Here are two screenshots of the modified script editor: https://www.dropbox.com/s/4bsjmbftg6uue9w/LC%20handler%20filter%20list%20empty.png?dl=0

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 8/23/2015 8:57 PM, Kay C Lan wrote: On Sun, Aug 23, 2015 at 11:55 PM, J. Landman Gay wrote: > >When the last script editor revision was released it included hooks so you >could work in any external editor. Was that pre or post GLX2? More information would be welcome. I manually take script

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Sun, Aug 23, 2015 at 8:44 AM, J. Landman Gay wrote: > Just out of curiosity, does it get better if you turn off script > colonizing? > As others have already made the cheap (and funny) one, I'll pass. But I didn't know that this could be done. I'll try. Hilting a script was the first thing

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Sun, Aug 23, 2015 at 11:55 PM, J. Landman Gay wrote: > > When the last script editor revision was released it included hooks so you > could work in any external editor. Was that pre or post GLX2? More information would be welcome. I manually take scripts in and out of BBEdit and it would be

RE: Script Editor future (was Open Source Kickstarter Report Card)

> Is "script colonizing" what happens when bugs creep into your > scripts and settle there?? Its nothing compared with a script colonoscopy. Best regards, Lynn Fredricks Paradigma Software http://www.paradigmasoft.com Valentina SQL Server: The Ultra-fast, Royalty Free Database Server __

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/23/2015 02:51 AM, Ali Lloyd wrote: It's not possible for it to have gotten worse in LC 7, as the 7 IDE is identical to the 6 IDE except for branding. Thanks. I stand corrected then. Still trying to track down why this is such a CPU hog in LC7. I'll remove the extra checks I put in for t

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Sun, 23 Aug 2015 at 16:18, Dr. Hawkins wrote: On Sun, Aug 23, 2015 at 2:51 AM, Ali Lloyd wrote: > It's not possible for it to have gotten worse in LC 7, as the 7 IDE is > identical to the 6 IDE except for branding > It does, however, seem to be a huge leap back from 5. The delays in 5 were

Re: Script Editor future (was Open Source Kickstarter Report Card)

On August 23, 2015 11:04:46 AM CDT, Mark Wieder wrote: >On 08/23/2015 08:50 AM, Peter M. Brigham wrote: > >> Is "script colonizing" what happens when bugs creep into your scripts >and settle there?? > >Don't you just hate it when that happens? Okay auto-correct, I've had it with your shirt. --

Re: Script Editor future (was Open Source Kickstarter Report Card)

On August 23, 2015 10:50:13 AM CDT, "Peter M. Brigham" wrote: >On Aug 23, 2015, at 11:44 AM, J. Landman Gay wrote: > >>> I am not exaggerating at frequently seeing a 2-3 second lag time, >and >>> (almost?) never under a second. >> >> Just out of curiosity, does it get better if you turn off scrip

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/23/2015 08:50 AM, Peter M. Brigham wrote: Is "script colonizing" what happens when bugs creep into your scripts and settle there?? Don't you just hate it when that happens? -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: Script Editor future (was Open Source Kickstarter Report Card)

On August 23, 2015 1:51:35 AM CDT, Kay C Lan wrote: >I wonder if someone >from the mothership sat down and said "right, we are going to make our >Script Editor compatible with the top 3 text editors on each platform, >how do we make that happen." if a lot of those hooks could be simplified >and th

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Aug 23, 2015, at 11:44 AM, J. Landman Gay wrote: >> I am not exaggerating at frequently seeing a 2-3 second lag time, and >> (almost?) never under a second. > > Just out of curiosity, does it get better if you turn off script colonizing? Is "script colonizing" what happens when bugs creep in

Re: Script Editor future (was Open Source Kickstarter Report Card)

On August 23, 2015 10:18:13 AM CDT, "Dr. Hawkins" wrote: > >I am not exaggerating at frequently seeing a 2-3 second lag time, and >(almost?) never under a second. Just out of curiosity, does it get better if you turn off script colonizing? -- Jacqueline Landman Gay | jac...@hyperact

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Sun, Aug 23, 2015 at 2:51 AM, Ali Lloyd wrote: > It's not possible for it to have gotten worse in LC 7, as the 7 IDE is > identical to the 6 IDE except for branding > It does, however, seem to be a huge leap back from 5. The delays in 5 were merely sluggish enough to be annoying, irc. Now

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Sun, Aug 23, 2015 at 2:35 AM Mark Wieder wrote: > > The IDE has way too > many hooks that need to be trapped in a frontscript in order to use a > editor from the built-in one. And it's gotten worse, not > better, with LC 7/8. > It's not possible for it to have gotten worse in LC 7, as the 7

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 2015-08-23 02:01, RunRevPlanet wrote: Then then there are bookmarks which are missing. The problem with the handler list pane of the current editor is that with a stack or card with many handlers there is a constant need to scroll up and down that if the two handlers I am working on have n

Re: Script Editor future (was Open Source Kickstarter Report Card)

Mike Kerner said: > effort should instead be spent on a > BBEdit/TextWrangler plugin or some > method for leveraging someone else's > text editor. Malte Brill said: > +1, just eclipse… ;-). The Dr. said: >vi, of course . . . >If you want to use that heretical emacs contraption, you'll

Re: Script Editor future (was Open Source Kickstarter Report Card)

I remember someone posted that they used red dot breakpoints as bookmarks. I have them in lcstackbrowser too. But they should be in the script editor. On Sat, Aug 22, 2015, 9:01 PM Dr. Hawkins wrote: > On Saturday, August 22, 2015, RunRevPlanet wrote: > > > > > the problem with this approach is

Re: Script Editor future (was Open Source Kickstarter Report Card)

On Saturday, August 22, 2015, RunRevPlanet wrote: > > the problem with this approach is that you need to find a single editor > that > runs on Linux, OS X Windows. vi, of course . . . If you want to use that heretical emacs contraption, you'll get performance almost as bad as the current IDE.

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/22/2015 07:41 PM, J. Landman Gay wrote: I've often wished there was a way to go back where I came from, but it is a one-way trip for now. It's a feature in glx2, but I'm not sure how to patch it into the built-in editor. -- Mark Wieder ahsoftw...@gmail.com

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 8/22/2015 8:01 PM, RunRevPlanet wrote: As a couple of concrete examples, that are mentioned elsewhere, but are repeated again in more detail, because this is a new thread. I'll agree with all your suggestions, you've laid out a good list of things the editor should do and I've wished for s

Re: Script Editor future (was Open Source Kickstarter Report Card)

On 08/22/2015 06:01 PM, RunRevPlanet wrote: I would be surprised if the amount of work making a plugin for another system would be less than just fixing what currently exists. from the work I've done on glx2 I'd second that. The IDE has way too many hooks that need to be trapped in a frontsc

Re: Script Editor future (was Open Source Kickstarter Report Card)

Mike Kerner said: > effort should instead be spent on a > BBEdit/TextWrangler plugin or some > method for leveraging someone else's > text editor. the problem with this approach is that you need to find a single editor that runs on Linux, OS X Windows. Without using a single editor/IDE on all