List of IDE stacks

[dunbarx]

A query on the use list, to understand and be able to set the color of the answer dialog, was answered by Panos.

Code: Select all

set the backColor of stack "answer dialog" to "red"
answer "whatever"

I posted there asking for a list of all IDE stacks, since though some names are simple and obvious, some are not, and it might be both useful and dangerous to have a complete list of all IDE stack names.

Craig

[bogs]

Curious as to what kind of list you are looking for. The most complete list I know of would be the one you see when you show the ide ui stacks in lists, then go through the project or application browser (the pb shows this more readily, but in the 8.x series as you know more slowly).

If your looking for something else, it would be helpful to know.

[FourthWorld]

dunbarx wrote:

> As a follow-up, is there anywhere a list of all IDE stacks? For
> example, the stack named "answer dialog", though perfectly logical,
> is not listed anywhere, and the names of some stacks, like the script
> editor, have changed over the several LC versions.

For stacks in memory, Panos' suggestion of changing Prefs to show IDE stacks is great.

For stack files (including script-only stacks) on disk, see the Toolset folder in your LC app bundle/folder.

For super-quick access to IDE scripts, consider devolution's MPath, which not only has a checkbox for showing LC scripts, but even more easily that can be toggled with the space bar while the MPath pane is open:
http://fourthworld.net/lc/devo3-mpath.png

Designed for quick access for scripting, everything in devolution's MPath pane has hot key shortcuts:
http://fourthworld.net/lc/devo-mpath-help.png

The devolution plugin for LC is freely available here:
http://fourthworld.com/products/devolution/


> It is a great way to get oneself in real trouble, but also useful if
> one wants red answer dialog boxes.

Yes, "if".

Tip: given the frequency of new LC builds, I've found it very helpful to automate IDE modification through scripts triggered on launch, as opposed to modifying the IDE stacks on disk.

Two benefits to this approach:

1. If you like your changes, they'll survive LC updates.

2. If you don't like your changes, reverting back requires nothing more than removing your plugin and re-launching.