To get the stuff done I thought, that the source code (of a different language) is offered without Smalltalk coloring - but a simply text editor (more would be better ...).
To manage this code in a Smalltalk like way, I would assume the following workflow. Normally I work with Smalltalk source code and nothing has to be done - a "New method template" does its work.
- Code: Select all
<type: json cp: utf8 extension: js>
Now the user enters its code and when he wants to save the stuff, the IDE parses "nameOfFile" and the pragma stuff and the rest of the text editor is seen as source code of the wanted language. Now the IDE creates a Smalltalk method, which has the name mentioned above, the pragma - and the rest of the source code is embedded within a Smalltalk string and the method returns this string.
In case of a bitmap or icon I could think about a small icon editor coming up within the area of the text widget.
All these "different" language resources should be entered on a class side of a class.