Comment Re:kylix kind of sucks (Score 0) 443
1. kylix was using winelib
Yes, the first time I started Kylix, my reaction was
Ughh. Software ported using winelib are ugly, they tend to flicker, and don't respect window managers. I couldn't get anything done, because some Kylix window always wanted to move on top when I moused over. So the Kylix IDE was pretty unusable. And don't tell I should use such or such WM!
2. Software was compiled using its own qt library. The widgets didn't look well and didn't match those of the rest of Qt apps.
3. Kylix used THREE different toolkits:
a. Winelib for the IDE
b. Qt for the compiled apps and some dialogs in the IDE
c. Motif for the Help browser
Kylix may be great tool (especially the compiler itself), but the whole package looks very amateurish.
BTW I use Eclipse.
Yes, the first time I started Kylix, my reaction was
Ughh. Software ported using winelib are ugly, they tend to flicker, and don't respect window managers. I couldn't get anything done, because some Kylix window always wanted to move on top when I moused over. So the Kylix IDE was pretty unusable. And don't tell I should use such or such WM!
2. Software was compiled using its own qt library. The widgets didn't look well and didn't match those of the rest of Qt apps.
3. Kylix used THREE different toolkits:
a. Winelib for the IDE
b. Qt for the compiled apps and some dialogs in the IDE
c. Motif for the Help browser
Kylix may be great tool (especially the compiler itself), but the whole package looks very amateurish.
BTW I use Eclipse.
