Re: #12804 - decorating admin views marked as invalid

Hi, thx for your quick response, I'll update the ticket and reopen it (I hope that's okay in this case…) Cheers, Florian On Feb 8, 3:05 am, Luke Plant wrote: > Ignore my last post - my 'fix' only fixes one corner case, and not a > very useful one either.  I've got it

Re: #12804 - decorating admin views marked as invalid

On Monday 08 February 2010 08:21:27 Florian Apolloner wrote: > thx for your quick response, I'll update the ticket and reopen it > (I hope that's okay in this case…) That's fine, apologies for the premature closing. Here is my analysis, sorry in advance for the length. Unfortunately, we have

Re: Django Design Czar

Good to see you guys are progressing. I've red lots of interesting and valid input, but from what I can see there is tearing decisions ahead and whoever will take the design lead will be invariably limited by the current state of the admin. If you want to achieve something like we are doing with

Re: Django Design Czar

On 6 fev, 20:03, Idan Gazit wrote: > Hey folks, > > Splitting off > fromhttp://groups.google.com/group/django-developers/browse_thread/thread..., > which has an exhaustive discussion about  how django needs to treat > design work. > > In the spirit of taking action, I put

Re: Django Design Czar

On Mon, Feb 8, 2010 at 2:34 PM, j...@jeffcroft.com wrote: > So, unless anyone disagrees with the idea that Wilson should have > first dibs on this position, it sounds like we have ourselves a Design > Czar. Or whatever you want to call it. Woot! I, for one, welcome our new

Re: Django Design Czar

Wait, does this mean we can't change designs just to wash the Wilson out of them? :) On Feb 8, 7:05 am, Russell Keith-Magee wrote: > On Mon, Feb 8, 2010 at 2:34 PM, j...@jeffcroft.com wrote: > > So, unless anyone disagrees with the idea that Wilson

Re: Django Design Czar

Hey Wilson, I'm sure I'm not the only one who is delighted that you have some cycles to spare for Django. :) As this thread was about practical matters, I'd say the next step is deciding on a few things that we want to get done. Up at the top, I suggested setting out a few modest goals for 1.3 as

Re: Django Design Czar

I do totally agree with Idan that often times designers needs don't have anything to do with design itself, and that designers may want to contribute by telling us how the parts of the framework they touch could be changed to make their lives easier. One way I think design proposals/tickets need

Re: Django Design Czar

On Mon, Feb 8, 2010 at 3:42 PM, j...@jeffcroft.com wrote: ... > One way I think design proposals/tickets need to be treated > differently than other stuff is that there shouldn't be this, "sure, > great idea, go build it and get back to us" attitude involved. I agree with

Re: Django Design Czar

In my experience, Trac (or any bug tracker) isn't a good place to deal with design issues, at least until they've reached the point where they're concrete and actionable specs. On the other end, I don't think we're quite far enough along yet to be able to deal with "design tickets" yet, but that's

Re: Django Design Czar

On Mon, Feb 8, 2010 at 4:00 PM, Wilson wrote: > I've started a stub of a wiki page that anyone who's interested can > start to share and collect ideas that require design work or input. > > http://code.djangoproject.com/wiki/DjangoDesign > > As the input outgrows the wiki page,

Re: Django Design Czar

Unfortunately, unless the person filing the > request/ticket makes it clear that their request isn't something they > can personally fulfill, it's hard to tell the difference between a > person being lazy (i.e. wishing for a pony) and a person asking for > assistance (i.e. a designer asking for a

Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

Luke, thank you for your explanations. If I answer once more, then I do it in the hope that our discussion may help to improve Django. On 8.02.2010 0:38, Luke Plant wrote: > It is easy to fix - a few lines in > ReverseSingleRelatedObjectDescriptor - because the behaviour there is > not

Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

On Mon, Feb 8, 2010 at 5:31 PM, Luc Saffre wrote: > [snip] Okay, it's obvious that Luke's and Luc's understandings of that problem > are quite different. We both explained our points of views. The next > step would be to hear other people's opinions. > I agree with Luke.

Re: #12804 - decorating admin views marked as invalid

On Mon, Feb 8, 2010 at 8:44 AM, Luke Plant wrote: > What do people think? > Ugh. Assuming no one can come up with a brilliant fix so that the auto_adapt stuff can work when combined with arbitrary other decorators (I can't), I favor switching to a system that requires

contrib.Auth

Hey Guys, So 1.2 is almost out the door so I wanted to raise an issue that I would love to start working to fix for 1.3. As we all have used the contrib.Auth application we know there are some short comings in the application. Here is a couple of issue that I have noticed since using it. - If

Re: contrib.Auth

On Mon, Feb 8, 2010 at 6:39 PM, Vitaly Babiy wrote: > Hey Guys, > So 1.2 is almost out the door so I wanted to raise an issue that I would > love to start working to fix for 1.3. > Not to discourage you, but be aware the focus of most attention until 1.2 actually goes out is

Re: contrib.Auth

Thanks, for the pointer. I think even if this gets people think about the problem its a good start, I will raise this question again after 1.2 release. Vitaly Babiy On Mon, Feb 8, 2010 at 6:46 PM, Karen Tracey wrote: > On Mon, Feb 8, 2010 at 6:39 PM, Vitaly Babiy

Re: Django Design Czar

On Mon, Feb 8, 2010 at 3:42 PM, j...@jeffcroft.com wrote: > A designer ought to be able to say, "It'd be really useful to > me if the 'if' tag supported basic operators, and I'd be happy to help > someone understand the needs of designers with regard to it, but I'm > not

Re: contrib.Auth

To add another point, this doesn't mean that the day 1.2 hits release that everyone is gung-ho on 1.3. If past releases are any indication, there is usually a refactory period of a few weeks when everyone is basking in post-release bliss. -justin On Mon, Feb 8, 2010 at 6:46 PM, Karen Tracey

Re: contrib.Auth

On Tue, Feb 9, 2010 at 8:15 AM, Justin Lilly wrote: > To add another point, this doesn't mean that the day 1.2 hits release that > everyone is gung-ho on 1.3. If past releases are any indication, there is > usually a refactory period of a few weeks when everyone is basking

Re: Django Design Czar

I would be willing to give this wiki-gardening a try. Not as a Dev, but merely an enthusiast sent from the research lab at http://networksecuritynews.net On Feb 8, 2010 5:11 PM, "Jeremy Dunck" wrote: On Mon, Feb 8, 2010 at 4:00 PM, Wilson wrote: > I've

Re: #12804 - decorating admin views marked as invalid

On Tue, Feb 9, 2010 at 7:19 AM, Karen Tracey wrote: > On Mon, Feb 8, 2010 at 8:44 AM, Luke Plant wrote: >> >> What do people think? > > Ugh. Assuming no one can come up with a brilliant fix so that the auto_adapt > stuff can work when combined with

Re: Django Design Czar

This is all very timely. Myself and my friend Harry Brignull (who runs the UX blog http://www.90percentofeverything.com ) have been talking for a while about the idea of doing some formal usability testing on the Django admin and this might prove to be the catalyst. I'll put together our plan and