Nice stuff, although we have native libs for many of these,
and I'd personally prefer using those if possible, rather than
reimplementing them in a QT-specific way. It's IMO also better
for Harbour.
But we don't have efficients tools to acces to db2 and Oracle. In
ADO is many bugs.
ADO should be fixed if this is really bothering for users.
It seem though that no one is interested, which to me means,
that no one is using it.
I still hold my opinion that this isn't a QT project in the
first place and we should focus on QT *UI* related stuff
regarding our hbqt contrib lib. It's enough of a challenge
by itself.
QT is too heavy to be used efficiently as simple glue layer
for such databases. I guess DB2 and Oracle both have proper
client libs we could relatively easy interface with, and for
sure in a much lighter way, and - what is the main point -,
without requiring the whole QT system to be also included.
Please remember that QT doesn't support all platforms which
we support in Harbour, so merely using QT as the jumping
board to get all these fancy features isn't a solution for
our project.
QT is huge and there is nothing which should stop any user
to start developing Harbour bindings for any part of it we
don't happen to support in Harbour itself.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour