I'm not sure if this is the place but here are some other issues or questions I have if this were to happen...
* The jQuery question is a big one. I've taken strides to make the debug toolbar interoperate with other popular JS frameworks (mootools and prototype, namely). But if jQuery were decided against, would it make sense to re-use some of the Javascript libraries that Django has developed for its admin? Would it use the same admin media handler trick? * Which set of plugins are included, and of those that have settings, what are their defaults. Some defaults currently optimize to general case and provide more debugging information, but on larger sites performance may suffer severely. It may make sense to take a philosophy of best default performance with opt-in added debugging. * Should there be a place for plugins (panels) that don't make the cut? Panels consist of some Python and some HTML, so it's not a single file. They *could* be changed to work similar to form.widgets with a render method and HTML backed in... but I'm not a huge fan of that. But it would make it a bit easier for posting on a site like Django Snippets. * Should the UI match that of the Django admin (overall theme, colors, etc)? * If the debug toolbar is incorporated, should we consider different integration options? e.g. Currently the debug toolbar injects URLs into the project in a rather ugly way -- could this be done better if it were part of Django? Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
