Better support for 3rd party panels needing URLs/views.

[robhudson]

This is an idea I had long ago but apparently never wrote down.

The idea was: imagine if the SQL panel were a 3rd party panel. The steps to integrate the panel would require both a debug toolbar setting to activate the panel but also a URL insertion to map a new URL to the view.

My thought was we could adopt something similar to what the admin does where it allows custom admin URLs to be added. I think it's get_urls on the admin class or something.

If panels had a similar mechanism to provide their own URLs and views, that opens up more options for 3rd party panels to be able to do their own calls out to views for AJAX or the like.

[aaugustin]

Yes, that's a good idea, and built-in panels should use this API too.

[aaugustin]

Whoops, this issue is still valid. The commit linked above merely sets the stage.

[aaugustin]

f48039e was an important step towards this goal.

Now that I have DebugToolbar.get_panel_classes(), I can easily implement DebugToolbar.get_urls() to collect URL patterns provided by each panel.

The syntax for including URLs will have to change, I think I can make it as simple as:

if settings.DEBUG:
    urlpatterns += patterns('',
        url(r'^__debug__/', include(debug_toolbar.urls)),
    )

where urls will be a callable implemented in debug_toolbar.toolbar and imported in debug_toolbar.

[aaugustin]

The solution I just committed looks pretty clean to me.

@robhudson, let me know if you have suggestions.

[robhudson]

Beautiful.