On Tue, Mar 31, 2009 at 9:43 AM, Russell Keith-Magee
wrote:
> I'm in full agreement that "Improving the admin UI" is certainly a
> good pre-proposal, and I'm sure there's plenty of tickets that could
> fill a SoC. My concern is that "move to using jQuery" isn't a good
> line item in a proposal wi
On Tue, Mar 31, 2009 at 9:44 PM, mrts wrote:
>
> Sorry if I sounded intrusive, what I meant was that prototyping with
> jQuery (or whatever other JS framework) may at the very least provide
> a quick way prove that a particular idea works (instead of a time-
> consuming plain-JS implementation).
On Tue, Mar 31, 2009 at 9:39 PM, Jacob Kaplan-Moss
wrote:
>
> On Tue, Mar 31, 2009 at 8:30 AM, Russell Keith-Magee
> wrote:
>> It would be _exceedingly_ unwise to advise any student to base a GSoC
>> proposal on the use of JQuery (or any other framework, for that
>> matter).
>
> I think that soo
Sorry if I sounded intrusive, what I meant was that prototyping with
jQuery (or whatever other JS framework) may at the very least provide
a quick way prove that a particular idea works (instead of a time-
consuming plain-JS implementation). But it is of course for the BDFLs
to decide if that is a
On Tue, Mar 31, 2009 at 8:30 AM, Russell Keith-Magee
wrote:
> It would be _exceedingly_ unwise to advise any student to base a GSoC
> proposal on the use of JQuery (or any other framework, for that
> matter).
D'oh.
The reason that Zain is including use of jQuery in this proposal is
because I, e
On Tue, Mar 31, 2009 at 9:02 PM, mrts wrote:
>
> On Mar 31, 2:41 pm, Russell Keith-Magee
> wrote:
>> 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.
On Mar 31, 2:41 pm, Russell Keith-Magee
wrote:
> 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 oth
On Tue, Mar 31, 2009 at 7:28 PM, Julien Phalip wrote:
>
> On Mar 31, 6:53 pm, zain 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 relatio
On Mar 31, 6:53 pm, zain 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 reference
I think inplace edit functionality could be very useful. You can take a look
to this Django application:
https://tracpub.yaco.es/djangoapps/browser/inplaceeditform/trunk/inplaceeditform
For any model like that:
class Book(models.Model):
title = models.CharField(max_length=200)
body = mod
- Photo Management - crop, rotate (with ability to add more filters)
- Make it easier for people to create custom themes and styles for the
admin and change between them
- Allow models to be added twice with two modeladmins serving a different
process
---
Dougal Matthews - @d0ugal
Add and remove instances to/from formsets with a button click is much
needed instead of the current delete checkbox and `extra` handling
(both for formsets in general and for admin formsets in particular).
There is a snippet (that I've not tried) at
http://www.djangosnippets.org/snippets/1389/
.
- Dynamic Managers
- Select which field you want to filter by and boom. No hard code
- Finer Permissions (not exactly an interface suggestion)
- Limit the ability of a user right down to the created object
- You have many accounts and you can assign an agent permissions to
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 a
14 matches
Mail list logo
