Working with DMFs for client-side commands is painful. The command input boxes are really small, they require a ton of escaping to be done manually by the user, and they just take absolutely forever to iterate and test. Each time you change something, you have to open the DMF, navigate to the element you want to change, right click on it (if you can), or use the element menu to grab it, and edit its properties, then go through the tabs to find the control you want to edit, then you have to squint at the tiny text box that likely only has space for a fraction of what you are putting into that box.

There's a neglected part of the engine that could make this a ton easier. DM scripts allow you to define aliases that make command entry more convenient for users.

But what if we could harness this same convenient command syntax in macros in the skin to tape back our big ass client-side winsets/winget/output commands behind a simple to remember and type name that doesn't overflow the command box in the skin?

This would really massively improve working with the DMF. Users would be able to quickly iterate on and visually debug their winsets in the code editor, format things in a more user-friendly way, and spend less time clicking through menus to alter commands.

Right now, many of the old client-side commands are accessible because aliases jump to the back-end command entry parser. However, the front-end stuff that was added to do client-side ui scripting isn't accessible from aliases.

It would just be a massive facelift to a pernicious part of working in the engine that nobody likes. And I mean, DMS is just neat.