<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Working on papercut bugs is somewhat crucial. </div><div class="gmail_default" style="font-family:tahoma,sans-serif">If the user experience with each module of Libre Office demands that the user has to use work-arounds to get work done in LO then he will just use other officesuites where he won't face those same issues. </div><div class="gmail_default" style="font-family:tahoma,sans-serif">Getting someone to fix those issues would be crucial. </div><div class="gmail_default" style="font-family:tahoma,sans-serif">An example in Calc like the one Renon posted in Impress is this one: <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=53300">https://bugs.documentfoundation.org/show_bug.cgi?id=53300</a> </div><div class="gmail_default" style="font-family:tahoma,sans-serif">A bug that exists since Open Office days... With LO and the TDF constantly bragging about having cleaned up so many bugs in LO it's unforgivable that UX bugs like this one are still lingering from Open Office days. </div></div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Feb 3, 2018 at 7:58 PM, Michel RENON <<a href="mailto:renon@mr-consultant.net" target="_blank">renon@mr-consultant.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Le 31/01/2018 à 21:48, Heiko Tietze a écrit : <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> [...] GSoC * Full list of ideas <a href="https://pad.documentfoundation.org/p/UX-GSoC_Ideas" rel="noreferrer" target="_blank">https://pad.documentfoundation.org/p/UX-GSoC_Ideas</a> * Public list <a href="https://wiki.documentfoundation.org/Development/GSoC/Ideas#User_Interface" rel="noreferrer" target="_blank">https://wiki.documentfoundation.org/Development/GSoC/Ideas#User_Interface</a> </blockquote> Here are some suggestions based on my recent experience in teaching LibreOffice and writing a python macro : Impress : work on "papercut" bugs ---------------------------------- 1 - Animations sets for a text box with several paragraphs don't affect new paragraphs (not inherited) <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=57581" rel="noreferrer" target="_blank">https://bugs.documentfoundation.org/show_bug.cgi?id=57581</a> This is the most annoying problem that new users face : - they create a slide with few lines of text, - they add an animation on the text, to make it appear line by line - they test : it works correctly - they add one line of text (inside or at the end) - they test and boom... the animation is "broken" - they make a pause, then... close impress and open powerpoint... 2 - Editing: Text spacing changes when click in textbox <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=89060" rel="noreferrer" target="_blank">https://bugs.documentfoundation.org/show_bug.cgi?id=89060</a> It is a subtle but very annoying visual effect. Python macros ---------------- I had to create a macro embedded in a file. As I had not written basic for a long time, I tried to write it in python. The fist problem is that on Ubuntu, it is necessary to install a specific package 'libreoffice-script-provider-python' The second problem is that, by default, there is no tool to integrate a python macro in a document. I found the APSO extension [1] that allows that and is very useful. I found some difficult points in writing python macro with that extension : - after modifying a python script, you have to close and re-open the odf file - some inline documentation is missing : about API, and some sample code - the context (available via XSCRIPTCONTEXT) is missing some API, compared to basic So here are my suggestions for GSoC : - allow an easy activation of python support : a simple button would download and install all necessary packages - integrate the functionality of APSO (to allow embedding/managing python script in odf file) - remove the need to re-open the odf file before using a new version of python script Other points can be done directly in the current extension : - add some inline documentation about API [2] - add inline documentation on both ways to use python script : - an external script that connects to LibreOffice - an internal script that get called by menu/button - allow to create scripts empty or with comments (that provide minimum documentation and good practice) - add a library of sample code (a list of "how-to ?"), that can be easily copied in script files Adding API to the context (available via XSCRIPTCONTEXT) can be done by working on LibreOffice code : /usr/lib/libreoffice/program/pythonscript/py Cheers, Michel [1] <a href="https://extensions.libreoffice.org/extensions/apso-alternative-script-organizer-for-python" rel="noreferrer" target="_blank">https://extensions.libreoffice.org/extensions/apso-alternative-script-organizer-for-python</a> [2] based on very useful page <a href="https://wiki.openoffice.org/wiki/Python/Transfer_from_Basic_to_Python" rel="noreferrer" target="_blank">https://wiki.openoffice.org/wiki/Python/Transfer_from_Basic_to_Python</a><div class="HOEnZb"><div class="h5"> -- To unsubscribe e-mail to: <a href="mailto:design%2Bunsubscribe@global.libreoffice.org" target="_blank">design+unsubscribe@global.libreoffice.org</a> Problems? <a href="https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/" rel="noreferrer" target="_blank">https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a> Posting guidelines + more: <a href="https://wiki.documentfoundation.org/Netiquette" rel="noreferrer" target="_blank">https://wiki.documentfoundation.org/Netiquette</a> List archive: <a href="https://listarchives.libreoffice.org/global/design/" rel="noreferrer" target="_blank">https://listarchives.libreoffice.org/global/design/</a> All messages sent to this list will be publicly archived and cannot be deleted </div></div></blockquote></div> </div>