Saving to the Cloud with Chrome Editor

I’ve invested a lot of time into building this new saving feature into Chrome Editor.

It was the most popular requested feature that Chrome Editors were missing.

Basically it’s the ability to save your files to Google Docs.

Chrome Editor will ask for access to your Google account, if authorized it will be able to save files to the Google Docs cloud.

I’m very excited about this feature and the potential it has for the Chrome OS users that are already using Chrome Editor currently.

It’s pretty neat that now you can sync with the cloud from Chrome Editor.

If you want to export from Google docs however, I believe it only supports .html files which I haven’t tried yet. So that might rule out php and js file formats, but you can still save them out as .txt and change them later.

So get ready for the Chrome Editor 2.0 update coming soon.

5 thoughts on “Saving to the Cloud with Chrome Editor

  1. Saving to Google Docs is a HUGE feature. Great work, Bryan. I love it. Have you, by any chance, been able to try collaborating with this new feature? One of the main features of Google Docs that I use is working on documents with other people. With Chrome Editor be able to open and save files that other users have shared with me?

    • Currently you can only save files to Google Docs, however you can save the file out from Google Docs and import it again into Chrome Editor. I will look into editing files from Google Docs as a feature.

  2. How hard would it be to include an option to save to DropBox as an actual HTML/js/CSS file like SourceKit does?
    Although it’s awesome that I can save my stuff on your app to google docs, it’s still kind of cumbersome to have to load google, copy… then go back to the tab your app is on and paste and continue. I know you can save directly to the browser, but I work on 3 different computers (work(mac)/home(windows)/laptop(chromeOS)) and would like to be able to just get up and continue to learn coding.

Leave a Reply

Your email address will not be published. Required fields are marked *