Comments on: Conceptual Integrity, Django, Pylons and TurboGears http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/ Thinking about programming in new ways Tue, 15 Mar 2011 02:30:01 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Compound Thinking » “Site Components” in Django and TG2 http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-130043 Compound Thinking » “Site Components” in Django and TG2 Wed, 13 Feb 2008 05:10:08 +0000 http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-130043 [...] Bennet responded to my recent post about Pylons, Django, and conceptual [...] [...] Bennet responded to my recent post about Pylons, Django, and conceptual [...]

]]> By: Marcus Cavanaugh » Blog Archive » Conceptual Integrity: Pylons and Django http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-129482 Marcus Cavanaugh » Blog Archive » Conceptual Integrity: Pylons and Django Mon, 11 Feb 2008 18:52:09 +0000 http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-129482 [...] Mark Ramm provided a great example of an existing system — with completely pluggable components — which has proven to be [...] [...] Mark Ramm provided a great example of an existing system — with completely pluggable components — which has proven to be [...]

]]> By: James Bennett http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-129377 James Bennett Mon, 11 Feb 2008 14:39:04 +0000 http://compoundthinking.com/blog/index.php/2008/02/11/conceptual-integrity-django-pylons-and-turbogears/#comment-129377 I started to write a comment, and then it ran a bit long. So I turned it into a blog post instead: http://www.b-list.org/weblog/2008/feb/11/integrity/ The short version: I agree wholeheartedly on the need -- in pretty much all of the newer Python frameworks -- for better documentation and explanations of just how everything fits together to help a developer out :) I started to write a comment, and then it ran a bit long. So I turned it into a blog post instead: http://www.b-list.org/weblog/2008/feb/11/integrity/

The short version: I agree wholeheartedly on the need — in pretty much all of the newer Python frameworks — for better documentation and explanations of just how everything fits together to help a developer out :)

]]>