Jay Foad
Jay Foad
I've just re-discovered that RIDE already supports drag-n-dropping a workspace onto the RIDE window, when the interpreter is running locally. See the code at the end of init.js. But that...
I've raised Mantis 15083 to define new protocol messages and support them in the interpreter.
Cool. It's a bit nasty that the menu option is present but does nothing when connected to a remote interpreter.
In 81d6ae270e316dcfdf666a157c1e8709c4b4cabd I fixed starting a Classic interpreter on non-Windows -- but probably broke it on Windows :-(
Sounds like #194, which was fixed.
I'd much prefer the interpreter to auto-detect whether there's a display it can use.
There's a vscode [issue](https://github.com/Microsoft/vscode/issues/1012) for this and an [extension](https://marketplace.visualstudio.com/items?itemName=adammaras.overtype) in the marketplace.
I suggest that the interpreter has no business telling RIDE whether to show the status window. That should be a RIDE preference.
Sorry but I really do not think this is a good idea. With RIDE we are trying to get away from the idea that APL can drive the IDE. Adding...
You previously said RIDE should have a toolbar _instead_ of a menu: #30.