Similarly I have a number of switches for things like (from memory):

- ide_ScriptEditor
- ide_SelectedScriptObject
- ide_ScriptEditorField

which switch depending on the "ide_Environment", and then

- rev_ScriptEditor
- glx_ScriptEditor
- ...

These allow tools that work on scripts to interoperate with the Script
Editor from either environment. Over the years, the way Galaxy / GLX2 has
defined these has changed. So then we have a versioning problem as well -
putting these all together it becomes seriously hard to distribute tools
that say work with the script currently shown in a script editor.

Dividing up the responsibility a bit, with the IDE manufacturers being
encourage to expose certain properties which as far as possible stay
constant accross versions, would help here.


2009/4/30 Mark Wieder <mwieder@...>

function glx2GetIDEStackName pRevIDEStackName
> local tStackName
>
> if "revErrorDisplay" is pRevIDEStackName then
> put "revGLX2 Execution Error" into tStackName
> end if
> if there is a stack pRevIDEStackName then
> -- we're running with the rev IDE
> -- just return the rev stack name
> put pRevIDEStackName into tStackName
> else if there is a stack "MetaCard Menu Bar" then
> -- we're running in the MetaCard IDE
> switch pRevIDEStackName
> case "revMenubar"
> put "MetaCard Menu Bar" into tStackName
> break
> case "revTools"
> put "Tools" into tStackName
> break
> case "revPreferences"
> put "Preferences" into tStackName
> break
> case "revSearch"
> put "Find" into tStackName
> break
> case "revErrorDisplay"
> put "Execution Error" into tStackName
> break
> default
> end switch
> else
> -- we're not in Kansas any more
> end if
> return tStackName
> end glx2GetIDEStackName


[Non-text portions of this message have been removed]