https://bugs.documentfoundation.org/show_bug.cgi?id=37134
--- Comment #120 from Roland Hughes <[email protected]> --- I didn't consider the last comment spam until I clicked the link. Had it actually been a UI best practices document that was free to read it would have been a nice post. It was a useful post in that it generated email reminding me of just how long this bug has been open. Given my 4 decades in IT I feel the need to point out LO is a legacy product. Yes, I used it to write some of the titles in my award winning technical book series https://theminimumyouneedtoknow.com/ trying to use Open-Source for everything, but, the last couple titles in that series as well as my latest novel, https://twentyoftwo.com/ were written with TextMaker. No, that's not spam, that's a writer's assessment. LO simply became unusable. In all honesty, what we've learned here, is really big stuff can't be designed by committee. Eventually you need a very small team and a clean sheet of paper. Most importantly, Agile is NOT Software Engineering. The first clean sheets of paper need to be filled with the Waterfall SDLC. First a list of features and "how" from a high level. Then you choose the programming language and tools. Some of the posts on this thing are from 2011. We can agree IT has changed dramatically since then. When SUN initially launched this it was to let Java strut its stuff. SUN is no more. Java is now used in fewer places than FORTRAN. (The dirty little secret of the AI world is the fact almost everyone of them is using FORTRAN and suddenly FORTRAN job openings are everywhere.) Is C/C++ still the language for this? It certainly has the most developers with college degrees, but I haven't kept tabs on other languages word processor/text editor capabilities. I know CudaText https://cudatext.github.io/ has exploded as an Open-source text edtior and it is written in Object Pascal if you can believe that. In the current world of C/C++ re-development (or my world) everybody is re-basing on SDL3. https://wiki.libsdl.org/SDL3/FrontPage Provides full cross platform I/O, ttf rendering, and lets mere mortals for font rendering and other uses so applications speed up. Whenever are peruse the LO bug database, almost every one of these bugs/feature requests as a "the size of the code base" argument against it. So, with respect to tabbed UI, just how much of the code base could be eliminated by using SDL3 or some other modern, well maintained, cross platform I/O and rendering pacakge? Haven't looked at your code, I've got my own legacy modernization stuff going on with LS-CS https://github.com/RolandHughes/ls-cs a fork of CopperSpice which is fork of Qt 4.8. Even in today's Qt that just dropped Windows 10 support to howls from customers on the mailing list, there is an ocean of dead legacy code. I just got rid of about half the code base in LS-CS. Yes, there have been many release notes over the years about "eliminating dead code" but how much code is LO maintaining for functions that should be provided by a modern industry standard 3rd party library? -- You are receiving this mail because: You are the assignee for the bug.
