General Activities LibreOffice 25.2.4 was announced on June 6 Olivier Hallot (TDF) added help for compact layout Pivot Tables, Writer table formula MOD and improved the help for Writer’s Send menu commands, font colour, text attributes for drawing ob…
IMO the old Tree menus seem like the best system for complicated option GUI's with many views to show.
Then you can describe this in JSON, with metadata for whether the data is a dropdown or number turner etc. and you make a generic view loading code to auto-generate the view based on the JSON.
Then for any temp changes you have a in-memory copy until apply/ok and that gets looped and applied to the settings file.
how will that work with languages like German where terms are usually longer than in English? The multiple rows of tabs are not ideal and predictable. But at least they wrapped, if I recall correctly.
@haskins Or perhaps there are genuine reasons for changing it, beyond UI developers "justifying their existences". But that would require actually reading things, such as the Design team meetings and Bugzilla reports, to see the justification for the change. But no, easier to pretend they are just "justifying their existences". Whatever works for you 😉
me·ta·phil, der
in reply to LibreOffice • • •YourShadowDani
in reply to LibreOffice • • •IMO the old Tree menus seem like the best system for complicated option GUI's with many views to show.
Then you can describe this in JSON, with metadata for whether the data is a dropdown or number turner etc. and you make a generic view loading code to auto-generate the view based on the JSON.
Then for any temp changes you have a in-memory copy until apply/ok and that gets looped and applied to the settings file.
Stefan Ihringer
in reply to LibreOffice • • •Kari Perttula
in reply to LibreOffice • • •Or can we stay using old tab orientation, if we like that more?
haskins
in reply to LibreOffice • • •LibreOffice
in reply to haskins • • •