Miakoda
@syndical @mkj @bipartisan @libreoffice
...Am I missing something on the UI? I wrote a letter in LO like 2 days ago, and it looks fine. It looks exactly how I'd expect a word processing program to look.
There was a period of time it looked a mess, but that was years ago.
🤷♀️ What am I not seeing?
João Tiago Rebelo (NAFO J-121)
@syndical I understand not every LO user is technical-minded, but if the developers don't know there's a bug it might go unnoticed for a long time/forever.
I agree UI/UX improvements are needed, those have to happen incrementally, big jumps need to be well measured (and mostly pay-to-develop). I started with StarOffice too, ver. 5 or 5.1, can't remember, went with OOo right away and then LO), so you know how it went whenever UI changes happened (even the optional ones, for example the tabbed experience), a dam of cries and moans breaks, but not much "this doesn't work well, please test that or that as alternatives" is heard. We need the community to steer the project and user's voices are essential to steward it. Their financing (when able) is too.
@mkj @bipartisan @libreoffice
syndical
@jt_rebelo @mkj @bipartisan @libreoffice
And here it is again. *I* can, and do, do those things (and I'm not asking for help). None of that is a reasonable ask for the average user, nor is it their fault or setup that causes this suite to look or act poorly.
And yes, one can expect consistency and stability across multiple platforms and setups, or do you think every other application that achieves this is somehow magic?
I'm not throwing shade at the Libre team - a suite like this is a massive undertaking, and star/open/libre has been my go-to for literally decades, whenever possible. But until there's some UI/UX modernization and stability improvement, for which you can *not* push responsibility back onto the userbase, then LO will remain that suite that people use when there's no other option.
João Tiago Rebelo (NAFO J-121)
@syndical and you are able to contact LibreOffice developers, give them all the help you can (your system config, etc.) so that it doesn't happen to you again (or anyone else, for that matter). You can't expect the developers to know every bug that might happen on hundreds of thousands of different system configurations, right? You don't to be a coder to say "I've encountered this bug/behaviour".
As for the UI/UX, needing more people means more voluntary designers or having to pay. I haven't donated that much to the project (trying to change that little by little), but those that want to see those improvements should, so that everyone can enjoy them.
That's the beauty of FLOSS software, you can use it for free and whatever your interest in the software is, you are a stakeholder, you matter and you can make your voice heard, help better it as you see fit.
I don't use a Mac, so I can't help, but in the forums (or here) there might be someone that can help you. It's not like MS throwing QA testers with the bath water and expecting you to pay while bugs and security fails show up every other day.
@mkj @bipartisan @libreoffice
syndical
@mkj @bipartisan @jt_rebelo @libreoffice
I adore Libre, I've been a user of this codebase since StarOffice. But...
While unhelpful, he's not _wrong_. Libre needs needs needs to find designers and work on the UI/UX, and it can't just be pawned off to the problem reporters to help. This is an office suite - the vast majority are not coders of any stripe, and never will be. Take a look at this completely vanilla install of Libre on Mac. Then it crashed while I was changing settings.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.