Tuesday, January 18, 2011

Make quick fixes quicker on Google Project Hosting

Have you ever noticed a bug or typo in your code but not been in a position to fix it? Perhaps you were browsing the code online from your Cr-48, or perhaps you just didn’t have Subversion or Mercurial handy. Today the Google Project Hosting team is announcing a new feature for you: the ability to edit your source code files directly in the browser, in our online editor powered by CodeMirror. Just look for the “edit file” link on files in the online source browser: As you edit, you can preview the diff of your changes so you know exactly what you are committing:

And if you don’t have commit privileges to the project? No problem. Instead of committing your changes, you can file your changes as a patch in the project’s issue tracker.

By lowering the barrier to entry for everyone — project members and users alike — we hope to make it easier for projects to grow and improve. Enjoy!

27 comments:

  1. Sometimes the "barrier to entry" serves a real purpose. Is it possible to use this and have automatic unit-tests execute after each commit? What about honouring source-control hooks?

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Wohhoooooo!!!! No longer have to use Google Gadget Editor now :)

    ReplyDelete
  4. Now I'm gonna stop using eclipse!

    ReplyDelete
  5. Wow, very cool!

    "Hey dawg, I put some code in your code...."

    ReplyDelete
  6. This is v. cool. I can't wait for someone to do a GWT based IDE...

    ReplyDelete
  7. Is there an online-version of eclipse?
    If so, please tell me where I can find it.
    I need it to teach an Android programming class,
    and half my time is wasted installing eclipse.


    gpscruise@ you know

    ReplyDelete
  8. Interesting, let me ping github about such feature. Does anyone actually still use google project hosting?

    ReplyDelete
  9. Nice! I'm still waiting for the ability to actually compile my code, like on Compilr.com.

    ReplyDelete
  10. Very cool.

    Please add a link to the wiki pages that provides the same features. I know committers can already edit the wiki from the browser but users cannot. Being able to edit in this way, and submit a patch, would be great.

    ReplyDelete
  11. Super cool, now if they would just allow for git repositories on Google Code all would be well :)

    ReplyDelete
  12. @carterson2 - yeah, check out eclipse orion. Build a web app in a web app!

    ReplyDelete
  13. Nice feature. I wish you would add more features to make google code hosting more competitive with places like github and bitbucket

    ReplyDelete
  14. Great feature, thanks :)

    ReplyDelete
  15. Very usefull, especially the quick patch option

    ReplyDelete
  16. I can see the barrier for entry for submitting patches dramatically lower. This is fantastic.

    ReplyDelete
  17. Oooooh, and just when I thought GC was starting to lag behind the competition. Pretty please, make a solid API for this and we could set up all kinds of cool interactions with our website. Imagine how easy it will be to contribute to a JavaDoc here and there!

    ReplyDelete
  18. This is exactly something I've been looking forward since a long time.

    ReplyDelete
  19. This is cute, but pointless if you can't run the code you are editing. You make a change to the code and the next person to checkout finds out you broke it because tests don't run, the code isn't evaluated at all. It is shiny but has no substance.

    ReplyDelete
  20. Does not work on iPad unfortunately!
    Output looks like crap and MobileSafari doesn't support contentEditable. Same problem as with Eclipse Orion.

    ReplyDelete
  21. Very interesting indeed. I tried it out but on the first file I edited, only the 92 first line (of 209) displayed...
    Using Firefox 3.6.13.

    ReplyDelete
  22. That is very click. Really like how if you don't have commit access it will auto submit a patch. So awesome. Great work.

    ReplyDelete
  23. But why would anyone want to do *BLIND* edits without even having the ability to see if the whole thing compiles and passes the tests? In my opinion without the ability to compile and run tests editing in the browser will be limited to fixing localization errors.

    ReplyDelete