3 ms·
"how often have they built bespoke widgets for Office rather than using their public APIs" I don't know. How many? UI/UX development is a two-way street. The
by canucker2016 3y ago
"how often have they built bespoke widgets for Office rather than using their public APIs"
I don't know. How many?
UI/UX development is a two-way street. The OS includes a basic set of UI controls for common scenarios. But it can't anticipate every situation.
MS Office's Ribbon is designed to show only the actions available given the current selection and document. A toolbar would show available actions, but also have the invalid actions disabled, increasing required screen space. Is there some other standard Windows control that could have worked instead of the custom Ribbon?
- hnlmorg 3y agoI can think of 3 different occasions. First was when the menu bar would show a bezel when you hovered over it, which didn't happen normally in Windows. The second was when the menu bar became detachable like a tool bar. That also wasn't supported by public Windows APIs. The third was Ribbon. That I can at least forgive a little more because it's a massive shift in UI/UX. But the first two instances were so subtle that most people wouldn't have noticed, which then begs the question, why even waste resources literally reinventing their own APIs?