Hi Pritpal,
First - a good news - I am been able to simulate
TBrowse() behavior as far as vertical navigation is concerned.
Horizontal navigation - freeze - is practically non-existent in Qt's
model/view architect and hence so far I have no clues how
to simulate this. Barring "FREEZE" and "FOOTER" everything is working
properly. Important to note is that there is no absolutely no
memory overhead as is associated with Qt's model/view architect
and so is extremely fast rendering has been achieved.
TBrowse.prg has provided me the architect. It could been
possible with <::aCellValues> which Przemek thought of and
I could exploit it to the maximum. Without <::aCellValues> construct
this would have been impossible to achieve this milestone.
Sound very good.
TBrowse() code is then been modified to XbpBrowse() behavior.
So far so good.
Second - as I am in a position to provide both TBrowse() and
XbpBrowse()
approaches, what do you think if I retain both or only XbpBrowse().
Internally, TBrowse() will map itself to XbpBrowse().
A QT-based TBrowse() is very nice, but doesn't have much to do
with XBP lib functionality per se, unless Xbase++ has similar
GUI version of TBrowse() (I don't think so). Since you say this
QT based TBrowse() is built on top of XBP stuff, it's certainly
not very practical to move it to a separate lib.
All this considered I'd put it to hbxbp lib, as a simple Harbour
extension, and with a different class name, f.e.: xbp_TBrowse().
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
