eterevsky
commented
11 years ago Plugins are certainly a good idea, though it doesn't feel right to put the make or a compiler functionality into the editor plugin.
The chrome.fileSystem API is currently very limited. It does not allow the kind of access to the FS that would be needed to actually build a project. I mean, of course, you can build from the files that are already opened, but you can't open a file based on its path. There is an ongoing work on the Chrome file system, so hopefully if will be resolved in some not-so-distant future.
That said, the plugin system is definitely a useful feature for any full-fledged editor, but it'd say it's not a top priority right now.
What do you think?
It would be nice if there was a way for Text Drive to support plugins. I'm thinking of a few use cases where plugins would be nice:
1) A build system. Since Chrome OS doesn't have
make, a plugin to build a project would be wonderful.2) Transpilers. From CoffeeScript or ClojureScript to JavaScript, or Less to Css, this is something a lot of developers like to use.
Those are just a couple off the top of my head. I just want to open up discussion about how this could be done (or whether it should be done).