Script Editor future (was Open Source Kickstarter Report Card)

Richmond richmondmathewson at
Fri Aug 28 02:17:38 EDT 2015

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 the settings dialog forced the re-read.

I looked in the settings dialogue as you suggested, and there it is,
but it still does not up in the Plugins menu; instead it loads as
a small palette.


> On Thu, Aug 27, 2015 at 1:16 PM, Richmond <richmondmathewson at>
> wrote:
>> 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 thing.
>>>>> More that for a cross platform IDE, written in it's supported
>>>>> language, to have an inadequate text editor is a very bad look
>>>> Again, we agree.
>>>>> and turns programmers away.
>>>> Only if they don't have a choice to use something better.
>>> Choice is useful only so long as it's a choice, rather than a requirement.
>>> It would hardly be an INTEGRATED development environment if it didn't
>>> have a script editor.
>>> Moreover, a script editor is a very good example of the sort of thing
>>> LiveCode can do very well.
>>> And best of all, AFAIK no one in the company is thinking about shipping
>>> LC without a script editor.
>>> Given all this, making the current script editor robust and performant
>>> would logically seem among the highest priorities, since a good SE makes
>>> the product a joy to use and a poor SE makes LC look bad.  In short, the
>>> choice is to either make more money or less, to the degree that the SE is
>>> solid and enjoyable.  After all, it's the one part of the IDE everyone uses
>>> most often.
>>> Along the way, reinstating an updated version of MetaCard's support for
>>> external editors would be useful AS AN OPTION, and probably something the
>>> community could deliver.
>>> To make the latter work well we'll want formatting and colorization
>>> plugins for as many third party editors as we can make them for - again,
>>> best done by the community since each of us has our own favorite so each of
>>> us may be motivated to write a LiveCode add-on for it.
>>> This page at Ken Ray's site discusses how external editors can be used in
>>> LC, with links to various LC-specific modules (though some of these may
>>> need to be updated):
>>> <>
>> Well: I've just downloaded the stsMLXEditor and placed it in the
>> /livecodecommunity-7.0.6 (x86_64)/Plugins/ folder and it does
>> not show up in /Development/Plugins in the 7.0.6 menu . . .
>> Richmond.
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list