July 3rd, 2007 | Published in Google App Engine
Admittedly we're biased, but we think Google Mashup Editor's web-based IDE makes AJAX web development simpler and more convenient than traditional methods. At the same time, we realize that Google Mashup Editor is a new product that may sometimes feel restrictive. For example, you can only upload resource files one at a time, and only into a single directory. Syntax highlighting and auto-indent aren't very well-suited to copying and pasting large chunks of code yet. We also know developers get attached to their text editors and development environments.
So if you feel like working on your project outside Google Mashup Editor, we understand. In fact, we make it easy for you by storing the source code for your applications (i.e. the .gml files and other resource files) using the project hosting feature of Google Code. Every mashup you've saved has a corresponding project on code.google.com, including a full Subversion repository. When you save or upload a file via the Google Mashup Editor, we automatically commit new revisions to the repository.
What does this mean for you? Two things:
- All prior saved versions of your application are stored and accessible via the Subversion repository. Did you delete a resource file accidentally? Or do you want to return to the version you published a week ago because you liked the formatting better? No problem: just connect to Subversion to see all previously saved versions.
- Once you've saved a project via the Google Mashup Editor, you can do all of your editing in your own IDE (using a Subversion plug-in). Or pull your files out of Subversion with a command-line tool and use whatever editor you want. You only need to return to our editor to republish the application.
So give it a shot. Go check out your project list at Google Code (click on the My Profile link). Subversion details are in the Source tab, but check out the others as well!
Don Schwarz, Software Engineer