Hi Bob! A markdown guide that goes in here
https://github.com/livecode/livecode-ide/tree/develop/Documentation/guides
would
be wonderful - then it would appear in the guides section of the dictionary
and also be built into the user guide PDF.
Eventually, IDE APIs will be built into an IDE 'diction
It’s is very possible to create a plugin that customizes the IDE/Script Editor
to your likely. I have a startup script that modifies many of the settings and
applies “bug" fixes to the IDE/Script Editor when my Dev environment opens.
“Bug” fixes are things that either are truly a bug in the IDE
That is rather an opaque answer.
Richmond.
On 7/18/17 12:48 pm, Monte Goulding via use-livecode wrote:
On 18 Jul 2017, at 7:19 pm, Richmond Mathewson via use-livecode
wrote:
"it’s currently not exposed in the IDE UI"
1. How can we work out what features are "latent" in LiveCode but are hidd
> On 18 Jul 2017, at 7:19 pm, Richmond Mathewson via use-livecode
> wrote:
>
> "it’s currently not exposed in the IDE UI"
>
> 1. How can we work out what features are "latent" in LiveCode but are hidden?
>
> 2. How can we 'hack' the IDE to expose any of those features we may find
> useful?
