Changes between Version 12 and Version 13 of DjangoDesign

Timestamp:

Feb 8, 2010, 6:21:30 PM (15 years ago)

Author:

Russell Keith-Magee

Comment:

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

DjangoDesign

@@ -1 +1 @@
 = Django Design =
 
-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.
+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.  If the idea relates to a Trac ticket that is already open, provide a reference the ticket.
 
 == Quick Hits ==
@@ -23 +23 @@
 When 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)
 
+=== Better UI for raw keys ===
+
+Raw Foreign Keys and Raw m2m widgets work, but provide poor UI feedback. Ticket #7028 proposes to fix this, and has a draft patch.
+
 === Dashboard "Placeholders" ===
 
@@ -31 +35 @@
 Apps 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)
 
+== Tool Changes ==
+
+Changes to the tool set that Django provides that would make life easier as a Django-based designer, such as changes to the template language. 
+
 == Valuable external resources ==