On Sun, Oct 3, 2010 at 5:58 PM, Marcob <marcob...@gmail.com> wrote:
> On 30 Set, 07:34, "subs...@gmail.com" <subs...@gmail.com> wrote:
>> Hello all,
>> I was browsing the tickets and saw a few of them nagging about some
>> restrictions to raw_id_fields.
>
> Since my first Django installation, a couple of years ago, I fixed and
> used this patch:
> http://code.djangoproject.com/ticket/7028
>
> I see that mtrs wrote an improved version.
> I also see that at each new Django release a fixed version comes up
> after few days (if not few hours).
> I think it is a huge improvement in user experience and I never fully
> understood why it always missed each django release since 1.0.

The reason that #7028 hasn't been included is the same reason that any
other ticket hasn't been included -- time. We have finite resources.
We can only fix a certain number of tickets if we want to keep a
timely release schedule.

As good as the ideas in #7028 are, they're not absolutely essential -
we've lived without the feature for a long time, and there's no data
loss at stake. As a result, it's been sacrificed in the interests of
other tickets.

#7028 is also subject to another major impediment -- it's dealing with
an area that requires front-end expertise. From my personal
perspective, I'm hesitant to get involved in anything touching the
front end out of lack of knowledge. I don't profess to being a UX
expert, and I'm certainly not an expert at CSS. I don't have the
facilities to do rigorous testing on any platform other than OSX. So -
even thought this ticket has been on my radar for a while, the barrier
for entry for me is higher than it is for other tickets.

Yours,
Russ Magee %-)

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

Reply via email to