> A compiler without a GUI Framework leads it to nitche apps: Servers, console > and cgi apps. > A GUI Framework without compiler leads it to death because lack of support. > If you do that then no new users will come here. > Vanity is not a good advisor.
Calling it "vanity" when it doesn't serve your short-term purpose, but welcoming it when it produces a good quality product doesn't give too much to this topic. And I'm certainly not interested in going personal. We can agree that GUI is generally a good thing, without going into deeper analysis. Nothing tells though that the GUI needs to reside in the same physical repository, nor does anything tells, that core developers have to deal with it, too. Also nothing tells, that only one GUI should exist for one base system. Looking around the compiler "market", I can't see similar compilers which have an integrated, built-in, selected GUI as part of core. Of course also nothing tells that Harbour can't have one core quality GUI that comes with it automatically while allowing also other options. And if you remember the discussions from the beginning, and seeing the amount of care from my side f.e., you could see that no so secretly I believed that HBQT could have become this selected GUI for Harbour. But, such selected GUI should be of core quality. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
