Changes between Version 12 and Version 13 of DjangoDesign


Ignore:
Timestamp:
02/08/10 18:21:30 (5 years ago)
Author:
russellm
Comment:

Added a stub for tool changes, and added note about #7028.

Legend:

Unmodified
Added
Removed
Modified
  • DjangoDesign

    v12 v13  
    11= Django Design =
    22
    3 This page is a stub for collecting ideas and proposals for design-related changes to Django, specifically in the admin interface. Whenever possible, try to explain the practical benefits or a real-world use case for any proposals.
     3This page is a stub for collecting ideas and proposals for design-related changes to Django, specifically in the admin interface. Whenever possible, try to explain the practical benefits or a real-world use case for any proposals.  If the idea relates to a Trac ticket that is already open, provide a reference the ticket.
    44
    55== Quick Hits ==
     
    2323When selecting or creating related objects in the admin UI, you're often forced to open new windows, and if you need to create successive new items, you can quickly have four or five windows open at once. I know we can all agree this is a poor experience. I'm not proposing any solutions at this time, but there's definitely an issue, here. (JC)
    2424
     25=== Better UI for raw keys ===
     26
     27Raw Foreign Keys and Raw m2m widgets work, but provide poor UI feedback. Ticket #7028 proposes to fix this, and has a draft patch.
     28
    2529=== Dashboard "Placeholders" ===
    2630
     
    3135Apps should be able to register functionality outside of the typical "CRUD," for example status widgets, information displays, tasks that can be executed, etc. Somehow, apps should be able to extend the admin's functionality. (JC)
    3236
     37== Tool Changes ==
     38
     39Changes to the tool set that Django provides that would make life easier as a Django-based designer, such as changes to the template language.
     40
    3341== Valuable external resources ==
    3442
Back to Top