Mr Rao,
I would prefer having different components to solve different problems. It is the S in the SOLID principles: single concern for every component.
The high degree of coupling among classes makes them very sensitive to changes, and not usable for data sources that are not provided. I would like to see visual component using an data agnostic, well defined interface, so everyone is able to used them.
TGet is a great class: It knows nothing about where the data comes from. The original Clipper's TBrowse showed a good way of data interface. It doesnt knows how to move throw records, nor how to retrieve column data, so TBrowse is usable for anything.
How bright original Clipper's authors were! They brought things like codeblocks, that currently become part of most modern languages, knows as closures or anonymous functions. And they did it at the very beggining of the birth of modern programming. I'm currently in a TypeScript/JS course, and can see many concepts introduced as "marvels" ... when we have had them for decades
If CA wouldn't kill it, the world will be running on Harbour's wheels today.
KR,