ou get feedback like this
at an earlier point. While I try to keep an eye out for where things
are going with django, this change and it's impact on me just was not
at all clear.
Anyway, thanks for listening. I do very much appreciate all you have
done to make Django a great product.
Margi
not use ModelForms, and use a non-
model Form and do all the save logic myself. But setting exclude
prior to the save really worked beautifully.
I would think the changelist could benefit from this paradigm as well.
Margie
On Jul 13, 5:41 am, SmileyChris wrote:
> On Jul 13, 9:10 pm, Margie w
folks think the paradigm is a good one, I would
be happy to work on the interface.
Thanks for your comments.
Margie
On Jul 13, 6:46 am, Russell Keith-Magee
wrote:
> On Tue, Jul 13, 2010 at 5:10 PM, Margie wrote:
> > Hi developers,
>
> > I would suggest considering making thi
ior to
instance save.
However, as Russell has noted, I am sadly very late in making this
observation.
Margie
On Jul 13, 8:28 am, Alaa Abd El Fattah wrote:
> On Tue, 13 Jul 2010 02:10:03 -0700 (PDT)
>
> Margie wrote:
> > It's hard for me to believe that no other developers hav
appropriate - just thought I was getting a
little deep in the source to be posting there. Also, if this seems
like an interesting widget to the development community, I'm happy to
contribute it to the source if I can generalize it enough.
Margie
--~--~-~--~~
point to the newly copied
ModelChoiceField in my area and see what that does.
Margie
On May 21, 6:01 am, Alex Gaynor wrote:
> On Thu, May 21, 2009 at 12:35 AM, Margie wrote:
>
> > In the process of doing some debugging into the django source, I've
> > come across something in t
rocess via the call to
BaseForm::__init__()
self.fields = deepcopy(self.base_fields)
Margie
On May 21, 7:24 am, Alex Gaynor wrote:
> On Thu, May 21, 2009 at 9:09 AM, Margie wrote:
>
> > I don't think we are calling Widget.__deepcopy__() at this point. I
> > thin
-developer to prune down
the choices for a foreign key via an ajax callback to an app-developer
specified method.
2) give the app-developer more control of the showAddAnotherPopup.
Is this the right place for this discussion? If not, what is?
Margie
On May 25, 3:11 am, Zain Memon wrote:
> Si
a lot of studying and stepping
through the source code.
Anyway, hope the problem I am trying to solve and the solution I have
posted are understandable. Would love to hear from those in the
development community as to whether you think this is a wortwhile
addition.
Margie
On May 25, 7:29 pm, Justi
same thing in the changelist. This is one of the
things I struggled with, and why I had to extract the id field out of
the form and send it back with my ajax request. Am interested in if
you see a workaround for that - I would definitely prefer to not be
using ajax calls.
Margie
On May 26, 5:
continent. It is not easy to send the country value as part of
an ajax request because its field in the form has no id at all.
Margie
On May 26, 5:10 pm, Alex Gaynor wrote:
> On Tue, May 26, 2009 at 7:05 PM, Ulrich Petri wrote:
> > It is quite possible to refer to the "parent"
really
helped a lot.
Margie
On May 27, 12:30 am, Yuri Baburov wrote:
> My usual workaround to this is to store object, request and action
> ("add", "change", "changelist") in thread local storage when add_view,
> changelist_view or change_view are called, and
and
having done that, I have come around in my thinking. I actually think
that autocomplete is probably the most general solution and a very
good addition. Sorry if my comments caused you to divert from this in
any way!
Margie
On Jun 8, 11:35 pm, Zain Memon wrote:
> This week, I checked i
I think there should be an indicator on the
selector that there is an error in the entry.
Nice work, I like it!
Margie
On Jul 6, 2:20 am, Zain Memon wrote:
> Hi everyone,
> In the last couple of weeks, I've implemented a bunch of inline features.
>
> Pictures speak louder t
14 matches
Mail list logo