Dividing the TightDB class into "typed" and "internal" utility classes

[nmihajlovski]

Currently the TightDB class contains many internal utility methods and the "print" method that's used for printing the "typed" tables. The class needs to be divided, to isolate the low-level utilities into separate class.

[bmunkholm]

I will soon add a toString (or whatever it should be called) method on
Table, TableView and Group (it's already in the c++ core). Then we can
remove the Print method.

On Thu, Dec 20, 2012 at 8:11 PM, Nikolche Mihajlovski <
notifications@github.com> wrote:

Currently the TightDB class contains many internal utility methods and the
"print" method that's used for printing the "typed" tables. The class needs
to be divided, to isolate the low-level utilities into separate class.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73.