[Libreoffice-bugs] [Bug 132323] Make SKIA default. Move OpenGL and GDI rendering to Expert configuration

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=132323

--- Comment #5 from Telesto <telesto at surfxs.nl> ---
(In reply to V Stuart Foote from comment #2)
> As the Skia implementatio matures, I could see moving the OpenGL related
> settings to Expert Configuration near term (eventually removing), but the
> checkbox to disable Skia, and enable either CPU or the Hardware Acceleration
> rendering is still useful.

GDI
I have no objection with GDI being around for a while longer; if Hardware
Acceleration is a part of it stay's. 

However the should be a time path to phase it out. Marking GDI as depreciated
starting with 7.0. Stopping official support with 7.0 release (except urgent
cases, maybe?) The setting should move to the Expert Configuration starting
with 7.3.. While dropping it at 8.0. Not written in stone.. situations can
change of course, but a course must be set.

OpenGL
Again deprecation starting with 7.0. However, it should go faster, IMHO. The
multiple choice back-ends flooding the UI; confusing. OpenGL was always
somewhat broken. The DEV's aren't interested in it.. and we have to start
somewhere with dropping support. And makes QA problematic.. I'm not inclined to
test multiple backends for bug reports... So if XOR rendering on Skia is fast,
but slow on OpenGL, not my problem..

Also, I guess all (nearly all) the Alpha testers are already using Skia.. So
nobody will notice bugs sneaking into OpenGL/GDI; which is also a problem. 

-- 
About SKIA, Julien is right about the SKIA support. There needs to be more than
one libreoffice developer available. And the developer should really commit to
the Skia (at BoD/ESC level). Not running away at the point when the
complains/bug come in.. The Firebird tragedy is combination of an immense lack
of testers, and an 'broken' tender (support, cleaning up the issues afterwards,
seems not to be included). Personal experience, 'developers' - i'm generalizing
-  are available as long as the a working on it.. story is somewhat different
for bugs appearing 6 months later..  

They should be committed fixed 'the flood' of bugs report asap.. Luboš is doing
a great job at this point in time.. There must be a (soft) guarantee someone
will support it the future ... Skia shouldn't become the next OpenGL
implementation [again no offence the developers who worked on it.. it didn't
turn out as expected I guess]

Another question is what the targeted audience is. Is Skia Windows only. Or
is/will it be also also for Mac and Linux, please let it be; yes? On what
timeframe? What about the different Linux backends.. I have seen a post arguing
the depreciate X11. Reducing those means more developer time for Skia and
repairs being useful for a large group.

LibreOffice Fresh has always been 'some sort' of beta. It can not be called
that way, because everybody would skip it waiting for the final. Final never to
be archived without testers. So we call it final, being a factual a beta or RC.
Depending on the quality standard of the Development team. There are Beta with
quality of final release. Betas with quality of a RC. RC with quality of beta.
Beta with quality of Alpha.. I have seen some releasing passing by with know
horrible bugs.. to be fixed in second or third .3 release.

--Going even more offtopic--
About the Firebird experience
Is there actually somebody in QA who is testing Base. Alex Thurgood? The Base
support scarce.. at QA level as at Dev level and user base is pretty small to
(and is getting even smaller as the bugs accumulate)

MacOS
There is no MacOS developer around, except Tor, once in a while. The code is
'legacy'. There are enough depreciation warning within the code. It still
surprises me it's still working; more or less. It really needs some love.
However, again a 'small' group of users.. no dev available (and or lacking the
Hardware). And fixing if for 'free' while Mac users can afford Macs is still an
issue. There should be specific donation campaign/ crowdfunding project..
assigned to make LibreOffice Mac great again. Or the whole Mac stuff must be
commercialized.. it's already, more or less:
https://apps.apple.com/us/app/collabora-office/id918120011?mt=12. Except Apple
getting the biggest part of the earnings (I assume). A even worse deal, paying
€29,99 and still broken.. The NeoOffice fork is a far better deal being
functional; however lacking features and security fixes. However we enter the
terrain of 'open source' and 'commercial interest'. Sometimes I wish that a
company could hold back fixes for some time to make a 'profit'. It's impossible
to earn something if say Collabora fixes Mac issues while a TDF build with the
same fix is available freely immediately afterwards. We come in the area how
NeoOffice handles it. With the code being open source.. however not pre-build.
Which in my vision would mean, TDF holding of for a while compiling with
fixes.. however, tricky area.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200422/34f0d9a4/attachment-0001.htm>