On Sat, Aug 15, 2009 at 4:48 PM, Graham
Dumpleton wrote:
> On Aug 15, 6:42 pm, Yuri Baburov wrote:
>> On Sat, Aug 15, 2009 at 12:24 PM, Graham
>> Dumpleton wrote:
>> > On Aug 15, 1:15 pm, Yuri Baburov wrote:
>> >> Hi all,
>>
>> >> I'm trying to figure out correct overall and settings path usage
On Aug 15, 8:53 pm, Russell Keith-Magee
wrote:
> On Sun, Aug 16, 2009 at 1:45 AM, hcarvalhoalves
> wrote:
>
> > On Aug 14, 11:48 pm, Russell Keith-Magee
> > wrote:
> >> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
> >> wrote:
>
> >> > On Aug 13, 9:30 am, Russell Keith-Magee
> >> > wrote:
>
> > Thanks, the accompanying discussion is very interesting and on point.
> > But as someone there points out, why stop at widgets?
>
> Because customizing widgets is a common request, unlike other attributes.
But customizing fields is quite common, no? I agree that it's rare
that you will want t
On Sun, Aug 16, 2009 at 1:45 AM, hcarvalhoalves wrote:
>
> On Aug 14, 11:48 pm, Russell Keith-Magee
> wrote:
>> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
>> wrote:
>>
>> > On Aug 13, 9:30 am, Russell Keith-Magee
>> > wrote:
>> >> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
>> >>
Michael Glassford wrote:
>
>
> hcarvalhoalves wrote:
>> On Aug 14, 11:48 pm, Russell Keith-Magee
>>
>> wrote:
>>> On Sat, Aug 15, 2009 at 8:09 AM,
>>> hcarvalhoalves
>>> wrote:
>>>
On Aug 13, 9:30 am, Russell Keith-Magee
wrote:
> On Thu, Aug 13, 2009 at 12:04 AM, Micha
hcarvalhoalves wrote:
> On Aug 14, 11:48 pm, Russell Keith-Magee
>
> wrote:
>> On Sat, Aug 15, 2009 at 8:09 AM,
>> hcarvalhoalves wrote:
>>
>>> On Aug 13, 9:30 am, Russell Keith-Magee
>>>
>>> wrote:
On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
wrote:
Secondly: I'm sen
On Sat, Aug 15, 2009 at 8:45 PM, mrts wrote:
>
> At HTML level, a form is a set of fields that gets submitted when
> a the form submit button is pressed.
>
> However, this is not the case with model forms and inline formsets
> (e.g. an admin page with inlines) -- inline formsets are
> disparate f
At HTML level, a form is a set of fields that gets submitted when
a the form submit button is pressed.
However, this is not the case with model forms and inline formsets
(e.g. an admin page with inlines) -- inline formsets are
disparate from the model form.
This creates at least two problems:
1)
I've implemented a simple hook called model_modified() that can be extended
in the user's ModelAdmin class. It's called after a New, Update, or Delete
action is taken. I've used it in my application to clear related session
information that I use to cache heavy query results.
Does this sound like a
Kevin Henry wrote:
>> There's also a ticket waiting for check-in implementing this common
>> usecase:http://code.djangoproject.com/ticket/9223
>
> Thanks, the accompanying discussion is very interesting and on point.
> But as someone there points out, why stop at widgets?
Because customizing wid
On Aug 14, 11:48 pm, Russell Keith-Magee
wrote:
> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
> wrote:
>
> > On Aug 13, 9:30 am, Russell Keith-Magee
> > wrote:
> >> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
> >> wrote:
>
> >> Secondly: I'm sensitive to the extent that 'on delete
On Sat, Aug 15, 2009 at 10:46 PM, Michael Glassford wrote:
>
> Russell Keith-Magee wrote:
>> On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford
>> wrote:
>>> Russell Keith-Magee wrote:
On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
wrote:
> On Aug 13, 9:30 am, Russell Keith-Magee
Russell Keith-Magee wrote:
> On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford
> wrote:
>> Russell Keith-Magee wrote:
>>> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
>>> wrote:
On Aug 13, 9:30 am, Russell Keith-Magee
wrote:
> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassfo
On Aug 15, 9:14 pm, Russell Keith-Magee
wrote:
> On Sat, Aug 15, 2009 at 3:52 PM, Haroldo
>
> Stenger wrote:
> > I've seen the admin evolve to very sophisticated user interaction.
> > Nonetheless, the param to HttpResponse() when a model object has been
> > saved, is hardcoded and most of the t
On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford wrote:
>
> Russell Keith-Magee wrote:
>> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
>> wrote:
>>> On Aug 13, 9:30 am, Russell Keith-Magee
>>> wrote:
On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
wrote:
Secondly:
On Sat, Aug 15, 2009 at 3:52 PM, Haroldo
Stenger wrote:
> I've seen the admin evolve to very sophisticated user interaction.
> Nonetheless, the param to HttpResponse() when a model object has been
> saved, is hardcoded and most of the times "../../.." or "../.." (see
> options.py in contrib.adm
On Aug 15, 6:42 pm, Yuri Baburov wrote:
> On Sat, Aug 15, 2009 at 12:24 PM, Graham
>
>
>
>
>
> Dumpleton wrote:
> > On Aug 15, 1:15 pm, Yuri Baburov wrote:
> >> Hi all,
>
> >> I'm trying to figure out correct overall and settings path usage
> >> strategy for my Django applications.
> >> What I
Hi Malcolm,
first of all, we'll soon start with a few experiments and since you
wanted to play around with some code, too, could you please tell us
your bitbucket username, so we can give you write access to the
repository?
On Aug 11, 4:07 am, Malcolm Tredinnick
wrote:
> Things like a ListField
...would get via the actual Python API? In this case, you couldn’t
switch the managers around either.
On Aug 15, 10:19 am, Zachary Voase
wrote:
> Correct me if I’m wrong, but won’t the inlines display the actual
> relationship that you
>
> On Aug 14, 5:43 pm, smcoll wrote:
>
>
>
> > Currently,
Correct me if I’m wrong, but won’t the inlines display the actual
relationship that you
On Aug 14, 5:43 pm, smcoll wrote:
> Currently, we can override the queryset used by ModelAdmins. This is
> helpful, since often times the default manager omits instances that
> nevertheless belong in the adm
> Please file a ticket for the documentation fix it would be greatly
> appreciated. :-)
Will do.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djan
In terms of backward compatibility, perhaps there could be a new
keyword argument to Field, something like with_model_defaults, that
the user would use to indicate a desire to get the attributes from the
Model. How would this work? Maybe something like this (this is just a
sketch): Field.__init__(
On Sat, Aug 15, 2009 at 12:24 PM, Graham
Dumpleton wrote:
> On Aug 15, 1:15 pm, Yuri Baburov wrote:
>> Hi all,
>>
>> I'm trying to figure out correct overall and settings path usage
>> strategy for my Django applications.
>> What I am experiencing now is that settings.py is imported 4 times on
>>
I've seen the admin evolve to very sophisticated user interaction.
Nonetheless, the param to HttpResponse() when a model object has been
saved, is hardcoded and most of the times "../../.." or "../.." (see
options.py in contrib.admin). Being able to change that string by some means
of instantiat
24 matches
Mail list logo
