Originally posted by JS987
View Post
Announcement
Collapse
No announcement yet.
LXDE Desktop Being Ported To Qt
Collapse
X
-
-
Originally posted by oleid View PostAlso, there is a better binding support for GTK compared to Qt, simply because not every language supports the usage C++ libraries - this is true for e.g. Haskell. While there _are_ haskell bindings for Qt, they can't be considered usable.
Originally posted by dee. View PostSo what would you do to EFL, WxWidgets, Motif, SDL, Clutter and the rest? How exactly would it benefit anything to have less choice of toolkits? How would it "defragment" anything, and how would it ease app development? App developers can already choose whatever toolkit they want, you'd want them to have less choice - how'd that make anything easier?
Originally posted by Awesomeness View PostNo, both teams cooperate.
The chance of both projects merging is high.
Comment
-
Originally posted by TheCycoONE View PostYes but most of the rest of the basic multilingual plane is shorter or equivalent length in UTF-16, and encoding/decoding is much simpler which could make for faster string operations. Also Qt is cross platform, and Windows e.g. standardizes on UTF-16 - to have portable programs they would have to deviate from one or the other. Actually I think almost everyone/everything uses UTF-16 or UCS-32 for in memory representations of unicode strings (though I may be wrong), they're just so much easier to work with.
Comment
-
Originally posted by JS987 View PostUTF-8 is 50% longer than UTF-16 for some Asian text, but UTF-16 is 100% longer than UTF-8 for ASCII which is worse. String class should support both: UTF-8 and UTF-16. Glib/GTK is using UTF-8 for strings.
Comment
-
Originally posted by carewolf View PostA classic C byte string in Qt is represented with a QByteArray it has all the same methods as QString it just works on single chars.
Comment
-
Qt = the end of lightweight
I had LXDE running on a machine until about 2 weeks ago when an automatic update (lubuntu) broke it in a really weird way
and I just didn't have the patience to debug it. I switched the computer to XFCE and I am even happier I've done it now that I read that LXDE is going Qt.
I have never seen ANYTHING lightweight done in Qt. Like, zero lightweight things in QT. Qt is the fattest pig out there.
I would love to see more attention given to EFL. That's what I call lightweight! If any of you Qt preachers want to see the real meaning
of the words light and fast, install bodhi linux and marvel at what Qt will never get close enough to even to see the heels of with the hubble telescope.
It's sad to see the linux world being crushed under the infinite lards of Qt the fatso king.
Comment
-
Originally posted by 0xBADCODE View PostThey should rename it. Because.. because Qt is cool, featured and so on. However, Qt is anything but lightweight. In fact it's quite a huge stockpile of libs and Qt programs usually tend to be memory hungry and quite slow. And C++ allows programs to get bloated really quickly.
Comment
-
Originally posted by JS987 View PostOriginally posted by TheCycoONE View PostYes but most of the rest of the basic multilingual plane is shorter or equivalent length in UTF-16, and encoding/decoding is much simpler which could make for faster string operations. Also Qt is cross platform, and Windows e.g. standardizes on UTF-16 - to have portable programs they would have to deviate from one or the other. Actually I think almost everyone/everything uses UTF-16 or UCS-32 for in memory representations of unicode strings (though I may be wrong), they're just so much easier to work with.
Comment
-
Originally posted by dvanzo View PostAnybody knows why text menu (first level) is in that language??????
Notice, that one entry in the menu on the right is also in "that language" (Chinese?).
Comment
Comment