How is this different from tyler36/ddev-xhgui?

[rfay]

tyler36/ddev-xhgui will likely be the basis of a core xhgui feature, or perhaps an official add-on.

How is this different from that one, which has a lot of support?

If it's not in active use, could you remove the ddev-get label from it to avoid confusion?

[seebeen]

This one has batteries included - it configures everything automatically - and doesn't require any additional user actions - such as adding profiler library etc

[rfay]

Hmm, ddev-xhgui doesn't require anything but suggests some composer add-ons.

Anyway,

• Please make the difference clear in your readme
• Contributions to tyler36/xhgui would be a great thing.

In our DDEV plans for this year getting a great xhprof experience for users is a key idea (see Features there). Your ideas are welcome. If you flesh them out in the README or whatever it at least gets us your ideas. Or perhaps an issue in tyler36/ddev-xhgui, or in one of the open ddev issues

Thanks!
Your experience as an actual user and maker in these things is super important.

[seebeen]

No probs. I can flesh out the reasoning behind this separate addon and a roadmap. You're more than welcome to take any good ideas and flesh out an official feature. Would be more than willing to implement it fully.