Ideas for the next releases of MxInspector. Same starting point as today: fast, lightweight, docked on any Mendix app, with nothing to install in the app itself. No dates and no promises: requests from Mendix developers decide the order.
Worked out and on the list for the coming releases. Everything stays client-side, like the rest of the panel.
Change a string, number, boolean, enumeration or date on an object in the Data panel and watch the page react. See what the UI does when that boolean is false, without touching the database.
Every object the Mendix client holds, grouped by entity: new, changed or untouched, and which widgets use it. A counter shows when the total keeps growing, so leaking non-persistent objects stand out.
Scans the page for [No translation], empty captions, empty labels and buttons without text, and points at the widget each one belongs to.
Save the state of the page, click a button, and see which objects and attributes changed and how much the DOM grew. Shows what an action did to the page.
Everything in the PDF report as structured JSON, for a ticket, a diff between two releases or your own scripts.
View the page with protanopia, deuteranopia, tritanopia or achromatopsia, or with low vision, cataract, glaucoma or macular degeneration.
Ideas that need research first. What the browser can see decides whether and how they ship.
Click through the app and every page you visit is scanned. One report lists each finding by page and widget, with the fix in Studio Pro and the WCAG 2.1 AA criterion. Criteria that need a manual test are marked as such.
Every call to the Mendix runtime per click, with duration and size. Click a request and the widget that made it lights up.
Screenshot, page name, the data on the page, console errors and the Mendix version in one file, ready to attach to a ticket.
Drag to measure distances. Hover to pick a colour and see the CSS variable behind it, plus every colour on the page.
Remembers the metrics per page, so you see when a page got slower or heavier. Kept in your own browser only.
Set your own warning levels, such as a DOM size or request count that fits your project.
A diagram of the entities and associations loaded on the current page.
Click an association to fetch and show the attributes of the linked object, within the rights of the current user. Apps in Strict Mode may not allow it.
MxInspector as its own tab in the browser's DevTools, next to Elements and Network, as an alternative to the overlay.
Tell me what you would like MxInspector to do. Requests decide what moves up this list.
Request a featureor mail hello@timothymaurer.nl
The situation helps more than a finished solution.
For example Mendix 10.18 on Chrome.
Of the panel, the page, or what you have in mind.
No names, records or URLs from client apps. A description is enough.