Implement a serious debug toolbar

[sedax90]

Having a good debugging tool it is fundamental for a good project development. Currently the best tool of all pph framework is definitely the debug toolbar Symfony2.
It would be nice to have a tool with similar functionality already built into Magento, would greatly simplify the work to each developer.

[mzeis]

This would definitely by a good addition.

[Flyingmana]

I would vote for using the symfony (or zend, I think they have one, too) toolbar as base

[alankent]

Z-Ray has a Magento 1 toolbar and will probably have a Magento 2 toolbar too. I am wondering whether this is best done as an extension? What is reason for making part of core? Or a hackathon project? (Curious to hear different opinions.)

[mzeis]

If I remember correctly, you only get Z-Ray with Zend Server, right? That would rule it out for us pretty much.

In my opinion it should be part of the core to support integrators (dev toolbars can speed up development quite a bit because you don't have to insert debug code / trace for the same reasons again and again).

If there will not be a developer toolbar in the core, for sure there will be several implementations by the community again. I'd like to see a joined effort, be it inside or outside the core.

[sedax90]

Drupal 8 has a module who integrate perfectly Symfony2 profiler (https://www.drupal.org/project/webprofiler). I do not think it's too expensive to incorporate in magento if we think of the enormous benefits that would bring.

[alankent]

An interesting question to me is whether "we" need to do a better job to coordinate larger community projects vs just wait for the core team to get to it. Peripheral projects like this feel more community friendly. How many community members would be be interested in helping this one? Is the job then more to work out a framework to help community members to collaborate? Eg define some best practices for teams to work together (working groups). To me this clearly should be a separate module so it's optional, but it makes sense having just one with lots of people contributing.

For example, we set up a list of "community projects" in a wiki page or something, then get a Magento engineer to be the bridge between core development and each such project, a community lead on the project and a list of volunteers. (I am sure we can borrow a process from some other project.)

[wojtekn]

If you decide to include toolbar in core, maybe just build a base which provides foundation. Then extension developers could extend it and add new toolbar features. Core toolbar could include debug features which already exist in core (enabling/disabling profiler, hints, inline translation, displaying profiler output etc.) and more could be added by community.

[roman204]

Good idea @wojtekn, and are the core developers not also missing such a feature ? So many things in Magento2 are inspired by the community... but a "core" developer toolbar not :-(

[vpietri]

In order to discover Magento2 I've made a simple developer toolbar https://github.com/vpietri/magento2-developer-quickdevbar . Let me know how can I improve it.

[pboisvert]

@piotrekkaminski Piotr can you take this one for dev experience?

[piotrekkaminski]

This is not currently a priority since external projects exist that seems to be tackling this issue:

• https://github.com/vpietri/magento2-developer-quickdevbar
• http://store.pulsestorm.net/products/commerce-bug-3