Description: The Windows VCL tree view uses a style reminiscent of Windows 9x rather than newer Windows versions like 11. Steps to Reproduce: Open Writer. Press F11 to open the styles sidebar. Switch to hierarchical view (if not already active) Actual Results: The sidebar displays the tree view using + and - for expanding/collapsing and by visualizing the tree structure in dotted lines. Expected Results: The tree view should use chevrons (downward facing for expanded and rightward facing for expandable) and not visualize the tree with dotted lines. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded
Created attachment 199258 [details] Example tree view from Windows UI Kit
Created attachment 199260 [details] Current state tree view from Writer styles
Created attachment 199261 [details] Tree view mockup in Win 11 style.
@jan d, please stop spamming the BZ with these specific implementation ideas--here and bug 165134, bug 165148 Support for Windows Display Manager may or may not move toward native WinUI3, but as likely likely would move toward a cross platform Qt or Skia based VCL widgets and have no visible relationship to native WinUI. Specifics are as always the developers choice, taking input and advise from the UX and design community. Just as there was no movement to Metro, or UWP, there is no mandate that the UI follow WinUI3 and Windows 11 theming. Also, it is rude to throw BZ issues against a specific developer, Sahil has in no way agreed to implement any of this, please don't make such assignments.
No concerns from UX to implement native widgets (neither to switch to Qt, or the like).
@Stuart: I posted the findings about the potential problems with the current Windows UI in the UX where the response was positive; complaints about the Windows UI looking "old" is a major concern that the group thinks about. I was asked by Sahil to assign him. Nevertheless, I can refrain from posting these issues.
(In reply to jan d from comment #6) > @Stuart: I posted the findings about the potential problems with the current > Windows UI in the UX where the response was positive; complaints about the > Windows UI looking "old" is a major concern that the group thinks about. > I was asked by Sahil to assign him. Nevertheless, I can refrain from posting > these issues. Oh, very sorry then. Maybe a note that you'd been chatting with Sahil but still better to just add hime CC list rather than assigning it. Always best to allow the developer to make an assignment to themselves when they are actively working something up. But at this juncture, of dropping Win7/Win8.1 and pending EOL of Win10, it certainly allows some movement but we have to remain mindful of the underlaying VCL framework. For us to implement Win11 MS Fluent 2 norms (Win32 with WinUI3/XAML) is just not feasible to do with VCL cross platform--requires implementing/maintaining too much WinUI native code. Meaning simply "decorating" widgets to mimic Win11 theming becomes an endless maintenance chore. Better to accept that it is not feasible (too costly) and look to other implementations as Michael and Sahil have suggested.
Thanks for letting me know! > Meaning simply "decorating" widgets to mimic Win11 theming > becomes an endless maintenance chore. My impression was that the current theme is already decorated to mimic Windows theming – or do we currently bridge display native UI elements? To clarify my concern - it is not the problem that LO does not look like Win 11 per se but that the current styles are a mix of elements from different versions of windows.