https://bugs.documentfoundation.org/show_bug.cgi?id=135501
--- Comment #110 from V Stuart Foote <[email protected]> --- (In reply to Telesto from comment #109) > (In reply to John Mills from comment #107) > So question is about committing to the Tabbed UI as the way to go. And > allocating resources to it. "... allocating resources to it." So, let's ask what dev resources this would commit: 1. Replacing the GLADE based MUFFIN assemblage used for the 'Tabbed UI' with os native code (qt, kf5, gtk4, WDM, Aqua/Cocoa) 2. give up MUFFIN (and all its dynamic UI goodness for users), because we would have to focus dev efforts on the native os code the refactored 'Tabbed UI' and integration for each DE would need 3. Client Side Decoration (the os/DE native code that places program features into an application frame's title bar) 4. assuring correct focus events cross platform for assistive technology for all that new native code And I'm sure a bunch of facets I've missed. Which makes for a simple (and continuing pragmatic) -1 as this contributors perspective. There are other functional areas of UX support for ODF documents that need the attention more than implementing a tabbed UI. -- You are receiving this mail because: You are the assignee for the bug.
