It's developed as an extension to webapp, so it's just one abstracted layer.
That abstracted layer is very minimal. Methods have the same or similar names to their webapp counterparts, but with useful extras that you'd probably end up coding yourself.
Simple routing; if you're familiar with Django or web2py, tipfy's routing is a huge step forward.
Finally, tipfy has an excellent support community. Rodrigo Moraes is especially helpful and engaging. Questions are answered very quickly, and courteously.
Although I mainly work with Django for larger work related projects (hosted elsewhere) I've tended to use webapp for things on App Engine. App Engine to me is best suited for small webservices that you then link together into a full app, and webapp suits that usecase pretty well. Small hacks as well I always use webapp just for simplicity and speed of development. Examples imified-demo.appspot.com, gitbug.appspot.com and github.com/garethr/appengine-image-host
Downside is tool support, you probably have to hack together little things to make your life easier that already exist in the Django world (eg. a test runner http://github.com/garethr/appengine-testrunner)
Anecdotal evidence from a previous project made me feel like Django was a little slow on App Engine for my liking.
Tipfy sounds a good idea, hopefully a case of App Engine maturing as a platform, although I have no personal experience with it at this stage.
All things considered it depends. A big project with multiple developers should probably opt for Django. It's standard ways of doing things will make life easier for everyone. For one off projects I personally prefer webapp or similar. But set aside some time for building your own tools as well as writing your application.
Django - the only part that's relevant is the templating and maybe the no rel..
Webapp - never tried it after
Tipfy - is what I'm using, seems to be more "pylons" like, has a basic apps/modules structure and lots of "helpers" which quite frankly should be in the google.appengine.api Easy to implement templates and routing is nice. Your pretty much left on your own on how to use tipfy and how to structure the application.
I'm still investigating, but I think webapp and tipfy will be a lighter framework than django. Right now, I am using just webapp and the cold start times are already too long. I want to use tipfy for sessions and keep everything else in webapp.
What are you trying to optimize for? Speed of development? Easy of programming? Obscure middleware?
Django 提供了默认的管理员 面板，否则需要 可以在 Webapp 中创建，尽管 Google 应用程序提供了一个管理界面，但是 这不等于完整的 成熟的可定制管理面板。
Webapp 本身遵循 Django 的模板。
I would still prefer Django for its structure and a high support available over internet for it and for the following reasons:
Webapp offcourse is light weight, but Django comes with a nice structure which saves a lots of time while working on a large application.
Google app engine does provide a good document for working with Webapp but Django has a large community of programmers and thus proves to be a better choice for implementing some complex applications.
Django provides a default admin panel, which otherwise would need to be created in Webapp, though Google app provides an admin interface but that is not equivalent of a full fledged customizable admin panel.
I use webapp2 which is a derivative of tipfy (in fact the functions and docs are in many cases identical) and takes ideas from other frameworks too. I recommend taking a look at some boilerplates if you are starting a new project and want to get a quick feel for the framework. Take a look at this boilerplate i've been working on with coto if you are interested in webapp2: http://github.com/coto/gae-boilerplate
发布评论
评论（6）
Tipfy
最后，tipfy 拥有出色的支持社区。 Rodrigo Moraes 特别有帮助且引人入胜。问题的回答非常很快，而且很有礼貌。
Tipfy
Finally, tipfy has an excellent support community. Rodrigo Moraes is especially helpful and engaging. Questions are answered very quickly, and courteously.
虽然我主要使用 Django 来处理较大的工作相关项目（托管在其他地方），但我倾向于使用 webapp 来处理 App Engine 上的事情。对我来说，App Engine 最适合小型 Web 服务，然后将它们链接到一个完整的应用程序中，而 Web 应用程序非常适合该用例。还有小技巧我总是使用 webapp 只是为了简单和开发速度。示例 imified-demo.appspot.com、gitbug.appspot.com 和 github.com/garethr/appengine-image-host
缺点是工具支持，您可能必须将 Django 中已经存在的小东西组合在一起，以使您的生活更轻松世界（例如，测试运行程序 http://github.com/garethr/appengine-testrunner ）
以前项目的轶事证据让我觉得 Django 在 App Engine 上的速度有点慢，不符合我的喜好。
Tipfy 听起来是个好主意，希望它是 App Engine 作为平台成熟的一个案例，尽管我现阶段还没有使用它的个人经验。
所有事情都取决于情况。拥有多个开发人员的大型项目可能应该选择 Django。这是标准的做事方式将使每个人的生活变得更轻松。对于一次性项目，我个人更喜欢 webapp 或类似的项目。但要留出一些时间来构建自己的工具以及编写应用程序。
Although I mainly work with Django for larger work related projects (hosted elsewhere) I've tended to use webapp for things on App Engine. App Engine to me is best suited for small webservices that you then link together into a full app, and webapp suits that usecase pretty well. Small hacks as well I always use webapp just for simplicity and speed of development. Examples imified-demo.appspot.com, gitbug.appspot.com and github.com/garethr/appengine-image-host
Downside is tool support, you probably have to hack together little things to make your life easier that already exist in the Django world (eg. a test runner http://github.com/garethr/appengine-testrunner)
Anecdotal evidence from a previous project made me feel like Django was a little slow on App Engine for my liking.
Tipfy sounds a good idea, hopefully a case of App Engine maturing as a platform, although I have no personal experience with it at this stage.
All things considered it depends. A big project with multiple developers should probably opt for Django. It's standard ways of doing things will make life easier for everyone. For one off projects I personally prefer webapp or similar. But set aside some time for building your own tools as well as writing your application.
恕我直言..
Django - 唯一相关的部分是模板，也许没有相关的..
Webapp - 在 Tipfy 之后从未尝试过
- 是我正在使用的，似乎更像“塔”，有一个基本的应用程序/模块结构和大量“助手”，坦率地说，应该位于 google.appengine.api 中
易于实现模板，路由也很好。关于如何使用 Tipfy 以及如何构建应用程序，您几乎需要自己完成。
Imho..
Django - the only part that's relevant is the templating and maybe the no rel..
Webapp - never tried it after
Tipfy - is what I'm using, seems to be more "pylons" like, has a basic apps/modules structure and lots of "helpers" which quite frankly should be in the google.appengine.api
Easy to implement templates and routing is nice. Your pretty much left on your own on how to use tipfy and how to structure the application.
我仍在调查中，但我认为 webapp 和 Tipfy 将是比 django 更轻的框架。现在，我只使用 webapp，冷启动时间已经太长了。我想使用 Tipfy 进行会话，并将其他所有内容保留在 Web 应用程序中。
您想优化什么？发展速度？编程容易吗？晦涩的中间件？
I'm still investigating, but I think webapp and tipfy will be a lighter framework than django. Right now, I am using just webapp and the cold start times are already too long. I want to use tipfy for sessions and keep everything else in webapp.
What are you trying to optimize for? Speed of development? Easy of programming? Obscure middleware?
我仍然更喜欢 Django，因为它的结构和通过互联网提供的高支持，原因如下：
Django 有一个很好的结构
这节省了大量时间
正在开发一个大型应用程序。
用于使用 Webapp 的文档，但 Django 有
一个庞大的程序员社区和
因此事实证明这是一个更好的选择
实施一些复杂的
应用程序。
面板，否则需要
可以在 Webapp 中创建，尽管 Google
应用程序提供了一个管理界面，但是
这不等于完整的
成熟的可定制管理面板。
I would still prefer Django for its structure and a high support available over internet for it and for the following reasons:
Django comes with a nice structure
which saves a lots of time while
working on a large application.
document for working with Webapp but Django has
a large community of programmers and
thus proves to be a better choice for
implementing some complex
applications.
panel, which otherwise would need to
be created in Webapp, though Google
app provides an admin interface but
that is not equivalent of a full
fledged customizable admin panel.
我使用 webapp2，它是tipfy 的衍生品（事实上，功能和文档在许多情况下是相同的），并且也从其他框架中汲取了想法。如果您正在开始一个新项目并希望快速了解该框架，我建议您查看一些样板。如果您对 webapp2 感兴趣，请查看我一直在与 coto 合作的样板： http:// github.com/coto/gae-boilerplate
I use webapp2 which is a derivative of tipfy (in fact the functions and docs are in many cases identical) and takes ideas from other frameworks too. I recommend taking a look at some boilerplates if you are starting a new project and want to get a quick feel for the framework. Take a look at this boilerplate i've been working on with coto if you are interested in webapp2: http://github.com/coto/gae-boilerplate