Comments for ivixlog http://www.ivixor.net Fri, 04 Jul 2008 13:20:45 +0000 http://wordpress.org/?v=2.3.3 Comment on A month of Django by dan http://www.ivixor.net/2008/04/10/a-month-of-django/#comment-38 dan Thu, 10 Apr 2008 23:08:10 +0000 http://www.ivixor.net/2008/04/10/a-month-of-django/#comment-38 Matt - I didn't <strong>have</strong> to import the model into an external script. but I thought I might as well try and use the ORM niceness. This is a script that is (currently)  run manually to parse log files. Re the ORM needing work - probably, I have no idea since I've only played with it. Matt - I didn’t have to import the model into an external script. but I thought I might as well try and use the ORM niceness. This is a script that is (currently)  run manually to parse log files.

Re the ORM needing work - probably, I have no idea since I’ve only played with it.

]]> Comment on A month of Django by Matthew Russell http://www.ivixor.net/2008/04/10/a-month-of-django/#comment-37 Matthew Russell Thu, 10 Apr 2008 23:00:49 +0000 http://www.ivixor.net/2008/04/10/a-month-of-django/#comment-37 Nice article. I'm still not a fan of the templating, but for some uses it's cool.  I'm interested why, you had to import the db from an external script as you mention in 'Flexibility'? As for the python community uniteing behind django, as you say, I think this is already happening.  I do think that the ORM needs a bit more work  - since you have to adjust your db schema to accomodate for lazy loading concerns.  There is some work going on to intergrate sqlalchemy into django (as an optional ORM), which would be sweet. Nice article.
I’m still not a fan of the templating, but for some uses it’s cool.  I’m interested why, you had to import the db from an external script as you mention in ‘Flexibility’?
As for the python community uniteing behind django, as you say, I think this is already happening. 
I do think that the ORM needs a bit more work  - since you have to adjust your db schema to accomodate for lazy loading concerns.  There is some work going on to intergrate sqlalchemy into django (as an optional ORM), which would be sweet.

]]> Comment on PHP/Wordpress is daft by ivixlog » Blog Archive » AberQuotes http://www.ivixor.net/2008/02/26/phpwordpress-is-daft/#comment-36 ivixlog » Blog Archive » AberQuotes Thu, 10 Apr 2008 22:02:19 +0000 http://www.ivixor.net/2008/02/26/phpwordpress-is-daft/#comment-36 [...] Pretty silly and will be forgotten about within weeks (if not already), but it at least made me use the majority of the components of Django to some extent. Having said that about blogs, I should probably get around to turning this site into a Django site, if only because wordpress is rubbish. [...] […] Pretty silly and will be forgotten about within weeks (if not already), but it at least made me use the majority of the components of Django to some extent. Having said that about blogs, I should probably get around to turning this site into a Django site, if only because wordpress is rubbish. […]

]]> Comment on Django by Matthew Russell http://www.ivixor.net/2008/02/25/django/#comment-21 Matthew Russell Wed, 27 Feb 2008 02:13:36 +0000 http://www.ivixor.net/2008/02/25/django/#comment-21 Having developed with Zope2+3, Pylons, Cheetah, web.py, Turbogears and django, I'd say they all have their merits for different use cases.  Django is so popular right now because it sits in the middle or most use cases.   If you have a multi database setup, then django doesn't support it within the same app (that is you need two different projects with two settings.py). In those cases, Pylons or Zope is a better fit. I personally can't stand the underscore counting django database idiom, and much prefer SQLAlchemy's approach.   It's not that it uses underscores per say, more that it's not intuitive (to me at least) .  It does (however much I don't like it) however give users (as in us programmers) a consistant way to use the api, and this is what draws people to django. SQLAlchemy has too many ways to do the same thing, and you've pretty much got to understand big chunks of the api before you can use it properly. That being said,  that might not be a bad thing. Having developed with Zope2+3, Pylons, Cheetah, web.py, Turbogears and django, I’d say they all have their merits for different use cases.  Django is so popular right now because it sits in the middle or most use cases.  
If you have a multi database setup, then django doesn’t support it within the same app (that is you need two different projects with two settings.py).
In those cases, Pylons or Zope is a better fit.

I personally can’t stand the underscore counting django database idiom, and much prefer SQLAlchemy’s approach.  
It’s not that it uses underscores per say, more that it’s not intuitive (to me at least) . 
It does (however much I don’t like it) however give users (as in us programmers) a consistant way to use the api, and this is what draws people to django.
SQLAlchemy has too many ways to do the same thing, and you’ve pretty much got to understand big chunks of the api before you can use it properly.
That being said,  that might not be a bad thing.

]]> Comment on Django by Eric Elinow http://www.ivixor.net/2008/02/25/django/#comment-20 Eric Elinow Tue, 26 Feb 2008 19:35:14 +0000 http://www.ivixor.net/2008/02/25/django/#comment-20 I just started working with django a few months ago and from scratch built http://www.inkedmagonline.com for Inked Magazine. Things were a little messy at first for some of the conventions, but I've quickly learned better (more django-ish) manners of executing what i wanted to do. I think Cheetah is a nicer template engine, but I've found there is still enough flexibility in Django's template system to get what I need done, done. Eric I just started working with django a few months ago and from scratch built http://www.inkedmagonline.com for Inked Magazine. Things were a little messy at first for some of the conventions, but I’ve quickly learned better (more django-ish) manners of executing what i wanted to do.

I think Cheetah is a nicer template engine, but I’ve found there is still enough flexibility in Django’s template system to get what I need done, done.

Eric

]]> Comment on Django by dan http://www.ivixor.net/2008/02/25/django/#comment-19 dan Tue, 26 Feb 2008 19:12:01 +0000 http://www.ivixor.net/2008/02/25/django/#comment-19 RE templates, yeah it's pretty obvious that anything that spits out HTML can be used in place of the django template system. It works well enough, but doesn't look nice on first glance, that's all. RE comment responses, Sounds good, I've added something which says it does that. RE templates, yeah it’s pretty obvious that anything that spits out HTML can be used in place of the django template system. It works well enough, but doesn’t look nice on first glance, that’s all.

RE comment responses, Sounds good, I’ve added something which says it does that.

]]> Comment on Django by Jonathan http://www.ivixor.net/2008/02/25/django/#comment-18 Jonathan Tue, 26 Feb 2008 17:20:49 +0000 http://www.ivixor.net/2008/02/25/django/#comment-18 On Reddit: It's Pylons. The FAQ entry is out of date. http://reddit.com/info/69j0t/comments/c038rlx (spez is the technical cofounder and lead developer of Reddit). On Reddit:

It’s Pylons. The FAQ entry is out of date.

http://reddit.com/info/69j0t/comments/c038rlx

(spez is the technical cofounder and lead developer of Reddit).

]]> Comment on Django by Beetle B. http://www.ivixor.net/2008/02/25/django/#comment-17 Beetle B. Tue, 26 Feb 2008 17:00:40 +0000 http://www.ivixor.net/2008/02/25/django/#comment-17 Regarding the template language, it pays to read the FAQ: "I can’t stand your template language. Do I have to use it? We happen to think our template engine is the best thing since chunky bacon, but we recognize that choosing a template language runs close to religion. There’s nothing about Django that requires using the template language, so if you’re attached to ZPT, Cheetah, or whatever, feel free to use those." On an unrelated note, as you're using Wordpress, it would be *really* nice if you could get the plugin that allows people who leave comments to be notified of responses via email so that people like myself can carry on a conversation. Regarding the template language, it pays to read the FAQ:

“I can’t stand your template language. Do I have to use it?

We happen to think our template engine is the best thing since chunky bacon, but we recognize that choosing a template language runs close to religion. There’s nothing about Django that requires using the template language, so if you’re attached to ZPT, Cheetah, or whatever, feel free to use those.”

On an unrelated note, as you’re using Wordpress, it would be *really* nice if you could get the plugin that allows people who leave comments to be notified of responses via email so that people like myself can carry on a conversation.

]]> Comment on Django by ryan http://www.ivixor.net/2008/02/25/django/#comment-16 ryan Tue, 26 Feb 2008 16:49:39 +0000 http://www.ivixor.net/2008/02/25/django/#comment-16 For those curious/not in the know: http://reddit.com/help/faq (near the bottom) For those curious/not in the know:

http://reddit.com/help/faq

(near the bottom)

]]> Comment on Django by ryan http://www.ivixor.net/2008/02/25/django/#comment-15 ryan Tue, 26 Feb 2008 16:47:54 +0000 http://www.ivixor.net/2008/02/25/django/#comment-15 I believe reddit uses web.py. @Adam: Re: Templating... Perhaps you are the one who hasn't used many templating languages... The Django default templates are quite simply entirely useless. Name _any_ other templating system and you've got yourself a better alternative. I'm not even going to name any since literally all of them are better than the default Django stuff. Re: "proving you're an idiot"... Why not, instead of just trolling, give some examples of what you would use it for... I found it a pain to setup for anything but trivial models. Painful to customize and would never consider pointing a client to it to do updates to their site/content. It's marginally better than invoking an interpreter and manually creating and editing your records. I believe reddit uses web.py.

@Adam:

Re: Templating… Perhaps you are the one who hasn’t used many templating languages… The Django default templates are quite simply entirely useless. Name _any_ other templating system and you’ve got yourself a better alternative. I’m not even going to name any since literally all of them are better than the default Django stuff.

Re: “proving you’re an idiot”… Why not, instead of just trolling, give some examples of what you would use it for… I found it a pain to setup for anything but trivial models. Painful to customize and would never consider pointing a client to it to do updates to their site/content. It’s marginally better than invoking an interpreter and manually creating and editing your records.

]]>