Django Debug Toolbar 1.0 beta released

4,972 views
Skip to first unread message

Aymeric Augustin

unread,
Dec 15, 2013, 8:11:50 AM12/15/13
to django...@googlegroups.com
Hello,

I'm happy to annonce that we're almost ready to release version 1.0 of the Debug Toolbar! Now we need your help to try the beta:
https://github.com/django-debug-toolbar/django-debug-toolbar/releases/tag/1.0-beta

The documentation is available on Read the Docs — make sure you read the "latest" version as there are many changes since 0.11:
http://django-debug-toolbar.readthedocs.org/en/latest/

Note that the setup process is different from previous versions:
http://django-debug-toolbar.readthedocs.org/en/latest/installation.html#quick-setup

Please report issues on GitHub:
https://github.com/django-debug-toolbar/django-debug-toolbar/issues

If no major problems are found, we'll release 1.0 in one week.

Here are the main changes from version 0.9.x and earlier. (Versions 0.10 and 0.11 were transitory versions leading to 1.0; they were released to validate some choices before committing to support them for the lifetime of 1.x.)

- Panels are now rendered on demand, solving the "20MB HTML page" problem
- Panels can be individually disabled from the frontend, in case a panel degrades performance severely on a page
- Interception of redirects can be toggled from the frontend
- The handle can be dragged along the right side, in case it hides exactly the part of the page you're working on :-)
- Static files are managed with django.contrib.staticfiles, solving a series of URL-related issues
- The setup process was rewritten, to provide a simplified automatic setup and an optional explicit setup
- Panels and settings received shorter or better names
- A stable API for third-party panels is documented
- The core of the toolbar was simplified drastically and almost all the code was refactored into panels
- The toolbar was made compatible with all current versions of Django and Python, including Python 3.
- The test suite was expanded and gained Selenium tests
- Dozens of bugs were fixed

I hope you'll like it!

--
Aymeric.

kamagatos

unread,
Dec 16, 2013, 6:33:46 AM12/16/13
to django...@googlegroups.com
Aymeric, I think the debug toolbar is very useful. I use it all the time. But on the other side, we should start thinking about a way to catch and display every ajax/json responses. because more and more applications are becoming ajax ready and they use front-end frameworks like angularjs or backbone to deal with getting stuff on the backend. I hope it makes sense.

Aymeric Augustin

unread,
Dec 16, 2013, 6:46:09 AM12/16/13
to django...@googlegroups.com
On 16 déc. 2013, at 12:33, kamagatos <kama...@gmail.com> wrote:

we should start thinking about a way to catch and display every ajax/json responses. because more and more applications are becoming ajax ready and they use front-end frameworks like angularjs or backbone to deal with getting stuff on the backend.

Several people have already thought about it, and some have written code: https://github.com/django-debug-toolbar/django-debug-toolbar/pull/356. But as I’m not using the toolbar myself — I merely modernized it because I believe it’s an important component of the Django ecosystem — I’m lacking motivation to write that feature.

Fortunately, in version 1.0, the core of the toolbar has been slimmed down drastically; almost everything is implemented in panels. You can implement the feature you’re describing as a third-party panel, without any changes to the toolbar itself. If you write such a panel and it works well, then we could discuss merging in the toolbar.

The public API for panels is documented here: http://django-debug-toolbar.readthedocs.org/en/latest/panels.html#api-for-third-party-panels. I hope this helps!

-- 
Aymeric.

Thomas Weholt

unread,
Dec 16, 2013, 7:30:28 AM12/16/13
to django...@googlegroups.com
I'm especially happy to see support for Python 3. Very nice.



--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2d498dbe-3880-4986-9dc6-a4f7a68ed1b6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
Mvh/Best regards,
Thomas Weholt
http://www.weholt.org

Aymeric Augustin

unread,
Dec 21, 2013, 4:33:54 AM12/21/13
to django...@googlegroups.com
Hello,

I just released 1.0 final. Enjoy!

--
Aymeric.
Reply all
Reply to author
Forward
0 new messages