Enable building turbo as a library

[unxed]

It would be very useful to allow turbo to be built as a library. This would make it possible to embed the turbo into a larger application, similar to how SETEDIT is compiled as a library when used within RHIDE. By providing a library build option, developers could reuse and extend Turbo's core functionality without having to fork or rewrite it.

This modularization would:

• Support the creation of IDEs or developer tools using turbo as a base.
• Facilitate reuse of turbo's well-tested UI and file-handling code in other Turbo Vision apps.

Would need:

• A libturbo target or similar in the build system.
• Clear interface boundaries (public API) for embedding.

[magiblot]

Hi @unxed!

Yes, Turbo can already be built as a library. TMBASIC is an example of a third-party application relying on Turbo. The Turbo project itself also contains a few very simple sample applications which demonstrate how to use Turbo as a library.

However, I do believe Turbo's public API is far from being up to the expectations because 1) it has notable design flaws, 2) it exposes Turbo's reliance on Scintilla publicly, and 3) it is missing important features.

The problem is that I'm not in the position to spend enough time on Turbo so as to solve all of these points...