Originally posted by kraftman
View Post
Announcement
Collapse
No announcement yet.
Fedora 11 Preview
Collapse
X
-
Originally posted by hax0r View PostYes, there is, it's called programming and reading code & manual.
So you can see my point why most of KDE apps have more features than their GNOME equivalent. If developer spent time on implementing features instead of reading manual how to draw a button in a window, GTK programs would be more like Qt programs - with more features.
Comment
-
Originally posted by DoDoENT View PostIs there any GTK support for C++? But I mean 'real' support, not just using GTK's C functions from C++. Is there any visual designer tool for GTK applications as there is for Qt? But not GLADE, because it creates some weird xml file which has to be parsed every time window is drawn. That's slow.
I don't know where you got the silly idea that Glade is slow, It's not.
Originally posted by DoDoENT View PostIs there any 'real' visual designer tool for GTK apps, which will generate C/C++ drawing code?
Comment
-
Originally posted by monraaf View PostI don't know where you got the silly idea that Glade is slow, It's not.
I didn't say that Glade programs are slow, but just that they could be faster, if they wouldn't parse XML window drawing instruction every time.
Comment
-
Originally posted by monraaf View PostI haven't delved into the internals of Glade, but AFAIK the XML parsing only happens on window creation, once you got your UI setup there isn't much XML parsing going on.
Or imagine an application which has big windows with a lot of components (wizard maybe, or something like KDE control center).
In such applications window creation time may differ significantly if parsing XML or just drawing from code.
Comment
-
Originally posted by hax0r View PostYeah I'm a troll, I'm speaking facts. KDE and GNOME has basically same features, but other DE like XFCE have little less. 1.85x memory usage is a fact, I took caching and buffers out of the consideration. List me some good QT apps except vlc.
I need to check, but as far as I know Gtk* uses stupid pixmap handling.Last edited by kraftman; 01 May 2009, 02:34 PM.
Comment
-
Originally posted by DoDoENT View PostTrue. Imagine an application with a lot of windows which are created and destroyed a lot.
Or imagine an application which has big windows with a lot of components (wizard maybe, or something like KDE control center).
In such applications window creation time may differ significantly if parsing XML or just drawing from code.
Just imagine a huge configuration file with 1000 of options, it will take _ages_ to get loaded at runtime!
On a more serious side, it's really just open the file and read what widgets to use, the most time is spent on actually CREATING the widgets anyways
Comment
-
Originally posted by kraftman View PostGnome doesn't have many KDE 4 features (or maybe I should say Gnome apps doesn't have many KDE apps features). About memory I already said why its usage seems higher on KDE. XFCE in example uses much less memory then Gnome. Think about this. If you weren't trolling give me names of Gnome applications which has same or more features as those: Amarok, Kate, Krusader, Konqueror, KMail, K3b, Gwenview, Okular, Okteta, SMPlayer. What's name of plasma equivalent in Gnome (in current version)? It seems you don't have idea what are you talking about.
I need to check, but as far as I know Gtk* uses stupid pixmap handling.
Don't know Kate. I haven't used Krusader a lot because as I said, all my experiences with KDE ended up with trying to do something and things taking quite bloody long, which sort of takes the fun out of it. I'd say Nautilus / Thunar in that respect are much superior (especially the later, does exactly what it needs to do, nothing more, nothing less).
I do realise Webkit which is a great engine is based on KHTML, so kudos there to the KDE developers. Konqueror itself was ever slow in every test I did. I'd take Firefox over it every day or any console browser. But I do plan to switch over to Midori once it leaves alpha status (oh, the irony - it uses Webkit).
I can't be inclined to delve into every last application you mentioned, but one that indeed springs to mind positively as one of the best media players I've ever encountered is SMPlayer. It's really great, my only fault is that I try to avoid toolkit-based interfaces so using mplayer is more attractive for me. Otherwise I'd use it without thinking twice, willing even to sacrifice my wish to keep my box clean of qt-bloat.
But my post boils down to what I've already said. KDE is not essentially bad, it's just _slow_ and it bugs the crap out of me. I get more or less the same functionality without paying with so much juice for it.
At the end, cuique suum, wasn't it?
Comment
-
Originally posted by NeoBrain View PostAnd what about config files?
Just imagine a huge configuration file with 1000 of options, it will take _ages_ to get loaded at runtime!
On a more serious side, it's really just open the file and read what widgets to use, the most time is spent on actually CREATING the widgets anyways
Comment
Comment