>> hbpqtui is a QT specific class, and while I understand >> the feature is useful, such class should reside in HBQT, >> not HBXBP, since it's not, or not easily portable functionality. >> Just think about the case if we'd like to create an HBXBP >> compatible library, but based on a different GUI subsystem >> (GTK, WX, whatever). >> > > It is scheduled to be compatible with Xbp framework. > That is why I put it there. As I am only concerned with Qt > at this moment I have decided it to be put under there only. > Many more clsses are under pipeline as discussed earlier > and I do not care what sub-sytems come in the future. > So far nobody has even thought of them.
"I don't care"? Great answer, so I don't care about HBQT + HBXBP + HBIDE either. That will free a lot of valuable time to spend on better things. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
