• An application that provides 'a simple API for writing and reading small chunks of data from anywhere' : http://tinydb.org/
• An app that adds photos to the developer's facebook account
• An Open Source Django utility project: http://code.google.com/p/django-ae-utils/
• An application that searches for clinical trials based on keywords
• An application that uses GWT, Maps and Gears to track and map appointments and uses App Engine to keep the client side data synced
• An app where users can list items for sale and get emails from interested buyers: http://sellstuff.appspot.com/

• The ability to use most manage.py commands
• A BaseModel class that appears the same as the standard Django Model class.
• The ability to serialize and deserialize model instances to JSON, YAML and XML.
• Access to Django's test framework with a test datastore and support for fixtures.

• More fixes paging so that 250 items can be displayed per page
• Fixes to the compiler so that it no longer optimizes tags. This fixes many bugs that caused problems in the display of compiled mashups.
• More fixes to feed fetching. All Atom and RSS compliant feeds should now work correctly.
• Documentation fixes

• More fixes paging so that 250 items can be displayed per page
• Fixes to the compiler so that it no longer optimizes tags. This fixes many bugs that caused problems in the display of compiled mashups.
• More fixes to feed fetching. All Atom and RSS compliant feeds should now work correctly.
• Documentation fixes

• Create a Google Gadget - Its the easiest way to get some great traffic to your application. Try creating a Google Gadget as a different view into your application or creating a stand alone app that would be interesting as a gadget. Check out recent tutorial on creating Google Gadgets using GME.
• Read a tutorial - We have created a bunch of tutorials to help you get started building some more sophisticated apps. You can also check out our Demo Gallery to see working demo applications. Remember you can also click the "View Source" link in any GME app to see how it was built
• Watch a screencast - We've just started building a set of videos that take you through building simple mashups. Check out our screencast gallery to see what we've been up to.

• Create a Google Gadget - Its the easiest way to get some great traffic to your application. Try creating a Google Gadget as a different view into your application or creating a stand alone app that would be interesting as a gadget. Check out recent tutorial on creating Google Gadgets using GME.
• Read a tutorial - We have created a bunch of tutorials to help you get started building some more sophisticated apps. You can also check out our Demo Gallery to see working demo applications. Remember you can also click the "View Source" link in any GME app to see how it was built
• Watch a screencast - We've just started building a set of videos that take you through building simple mashups. Check out our screencast gallery to see what we've been up to.

<gm:page title="Demo - Defer authentication" authenticate="false" onload="init()">

<script>
  function init() {
    if (google.mashups.isUserAuthenticated()) {
      document.getElementById('signInLink').style.display = 'none';
    } else {
      document.getElementById('signInLink').href = google.mashups.properties['loginURL'];
    }
  }
</script>

<div class="gm-app-header">
  <h2>Displaying the login screen when a link is clicked</h2>
</div>

<gm:list data="${app}/test" template="simple"/>

<a id="signInLink" href="#" onclick="">Sign in to add entries</a>

</gm:page>

<gm:page title="Demo - Defer authentication" authenticate="false" onload="init()">

<script>
  function init() {
    if (google.mashups.isUserAuthenticated()) {
      document.getElementById('signInLink').style.display = 'none';
    } else {
      document.getElementById('signInLink').href = google.mashups.properties['loginURL'];
    }
  }
</script>

<div class="gm-app-header">
  <h2>Displaying the login screen when a link is clicked</h2>
</div>

<gm:list data="${app}/test" template="simple"/>

<a id="signInLink" href="#" onclick="">Sign in to add entries</a>

</gm:page>

• New header in the Editor that makes a easier to understand what files are being edited and provides quick links to the published application and the open source project that contains your source code.
• All feeds refresh every 10 minutes instead of 1-6 hours.
• Ability to turn off code coloring if you have large files that cause performance issues with code coloring turned on.
  
• New time attribute for the gm:date tag. Allows you to display only the time of a XML timestamp.
• Controls are all inline elements so you don't need any extra CSS to make them look right.
• Updated samples and documentation
• Fixes to geocoder, iframes within tabs, and viewing the source in IE among other bug fixes.

• New header in the Editor that makes a easier to understand what files are being edited and provides quick links to the published application and the open source project that contains your source code.
• All feeds refresh every 10 minutes instead of 1-6 hours.
• Ability to turn off code coloring if you have large files that cause performance issues with code coloring turned on.
  
• New time attribute for the gm:date tag. Allows you to display only the time of a XML timestamp.
• Controls are all inline elements so you don't need any extra CSS to make them look right.
• Updated samples and documentation
• Fixes to geocoder, iframes within tabs, and viewing the source in IE among other bug fixes.

The Atom Publishing Protocol (aka AtomPub) is now a Proposed Standard Protocol from the IETF as RFC 5023. The Atom Working Group was formed in June of 2004 with the goals of producing a new syndication format and a new publishing protocol. The publication of RFC 4287 (The Atom Syndication Format) and RFC 5023 (The Atom Publishing Protocol) represent three years of effort by the members of the working group.

This is great news for us because the Google Data APIs are built on the Atom Publishing Protocol. The current Google Data APIs are based on early versions of the AtomPub specification and now that AtomPub is a Proposed Standard work will begin on getting all of our Google Data APIs compliant with RFC 5023. A big part of that work involves a lot of careful thinking about how to support the final version of the protocol and also support our existing clients. I'll talk more about our versioning strategy in a later blog post.

So what does "Proposed Standard" mean? That might not sound very stable - "Proposed" - but that term does have special meaning in the IETF. The best way to explain it is that there are plenty of other protocols that you use every day that are "Proposed Standards", for example: WebDAV, TLS, LDAP, SMTP, SIP, and IMAP. Of course, if you want to know more about the IETF's standards process, they have it documented, in RFC 2026

• Java


• .NET


• PHP


• Python