Comments on: The Pinax Tutorial #2: Developing the basic application and plugging it in Pinax

By: Paolo Corti

Paolo Corti — Thu, 24 Dec 2009 17:03:55 +0000

you are right, thanks

By: Sanya

Sanya — Thu, 24 Dec 2009 16:51:19 +0000

Also in forms.py ‘tags’ should be removed from fields tuple since Book model does not have such field yet.

By: Sanya

Sanya — Wed, 23 Dec 2009 01:37:45 +0000

Hi. First of all I’d like to thank you for your efforts. This tutorial
is really very helpful.

And I also would like to point out some typos I have noticed
1) in file models.py:

return path.join(path.dirname(self.coverart.url), folder, path.basename(self.coverart.path)).replace(’\', ‘/’)
should be replaced with
return path.join(path.dirname(self.coverart.url), folder, path.basename(self.coverart.path)).replace(’\\’, ‘/’)

and the second occurrence of
thumb.allow_tags = True
should be replace with
fullpicture.allow_tags = True

2) in file bookstore/urls.py:
url(r’^(d+)/book/$’, ‘bookstore.views.book’, name=”describe_book”),
should be replaced with
url(r’^(\d+)/book/$’, ‘bookstore.views.book’, name=”describe_book”),

url(r’^user_books/(?Pw+)/$’, ‘bookstore.views.user_books’, name=”user_books”),
should be replaced with
url(r’^user_books/(?P\w+)/$’, ‘bookstore.views.user_books’, name=”user_books”),

url(r’^(d+)/update/$’, ‘bookstore.views.update_book’, name=”update_book”),
should be replaced with
url(r’^(\d+)/update/$’, ‘bookstore.views.update_book’, name=”update_book”),

url(r’^(d+)/delete/$’, ‘bookstore.views.delete_book’, name=”delete_book”),
should be replaced with
url(r’^(\d+)/delete/$’, ‘bookstore.views.delete_book’, name=”delete_book”),

By: Tiberiu Ichim

Tiberiu Ichim — Tue, 15 Dec 2009 17:41:20 +0000

Also, good job!

By: Tiberiu Ichim

Tiberiu Ichim — Tue, 15 Dec 2009 17:40:49 +0000

I’m trying to adapt this application to a Pinax site I’m doing, and I’ve noticed some problems with the code on github. First, some of the URLs are hardcoded into the templates (the /bookstore/ prefix), and some of the blocktrans tags display some of the problems that I’ve explained here: http://play.pixelblaster.ro/blog/archive/2009/11/30/a-dont-do-for-internationalizing-django-templates
(basically, don’t split phrases into separate entities, keep them together because the translation might need to switch the position of entities).

By: Grant

Grant — Sat, 05 Dec 2009 08:24:18 +0000

Great post! Looking I’m looking forward also to seeing the integration with localization. I’m trying to get my head around it right now, so I think it will be helpful.

By: Tim Lee

Tim Lee — Tue, 01 Dec 2009 23:26:08 +0000

Great Post! Thanks!

Looking forwards to the sequel

By: Paolo

Paolo — Mon, 30 Nov 2009 17:25:01 +0000

Fritz,
as far as I know the Pinax developers will start evaluating the possibility to run Pinax on GAE as soon as Django for non relational database will be released (and so Django will be able to run on GAE)
Refer to this:
http://groups.google.com/group/pinax-users/browse_thread/thread/b67be1fb3d1dfd68/13835507d705c56a?lnk=gst&q=google+app+engine#13835507d705c56a
and to this:
http://groups.google.com/group/django-developers/browse_thread/thread/fcf501d073ae33f
Of course the same concept is valid for other non relational DB like Amazon SimpleDb, MongoDb, CouchDb and Apache Cassandra.

By: Fritz

Fritz — Mon, 30 Nov 2009 14:24:51 +0000

Wow, that is quite extensive!
Thank you so much.

I was wondering if you might have an idea if this would run easily on google app engine, from doing some reading it seems it would have to. Do you have any ideas on this?