Skip to content
James Foster edited this page Jun 19, 2019 · 3 revisions

Presentation

The traditional Smalltalk IDE has a text editor where the item being edited is either a class definition or a method definition. In the context of VSCode should we preserve that model (and navigate to each method as if it is a file in the class directory)? Alternatively, should we go to a file-based model where we have one file per class and use the "Outline" feature to navigate between methods?

I think our initial approach will be to use Topaz file format in VSCode. (Tonel is not yet supported on GemStone.)

Storage

Should we actually store files in the file system? This would make it easy to use other tools (search, Git, etc.). Initially we will use a FileSystemProvider to give a way to access a "file" stored in GemStone.

Workspace

The traditional Smalltalk IDE has a workspace that can be saved as a file. We support executing code in any text file, so don't have to build a separate view.

Clone this wiki locally