Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Just occurred to me, like the idea in many ways:
Design:
Have a setting for devel which, when checked, doesnt generate Krumo output into the #messages region, but enables a new menu item www.mydrupal.com/develOutput.ajaxPage
This page manages your devel output, all through ajax.
Benefits:
Inital page load is much faster (Krumo is not run during base page load. This will improve development time (in some cases dramatically)
Issues with producing devel output during the theme layer (currently the krumo output shows up on the next page load, which is functional), can be overcome using some Ajax simple tricks
Extensions:
E.g. Keep some page load history, various other stuff.
Difficulty:
Use the existing methodology that holds devel output between page loads, and just pull it out by ajax. Have hook_exit mark when the page has actually been sent to the client.
Id be happy to do some work on that, though I have absolutely no time until after October 25
Comments
Comment #1
salvisYes, that sounds very interesting. I can't tell whether it can be done and at what cost.
However, as always, D8 would need to go first. We can't develop new features for D7 which will not be there after upgrading to D8. I'm afraid that D7 and D8 are very different in the relevant areas (and D8 is still under construction)...
Will this require a lot of changes to Krumo? Moshe has said in the past that he'd like to get our own implementation of Krumo-like functionality, rather than further hacking Krumo.
Incidentally, what would happen if we're already using multiple browser tabs, maybe even switching users?
Comment #2
willzyx CreditAttribution: willzyx commentedKrumo was removed from 8.x branch. Moving to 7.x