In order to promote GAEO, we need lots of documentation for references or guides to develop. Officially, we only provide an English-based documentations. However, there're many people around the world doesn't read English (very well). So we want to make our documentation global.
Now, there're some enthusiastic people help us to translate the GAEO Documentation to Français and 正體中文 versions. If you want to help us to translate the docs to more languages, please leave message here and I will tell you how to start.
Thanks you who help promoting GAEO :-)
2008/10/30
Subscribe to:
Post Comments (Atom)
7 Comments:
Hi, love your project!! Thankyou!!
Have found an error in your tutorial "Create a guestbook.." in the template to show messages (the last code block on the page, the {endifequals} should just be {endif}
@keith
Thanks for your correction :-)
Hey, me again. Just wondering if it would be possible for the scaffold to automatically add the import statement if i declare a db.ReferenceProperty.
thanks again!!
Hey, me again!! Just wondering if you think it would be feasable to implement this:
http://code.google.com/p/python-rest/w/list
as a plugin, to provide restful controller...
I'm thinking something like this:
http://www.akitaonrails.com/2008/1/25/easy-restful-rails-screencast
Back again. Sorry to keep coming back....take it as a compliment though!!
I have a couple of suggestions following on from my last post, which would bring the project more inline with the rails project.
While i appreciate it's a different project, i think you'll benefit hugely if you do follow some of their conventions so developers moving coming from RoR will pick things up even quicker.
First thing is i would recommend following their folder structure a little closer, so rename "application" to "app", and introduce the "vendor" folder where you can even bake in a version of the gae as a plugin.
Secondly i do think you should follow the mvc convention and call "templates" "views".
And finally you could clean up the scaffolding view code to use a shared _viewname.html "partial" file, which is then included using {% include "_profile.html" %} for example.
Anyways, as always, thanks for a great project, i hope i can get the point where i am able to contribute in the future.
One more and i promiss i'll shut up for a while.
Did you think about using this for routes?
http://routes.groovie.org/
@keith
Thanks for your suggestions!
Now you can manually handle the REST requests by detecting the request method.
We're trying to make the RESTful easier to use. Please wait for the 0.2 GA release :-)
Post a Comment