I'm not as strong with GAE/Python as I am with GAE/Java, but my feeling is that ...

Kilimanjaro · on Nov 23, 2010

Webapp, webapp templates (just like django) and datastore.

I like it barenaked and closer to the metal.

cmelbye · on Nov 24, 2010

Could you share some information about how your app code is structured? The main reason I'm using Django is because I like that it gives me a directory structure. The only examples I've seen of webapp are a ton of handlers in one main.py file, which doesn't seem maintainable.

Kilimanjaro · on Nov 24, 2010

Usually I put one handler per .py, to the point, what that particular module should do and nothing else. I leave the routing stuff to the app.yaml file.

For a dir structure, I have admin, css, js, prog and view. Not hard to know what goes in every folder. Right now I have like fifty progs and fifty views, each for every specific task.

For every program there is usually one line to get the data from models and one line to render it using a template. Nothing else.

I really don't get what a framework would do to help me, I already have everything I need at my fingertips.

Kilimanjaro · on Nov 24, 2010

Here is a sample index.py that renders index.html. I enhanced webapp with some utilities to make my life easier, I hate typing in excess.

    import app

    class main(app.request):
      app.session.start()
      data=app.models.getContacts()
      app.render('index',data)

    app.run('/',main)

And here the html in the template:

    <html>
    <body>
      <h1>Contacts List</h1>
      {% for item in data %}
        <li>{{item.name}} - {{item.phone}}</li>
      {% endfor %}
    </body>
    </html>

Some purists will burn me at the stake, but it works wonders for me.

fletchowns · on Nov 23, 2010

How about a framework like objectify? Is that close enough to the low level datastore to get good performance?

mmastrac · on Nov 23, 2010

I've heard really good things about it. It's written for GAE and GAE only, so there aren't any abstractions that insulate you from how the datastore works. It's still worth your time to write some code against the raw datastore APIs. It takes some time for entity groups, keys and parents to sink in and working with the raw API helps you see what's going on.

RoyceFullerton · on Nov 24, 2010

I started with the raw datastore API and was able to do what I wanted after quite a bit of research and trial and error. I was then turned on to Objectify and couldn't be happier. I know what is going on underneath and the limitations but I have a much easier way to deal with them. Objectify is highly recommended, but my app doesn't have massive scale so I am not sure if it adversely affects performance much.

adn37 · on Nov 23, 2010

> We've also developed our own Django-like templating system for Java

Any chance you could list viable alternatives, please? (I'm considering GAE/Java). Thanks for this interesting thread.

mmastrac · on Nov 23, 2010

I did a study of the bigger templating systems available on Java earlier this year and the landscape wasn't that great: JSP, Freemarker, Velocity and a number of smaller projects. We decided that it was worth some time developing a system inspired by Django's lightweight syntax. If you send me a note (matthew@mastracci.com), I can let you know when we get our project up on github. It's rendering every page on gri.pe right now and has been stable for a few months now.

arthur_kalm · on Nov 24, 2010

Have you looked into Google Sitebricks for templating?