Originally posted by Honton
View Post
Announcement
Collapse
No announcement yet.
GNOME's GTK+ 3.10 Irons Out HiDPI, Wayland Support
Collapse
X
-
Originally posted by Honton View PostI read your posts. It is not fair to ask me for complete documentation. Sure Gnome is doing a lot more on Wayland than this. You can go look it up either at wiki.gnome.org or at bugzilla.gnome.org. I kept things quite simple you know. I only asked for examples that could match Gnomes work on essential support for HiDPI and CM.
So no one have given any examples of any one matching Gnomes work. Still Gnome can not be calling a leading consumer Wow great reasoning!!!
Comment
-
Originally posted by Honton View PostYou are still hiding behind the words. Well I don't care. You will be keep hiding behind semantics, Gnome will keep developing Wayland, and KDE will keep falling behind. And that is what really bothers you.
Comment
-
Originally posted by Honton View PostThere is a huge difference to tje approach. Kwin will bend the intentions of the Wayland protocol. Gnome works upstream on both wayland and weston. That is the difference between wrong and right. And wait a year or two, then KDE will end using all of Gnome's upstream work for desktop use. Qt's wayland support doesn't cover what desktop needs but what a phone needs. Oh and when KDE gets there, they will probaly complain about Gnome's work and demand Gnome includes disasters like the KDE indexing framework
Haha. KDE being ignored is self inflicted. Look at the way they handle wayland. Kwins deviation is a sick joke. Why would anyone want to copy that? And Qt taking over because a few apps ports and LXDE merges with Razor? Haha. Whats next? MIR taking over because Xubuntu might use it?
Nearly all new apps use Qt, the Qt wayland supports everything what an application needs not what a desktop needs.
Why its KWin way a joke? The just use the specs, as the run KWin as system compositor the could only improve libwayland or the wayland spec.
I have nothing against GNOME but the attidude to add their libs to every cross-desktop project is anoying.
Comment
-
Originally posted by Honton View PostAs stated earlier and also to be read from the very article you are commenting:
Gnome did the COLOR MANAGEMENT FRAMEWORK FOR WESTON
Provide your documentation or keep quite.
Comment
-
Originally posted by Honton View PostYou are still hiding behind the words. Well I don't care. You will be keep hiding behind semantics, Gnome will keep developing Wayland, and KDE will keep falling behind. And that is what really bothers you.
Comment
-
Originally posted by Honton View PostWell. Fact is I have given a few examples of Gnome working upstream at wayland and weston. No one have shown KDE doing that. Still people complain about KDE is getting ignored. Maybe KDE should start working upstream instead of claiming Qt will save us all. Qt is for tool kits what MIR is for display protocols.
Why should Qt should by the Mir for tool kits? It is more than GTK and more multi plattform friendly.
Comment
-
Originally posted by Honton View PostWell. Fact is I have given a few examples of Gnome working upstream at wayland and weston.
Comment
-
Originally posted by Honton View PostQt and MIR share the same disease. Contributor agreement and one-company control. They don't function like normal open source libraries but more like commercial business. Always looking for marketshare. Dishonesty and defamation of others is a part of the strategy.
At least Qt is being (and wants to be) used by multiple projects. Mir is (and only wants to be) used by Canonical on Ubuntu, except for some really curious people (who I have nothing against) that want to see if they can get it to work on (for instance) ArchLinux.Last edited by Nobu; 10 August 2013, 09:58 PM.
Comment
Comment