LibreOffice 3.3.0 (fork of OpenOffice.org) final released


Recommended Posts

Considering that most of the OO.org community moved over to LibreOffice...

Most have moved over? I haven't, and neither have my buddies. They haven't heard of LibreOffice until I pointed out this thread, and in the workplace we've all heard of OpenOffice but not Libre.

However, one shall keep an eye on Libre's progress ;)

Most have moved over? I haven't, and neither have my buddies. They haven't heard of LibreOffice until I pointed out this thread, and in the workplace we've all heard of OpenOffice but not Libre.

However, one shall keep an eye on Libre's progress ;)

Most of the community of OO.org developers at least has moved to LO. It's what will get new features and fixes in the future rather than OO.org.

Most of those complaining about the OO.org/LO GUI - myself included - simply prefer the Ribbon UI as introduced with Office 2007 over the old-style UI. To me the ribbon UI is much more logical than the old menus and toolbars; YMMV.

We all have different preferences but I've never cared for the ribbon myself. I can use it fine but I prefer menus. I am use to them and I can work faster. But to each their own.

It's why MS removed all easter eggs. you're no longer allowed to include undocumented features in apps. I think it's a side effect of a law against backdoors/malware/trojans or something. I also think it's a US think but noone will remove the easter eggs just for the US.

It's why MS removed all easter eggs. you're no longer allowed to include undocumented features in apps. I think it's a side effect of a law against backdoors/malware/trojans or something. I also think it's a US think but noone will remove the easter eggs just for the US.

I personally very much doubt that's the reason Microsoft stopped adding easter eggs in their software.

I personally very much doubt that's the reason Microsoft stopped adding easter eggs in their software.

you can personally believe anything, but that's why, that's why the easter eggs stopped after that law, and why MS said that's why they stopped them.

It's why MS removed all easter eggs. you're no longer allowed to include undocumented features in apps. I think it's a side effect of a law against backdoors/malware/trojans or something. I also think it's a US think but noone will remove the easter eggs just for the US.

I'm like 90% sure that's just for apps being used on governmental computers.

They're not getting it back, because it works. Unlike cheaply-made context browsing... like the Ribbon.

Drop-down menus work. And you can remove the toolbars.

Every person that needs a office suite that: just works, is gratis, works with legacy files, works in a plethora of platforms.

xP7EU.jpg

Being a dial-up user: **** off.

Here's an example of how the "cheaply-made context browsing" is far better than menus and toolbars:

Inserting Clip Art:

Office 2003

Insert Menu > Picture > from Clip Art

Office 2007/2010

Insert Tab > Clip Art Button

Yes, I know that you could use a button on a toolbar or drag and drop, but the method above is what the average user would do.

So, two clicks with the ribbon and three clicks with menus and toolbars. Which would you say is faster?

There are many examples that could be listed. But one of the biggest benefactors of the Ribbons is that each function has its own icon, is grouped together by function, and allows otherwise hidden features to be brought forward.

The more menus people have to dig through, the more likely that a specific feature will be ignored.

So, two clicks with the ribbon and three clicks with menus and toolbars. Which would you say is faster?
None is faster because you are doing it wrong in believing that HCI is just about benchmarking presses. Your "Ribbon" "just works" because it removes contexts blocks. Do you want an example? Where is the "Save" context block? There isn't one as a context block.

The "Ribbon" or context-browsing interfaces are completely legitimate to use, but never in this grade of application.

The more menus people have to dig through, the more likely that a specific feature will be ignored.
It's exactly the opposite. Unless you're mentioning something sort-of related... but that's a whole different chapter.

None is faster because you are doing it wrong in believing that HCI is just about benchmarking presses. Your "Ribbon" "just works" because it removes contexts blocks. Do you want an example? Where is the "Save" context block? There isn't one as a context block.

The "Ribbon" or context-browsing interfaces are completely legitimate to use, but never in this grade of application.

It's exactly the opposite. Unless you're mentioning something sort-of related... but that's a whole different chapter.

you know there's about 50 miles worth of use cases that proves you wrong. Microsoft put a lot of work into the ribbon, more so they put a lot of testing into it to make sure it was a better, and more efficient way to use Office, and that it actually gave people easier access to all the functions they needed when they needed them, even functions they never knew about. and the save block is in the system/app/file "menu".

When they put out the claim that the ribbon makes all functions faster and more easily accessible and that people find them faster and use hem more and use functions they would otherwise never use, that wasn't empty statements with nothing to back them up. Not being an open source developer with no funds, MS can afford to spend millions on use cases and focus groups to test their new innovations.

and the save block is in the system/app/file "menu".
Which is not a context block.
When they put out the claim that the ribbon makes all functions faster and more easily accessible and that people find them faster and use hem more and use functions they would otherwise never use, that wasn't empty statements with nothing to back them up
They can back up with all the studies and money they want. In the end, given my personal/university/state's experience with Microsoft's focus groups and research I know we will frown on most of what they throw at us.

you know, focus group on a FOSS centered group that goes into the room already expecting to dislike the system, and thusly not even trying it properly. they're not proper focus groups. hence why there are use cases, you've heard of those right ? even though they're something the FOSS community doesn't use, cases it takes time away from the coders to code their UI's. afterall why should you have special people to design UI's and test stuff and do usability when a coders can do all that just as good.... right...

A whole county in Norway is now ditching OOo and going back to MS Office, you know what ? because it'll save them millions. In fact it'll save them more than what they said they would save on switching to OOo years ago. Most of it because of it being faster and better to use, partly because Outlook makes Thunderbird seem like a kids toy, and partly because of support costs. And they're not the only ones.

The "problem" with the Ribbon (and anything else new) is that it still has to be learned. It doesn't just magically make everything better and more efficient with no investment. That's what most of the complaints really boil down to. You need to invest time and money in retraining people who are already proficient in the previous interface. You might see some return in the long run, but there is a need for large immediate investment that can be difficult to defend.

you know, focus group on a FOSS centered group that goes into the room already expecting to dislike the system, and thus not even trying it properly. they're not proper focus groups.
Improper usability design exists in both FLOSS and proprietary development alike.
hence why there are use cases, you've heard of those right? even though they're something the FOSS community doesn't use, cases it takes time away from the coders to code their UI's. afterall why should you have special people to design UI's and test stuff and do usability when a coders can do all that just as good.... right...
They use them... somewhat properly at best, improperly at worst. If you want to name names: Ubuntu. And I'm one of the special ones, but I don't do accessibility assessments anymore.
A whole county in Norway is now ditching OOo and going back to MS Office, you know what ? because it'll save them millions. (...) And they're not the only ones.
A country is a country is a country. Whatever works in your boat may not work in ours. But then again, our studies are commissioned by Microsoft and the officials are bribed by Microsoft.
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop 'Google Chrome' is downloading without you agreeing to it. Fun right? Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!