On Tue, Mar 31, 2009 at 7:28 PM, Julien Phalip <jpha...@gmail.com> wrote:
>
> On Mar 31, 6:53 pm, zain <z...@inzain.net> wrote:
>> I'm applying for the GSoC with some thoughts to generally improve the
>> admin interface. So far, I have the following ideas:
>>
>> 1) An autocomplete widget
>> 2) Drag & Drop support for ordered relations
>> 3) Foreign Key traversal to see and modify models referenced to by
>> ForeignKeys inline
>> 4) Refactor the admin's Javascript to use JQuery for maintainability
>>
>> Do you have any other ideas for features and fixes to improve the
>> admin interface?
>
> I think that an API for declaring read-only fields and the ability to
> edit multiple objects on the same page are some wanted features which
> have been discussed on this list. I'm not sure if you would consider
> those suggestions pure interface design though.
>
> All the things enumerated so far seem more like a list of small
> features. So I assume that for a GSoC proposal you'd need to suggest a
> coherent approach rather than a list of minor fixes/feature
> extensions.

Not necessarily. Using the Django ticket tracker as a source for ideas
could be a way to create a very compelling application. A random
grab-bag of tickets probably won't be looked upon favourably, but If
there is a common theme to the tickets (e.g., in this case, UI
enhancements for the admin), then you essentially have a collection of
ideas that have already been approved by the Django core, and are just
waiting for someone to do the work. The granularity provided by using
multiple tickets makes it easier to make accurate time estimates,
easier to evaluate progress, and easier to constrain scope if the time
required exceeds expectations.

> As for including jQuery (or any other javascript library),
> I doubt this will be received favourably. Going for plain javascript -
> even if it's a bit more challenging to do - is a good way to find
> overall consensus.

Correct. Django has very deliberately made a decision to avoid
blessing any single Javascript toolkit. It is unlikely that this will
change simply because a GSoC applicant has proposed it. Proposals that
hinge on the use of JQuery (or any other toolkit) will not be looked
upon favourably.

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-developers@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