I very much like the look of that one, but I'm not sure if it completely fills the need I want for my own project. All of the fields need to be quickly visible, without needing to know the rendered name of the instance.
Those 'new inlines' address the problem of space, but they cater to those who already know what they're looking for. My coworkers need to constantly look over lists of location addresses, and require that all the fields are displayed for quick scanning. In other words, the users of this particular admin page will rely very heavily on it to show them all the data at all times. Another improvement to inlines in general would be to make them sortable. There are some Javascript enhancements out there for sorting HTML tables by any column, by clicking on its <th> tag. The 'new inlines' don't really allow for this possibility. (I did make a simple app out of the TiledInline: http://code.google.com/p/django-tiledinline/) Again, thanks for the feedback! I should play more with those new inlines. I really do think that there is potential there, as with most of the wonderful things that come from GSoC. Tim On Nov 7, 5:23 am, Renato Garcia Pedigoni <renatopedig...@gmail.com> wrote: > Hi Tim > > Wouldn't be the 'new inlines' [1] of GSoC admin improvements a nice > approach? The height is fixed, no waste of space... And no need to have > blank fieldsets for new objects (the 'extra' inline option). > > But anyway sometimes Stacked and Tabular just don't fit, it's nice to have > another way to show related objects. > > [1]http://media.wilsonminer.com/images/django/related-objects-stacked.gif > > Renato > > > > > > On Fri, Nov 6, 2009 at 11:59 PM, Tim <tonightslasts...@gmail.com> wrote: > > > On Nov 6, 6:20 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > > > This sounds interesting, but I'm having a hard time visualizing it, > > > any chance you could provide some screenshots? > > > Absolutely. I wrote up a blog post about it today: > >http://mangos.dontexist.net/blog/?p=352 > > > There are a couple of screenshots listed there. > > > I truly find this most useful when dealing with TextFields, like I > > mention in the blog post, because if you get 5 or 6 of those together, > > they get really wide really fast, and neither the Stacked nor Tabular > > really suits the situation, in terms of usability. > > > > As for whether it > > > should be included I'd say the first step is to get it out there in an > > > app anyone can download, as things like this can live outside of > > > Django. > > > Yeah, with the blog post there is a zip file download. It's not > > really in an "app" form, but that can be done fairly easily. I shall > > put one together, for the sake of getting it working as close to zero- > > config as possible. > > > Thanks much for the reply. Glad to hear some interest. > > > Tim > > > > Second, if you are serious about getting this included in > > > Django I'd file a bug and upload a patch, it's much easier to discuss > > > these things when there's something concrete on the table. > > > > Alex > > > > -- > > > "I disapprove of what you say, but I will defend to the death your > > > right to say it." -- Voltaire > > > "The people's good is the highest law." -- Cicero > > > "Code can always be simpler than you think, but never as simple as you > > > want" -- Me > > -- > Atenciosamente, > Renato Garcia Pedigoni --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
