it is still very well usable - i used TV 2.0 year ago to do some prototype. i wanted (and mostly succeeded) to create turbovision front end for LLDB debugger... you know, that would behave like Borland's Turbo Debugger.

few quick notes:

- blimey it was like it where i left it 199x :) you can even compile/run code from 1993 without major issues.

- there's even a better internal TV editor based on scintilla, so with syntax highlighting and such. although i was trying to mod it without success, i'll have to ask author for help, probably.

- there's no documentation (in the sense of common wisdom), so you can't ask stack overflow or AI. you have to do it like in old days: learn from examples (that have bugs in them ;) and read those few books on turbo vision again and again.

- manual 'layouting' is kinda annoying, some auto layout like qt would be handy

- i miss splitters, but that should not be hard to implement

- tbh i am kinda surprised how small and compact TV really is. it felt ginormous in the 90ies :)

overall - the author did very good job modernizing the library and i love it.

▲

Narishma 4 hours ago | parent [-]

> there's no documentation (in the sense of common wisdom), so you can't ask stack overflow or AI. you have to do it like in old days: learn from examples (that have bugs in them ;) and read those few books on turbo vision again and again.

Not sure what you mean here. Turbo Vision came with extensive high quality documentation. If anything such documentation is what's lacking nowadays.

https://archive.org/details/bitsavers_borlandTurrogrammingGu...

	▲	an hour ago \| parent \| next [-]
		[deleted]
	▲	lepicz 2 hours ago \| parent \| prev [-]
		i mean: for example you have a problem 'how do i create scrollbars two squares wide' (not a real problem, can't think of something now) if you work with qt for example so these days you ask google/stackoverflow/qtforum and you have multitude of responses if it's a common problem and sometimes you have whole solutions ready to copy&paste. when you work with TV and ask google - you usually get... not much. so you have to take the longer route: study the doc/books (you mentioned), study the code, examples... or be friend with the author of this library or those two or three people who actively use this library these days ;) -- edit: btw those books (there's a c++ one as well) you mention are good, but, sadly, no book is detailed enough when you have very specific problem :)