I'm building an editor where the user interacts with a graphical representation of the data. This data is actually generated from a script which the user may expose and edit (the "code behind").
How can I best design the UX to explain to the user what will happen when they click the button that exposes (unhides/slides in/fades in/...) this adjacent text editor?
The common terms seem like poor choices to me since they describe the text ("code behind", "script editor", "development environment"), rather than explain what it does or the nature of its relationship to the graphical data they are currently viewing.
Am I way off here? How should I architect this interaction?
Here is a screen shot of the graphical editor next to the textual one. When you first arrive the text editor is hidden.
Thank you for your input! Cheers.