Request a feature
The suite grows because customers ask it to. If a control is missing something your work needs — a property, a behaviour, a rendering mode, an event — say so here.
What makes a request buildable
Every control in the suite has to work in an application it knows nothing about. That one constraint decides what can be built and what cannot — and it is worth a moment before you type, because a request framed the right way is usually a request that ships.
Goes straight on the list
- A capability any application using that control would want — not just yours.
- A property, an event, a command or a method that ought to exist and does not.
- A look: a rendering mode, a theme, a glyph set, an animation, a print or export format.
- A behaviour: keyboard handling, selection, drag and drop, virtualisation, accessibility.
- Something you are working around today — tell me the workaround, it is usually the clearest description of the gap.
Cannot be built into a control
- Anything tied to your own data, screens or workflow. A control that knows about one application is no longer a control.
- Wiring the suite into your codebase, or debugging your application — that is support, and it is included with your licence.
- A private build for one customer. Everything here ships to everyone, which is also why it keeps being maintained.
- A change that would break the public API for existing licensees, unless it can be added alongside what is there.
The line is usually easy to find: “sort every branch by a column” is a control feature. “Sort my invoices tab the way finance likes it” is an application feature built with that control.
Tell me what it should do
Nothing here is tracked and there is no account to make. An email address is the only thing I really need — without one I cannot tell you what happened to your idea.
What happens to it
- It is read, by meNo queue triage, no bot, no ticket number. Requests are read as they arrive.
- You get an answer either wayIf it can be built you are told which release it is going into. If it cannot, you are told why — usually because it would need the control to know something about your application.
- It ships to everyoneAccepted features land in a named release, go into the release notes and the documentation, and reach every licensee at no extra cost — including you.