Design/Meetings/2022-03-16

TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate

• Wiki Home
• Development
• Design
• QA
• Events
• Documentation
• Website
• Localization
• Accessibility
• Marketing
• Diversity
• Wiki Help

• Design Home
• Whiteboards
• Development Blueprints
• UX Principles
• UX Guidelines
• Artwork Resources
• Branding Guidelines
• Meetings

Link

https://listarchives.libreoffice.org/global/design/2022/msg00032.html

Minutes

Present: Amina, John, Heiko
Comments: Cor

Tickets/Topics

 * LO should remember settings of last user session
   + https://bugs.documentfoundation.org/show_bug.cgi?id=141400
   + use case to have two documents side by side is relevant and
     we should store the window position in the document
   + as today, new documents should take the position/size of the
     last session, even when the document was not not saved
   + the document's window position/size overrules the workstation info
   => do it

 * Resolve state isn't tracked by track changes
   + https://bugs.documentfoundation.org/show_bug.cgi?id=147574
   + besides technical restrictions it's a question whether we want to
     track the resolved state of comments
   + unclear benefit from tracking the resolved state, would rather
     not clutter the TC info (Heiko)
   + only information that TC reveals is who resolved a comment,
     and having those makes sense to me (Amina)
   => go for it if competitors do it too

 * Make range highlight thicker when opening formulas in Calc
   + https://bugs.documentfoundation.org/show_bug.cgi?id=147927
   + agree with the request, makes the view more consistent (John)
   => do it

 * CSV import: "String delimiter" drop-down needs indication that it's editable
   + https://bugs.documentfoundation.org/show_bug.cgi?id=147858
   + valid request (Cor, John)
   + control is clearly different from simple dropdowns (Heiko)
   + options: a) separate positioning and a bit larger size, b) remove the
     dropdown in favor of text input (with default to double quote),
     c) tooltip / documentation
   => a) sounds like the best solution