Skip to content

Rich text

Xavier Michelon edited this page Jul 19, 2020 · 1 revision

Beeftext v8.0 will drop support for rich text.

v6.x and v7.x of Beeftext have basic support for rich text combos (i.e. combos containing text with custom fonts and colors, hyperlinks, etc...). Starting with v8.0, Beeftext will not support rich text anymore. Emojis are considered plain text, so they will still be supported.

Motivation.

The main goal of Beeftext is to work with 99% of the applications. The rich text feature is provided by the Qt framework. It works perfectly fine for Qt applications, and can be converted to HTML. However, ensuring that the result looks as expected in every application is extremely difficult.

Beeftext is the work of a single developer working on it on his free time, and I (Xavier Michelon) only have a few hours per week available for Beeftext. The amount of time required to deal with issues related to rich text is now impacting development to a point where there has been no new feature in more than 6 months.

As a consequence, I have decided to drop support for rich text. This decision will lead to the availability of new exciting features: server-less synchronization across multiple computers, insertion of keystrokes such as Tab or Enter, and more.

Transition.

If you have at least one rich text combo in you library:

  • Beeftext v7.2 will display a message informing you of the change.
  • Beeftext v8.0 will offer you the following options:
    • Convert your rich text combos to plain text.
    • Delete them.
    • Exit the application. This option will give you the opportunity to revert to v7.2.

What to do if you absolutely need rich text.

  • Keep Beeftext v7 and disable automatic updates.
  • Switch to a professional product from a software company that has enough resources to correctly support rich text, such as Phrase Express and TextExpander.