Benchmark: Memory Usage: LXQt desktop environment vs XFCE

It has always been rumored that Qt is bloated so programs written in Qt should be bloated. Some even argued that the LXDE developers made a wrong decision on the migration to LXQt.
Why not replace the assumptions with some experiments?
In fact, LXQt 0.11 even uses slightly less memory than XFCE (with gtk+ 2). After cold boot, LXQt uses 112 MB in the testing environment. Continue reading “Benchmark: Memory Usage: LXQt desktop environment vs XFCE”

LXPanel 0.8.1 released.

After some bugs gathered and fixed, the bugfix release of LXPanel got its time to happen. So 0.8.1 now. In addition to 17 complete translations in 0.8.0, it now also completely translated to Japanese and Polish languages. The most probably it’s the fisrt and the last in 0.8.x series, time to do some development is around, you can wait for new awesome features, of course.
New release tarball download link:
lxpanel-0.8.1.tar.xz
SHA1: bfaf34b2574b02b9703777904e658ed082cf17dd Continue reading “LXPanel 0.8.1 released.”

Memory Usage of LXQt 0.9

Since the release of LXQt 0.9 several days ago, many people are curious about its memory usage since in the release announcement we mentioned the use of two libraries from KDE framework 5. Don’t worry! They are just “pure Qt libraries” without other KDE dependencies (Thank you KDE guys!). Good engineers always base their design desicions on careful analysis, experiments, and measurements, not politics. If a library works pretty well, it does not really matter where it comes from or it belongs to which camp. If it’s free software and it’s suitable for our need, I’d say “use it”. Here are some numbers of memory usage after cold boot. Continue reading “Memory Usage of LXQt 0.9”

LXPanel 0.8.0 released.

As already was announced, the time to release next LXPanel has came. The release goals for 0.8 were:

  • complete multi-monitor support
  • improve and further simplify plugins API

It also happen to have better performance than before, that was a side effect of optimizations. The release 0.8.0 comes fully translated to 17 languages: Chinese (China), Dutch, Finnish, French, Galician, Ganda, German, Greek, Icelandic, Indonesian, Italian, Portuguese, Russian, Spanish, Swedish, Turkish, Ukrainian. As usual, a lot of bugs were fixed, and you are welcome to report any bugs you happen to find yet. Work on LXPanel features will be continued shortly, stay in touch, it will become yet more convenient later. 🙂
New release tarball download link:
lxpanel-0.8.0.tar.xz – SHA1: c0b2d9edfd0d95ee142db7cd0e55763a785daa0a Continue reading “LXPanel 0.8.0 released.”

LXPanel 0.8.0 pre release testing.

After some development, it’s time to release next feature version of LXPanel. The release goals for 0.8 were:

  • complete multi-monitor support
  • improve and further simplify plugins API

Now that it was done, and numerous bugs fixed along with that, LXPanel has come to release time, which is scheduled in about 2 weeks. We would appreciate all the testing and feedback on it. The fresh sources are in GIT repository, as usual. The changelog since version 0.7.2 is big enough, you can find it in the sources or read online.

I also would like to ask all our translators to come into Pootle and translate it. I would ask to read the Wiki if you didn’t do that lately. Thank you in advance, everyone.

In memory of Razor-qt

Although people often compare LXDE and the “so-called” Qt port, LXQt with each other, they are actually from different code bases.
The most parts of LXQt are actually built on top of razor-qt, a lightweight Qt-based DE with the same philosophy as LXDE. We reorganized the source code of razor-qt and removed unused pieces. Then we ported several LXDE components to Qt and also developed some new ones. Hence it’s more the merge of developers than the merge of the actual source code. That’s why they have slightly different feature sets. Without the work of razor-qt project, we can’t have LXQt now.  Its developers deserved the credit. Since the story is too long for the tiny “About” dialog, I wrote the blog post here to thank their contributions.
Long live free software!