On Dec 10, 5:22 pm, Łukasz Rekucki wrote:
> > On Fri, Dec 10, 2010 at 9:37 AM, Rainy wrote:
>
> >> Is there a doc somewhere that details what the limitations are? How
> >> do you tell if some task is definitely too much for new generic views?
> >> I'm
>> Class based generic views still have the major drawbacks of the
>> previous version. They are a more powerful, more complicated version,
>> but they're still a red-herring.
>
> Can you elaborate on this ? Taking your original concerns:
Sure.
First of all, I'm not opposed to class based
On 10 December 2010 22:47, Ted Tieken wrote:
> Class based generic views still have the major drawbacks of the
> previous version. They are a more powerful, more complicated version,
> but they're still a red-herring.
Can you elaborate on this ? Taking your original
Class based generic views still have the major drawbacks of the
previous version. They are a more powerful, more complicated version,
but they're still a red-herring.
Ted
On Fri, Dec 10, 2010 at 9:37 AM, Rainy wrote:
> On Dec 10, 4:04 am, Łukasz Rekucki
On Dec 10, 4:04 am, Łukasz Rekucki wrote:
> You should try the new class-based generic
> views:http://docs.djangoproject.com/en/dev/topics/class-based-views/
>
> They're much more flexible.
Is there a doc somewhere that details what the limitations are? How
do you tell if
You should try the new class-based generic views:
http://docs.djangoproject.com/en/dev/topics/class-based-views/
They're much more flexible.
On 10 December 2010 02:44, Rainy wrote:
> On Nov 8, 6:42 pm, Ted wrote:
>> What are their pros and cons? How
On Nov 8, 6:42 pm, Ted wrote:
> What are their pros and cons? How often do you use them when you're
> coding?
>
> The more I code in django the less I find generic views to be useful
> shortcuts (direct to template being the exception).
>
> My biggest complaints are:
> *
On Wed, Nov 10, 2010 at 4:35 AM, derek wrote:
> I have not really understood when and why they are needed; I would be
> interested to see an alternative also because it might improve my
> understanding.
>
I've never used them before, and always avoided looking into them
Every Framework is so difficult to understand that it is better to
"code by own" the functionality provided by them.
We would have better control + peace of mind. Frameworks unnecessarily
bring hassle, irritation for a programmer.
--
You received this message because you are subscribed to the
I have not really understood when and why they are needed; I would be
interested to see an alternative also because it might improve my
understanding.
On Nov 9, 3:27 pm, ringemup wrote:
> I don't use them either for much the same reasons, and because I often
> end up using
I don't use them either for much the same reasons, and because I often
end up using custom render_to_response shortcuts that set common
context or handle custom template loading. Although the new class-
based views may make them more customizable.
I don't see much need for an alternative,
What are their pros and cons? How often do you use them when you're
coding?
The more I code in django the less I find generic views to be useful
shortcuts (direct to template being the exception).
My biggest complaints are:
* You don't end up saving many keystrokes unless you have 3 or more
12 matches
Mail list logo