From: Andrej N. G. <an...@re...> - 2013-04-24 13:55:40
|
Hello! Abdurrahman AVCI has written on Tuesday, 23 April, at 13:39: >23 Nisan 2013 Salı 10:44:52 UTC tarihinde Andriy G yazdı: >> Well, that shouldn't be too big problem. I believe it shouldn't take >> too much efforts to support both GTK2 and Qt versions to honor GTK2 users. >> Why I don't talk about GTK3? Many of you know GTK3 is a lot more buggy >> and resourse consuming. And less of you know about another GTK3 problem: >> they tend to change APIs too much and too fast. For example, last night I >> did researches to implement some new plugin into libfm-gtk. And what I >> see? Let's say, class GtkVBox. In GTK 3.0 they've marked it deprecated >> and suggested to use newly created GtkBox. In GTK 3.2 they've created new >> GtkGrid class and in 3.4 they've deprecated GtkBox as well telling to use >> GtkGrid. What will be next? They deprecate GtkGrid in a year or too? So >> who knows if applications designed for GTK 3.0 can be even compiled in >> mere year or two without lots of workarounds and conditionals? I wouldn't >> be so sure. But what about Qt, BTW, is its API somewhat stable? At least >> I strongly want libfm to be compatible with libraries of year 2010 - it's >> glib 2.22 for example. The Qt was 4.5.4 at that time. Is it possible or >> hard to have things compatible with both Qt 4.5.4 and with latest one? >Qt doesn't break API or ABI compatility within the lifetime of a major >release. >So, conceptually if you have a program that compiled with Qt 4.0 (circa >2005), >it should compile fine with Qt 4.8.4, the latest Qt4 release. Only new >stuff >added during minor releases, nothing removed or broken. >In fact Qt5 doesn't break the API much either, so you can have an >application >that compiles with Qt4 and Qt5 with minimal ifdefs. Thank you very much for clarification. That's great thing for the development and application life. >> >Instead of having two incomplete DEs, at least we can have a really good >> one. >> Exactly my thoughts. :) So what do we have now? I would like to hear from razor-qt guys what they think about the idea to merge our efforts and teams to make LXDE and razor-qt camps the one. I mean LXDE and razor-qt to be similar things but just based on different toolkits - GTK2 for LXDE and Qt for razor-qt. This way the razor guys will affect quality of GTK2 versions and lxde guys will give Qt versions of missing parts (file manager for example). As I said a bit earlier, two teams together is definitely more than just sum of two and you all know that. With the best wishes. Andriy. |