Re: GENERIC VIEW CONCERNS AND EXPLANATION REQUIREMENTS

Short answer: yes.

The generic views are there for a reason, to provide a simple implementation of most generic operations like detail views, listings ... 

A complete different things is the "if I have to", you don't!

One thing is DRY other is use the tools and possibilities that the framework gives allows you to, depending on the case you might find some limitations on the usage of generic views. It's all about "generic" you need your views to be!

N.

On Mon, Feb 28, 2011 at 4:55 PM, Dipo Elegbede <delegbede@dudupay.com> wrote:

Hi all,

I am currently trying to read up generic views.

I can do most of my django stuff at my level without the generic view but it appears almost in all texts i read and also seem to be a key part of django's underlying principles of DRY and keeping things from redundancy.

My question is, if i have to use generic views syntaxes in my urls.py, does it mean I don't have to write a function for the url in my views.py file?

I am currently reading Practical Django Projects by James Bennette.

Kindly help with some explanations.

Thank You.

--
Elegbede Muhammed Oladipupo
OCA
+2348077682428
+2347042171716
www.dudupay.com
Mobile Banking Solutions | Transaction Processing | Enterprise Application Development

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
Norberto Leite

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.