The Semware Editor

Possible Future Projects

In no particular order


This is a possible future project.

I have come to find Sammy's TSE English syntax hiliting file a delight for catching spelling errors in .txt files.

I now would love to have a TSE extension with these additional features:

  • A cleaned-up syntax hiliting file to start from.
    The current file is pleasantly complete, but also contains a lot of weird words.
  • Better hiliting of numbers and punctuation marks.
  • An easy way to add a not-yet-hilited word from a text to the syntax hiliting.
  • A way to also apply English hiliting to comments in programming languages.
    Mixed syntax hiliting will be a hard problem, which might require a separate future project and extension.

Integrated SSH based file browsing

This is a possible future project.

The idea is to give TSE integrated SSH based file browsing.

Ideally it should allow TSE to open and save remote files using TSE's existing user interface.

Such remote files should appear in TSE's File Open history.

Logging in should work both Pageant-based and password-based. Pageant is a tool that requires one master-password for itself, and can then be set up to log in to many SSH-enabled servers with a secure key exchange instead of a plain password.

Under the hood the future tool or extension is going to use an existing external SSH interface/tool.

In the demo/test macro EditRemote I experimented with how a TSE extension could use TSE's own Edit(This)File commands to open remote files that use the HTTP protocol. The same base principle should apply to the SSH protocol.

For comparison, a tool like WinSCP first copies a file to a local directory, that local directory is created with a new name each time, which results in TSE not getting to see a consistent file name each time the file is opened, and the file not being available in TSE's file history.


This is a possible future project.

Syntax highlight the View Finds list.

A TSE extension should be able to do this. The biggest hurdle would be multi-line comments. Which is unfortunate, because hiliting comments and not-comments as such would also be the extension's greatest benefit!


This is a possible future project.

I needed and created a quick & dirty version of a tool that can convert a base64-encoded text to readable text.

It "works", but is currently so user-unfriendly, that I do not consider it publishable. To do.


This is a possible future project.

Linux TSE and Windows GUI TSE gave us the ANSI character set, which gained us language compatipilty between at least 14 languages, but lost us line drawing capability.

Unicode supports line drawing, and the Unicode and Uniview extensions give TSE Unicode compatibility, but there is no tool yet that uses the Unicode character set for line drawing.

UniDraw could be that tool.


This is a possible future project.

Copying and pasting Unicode text from and to the Windows clipboard is already possible with the Unicode extension. However, this functionality needs its own extension, provisionally called UniWinClip or UniClip. The main reason is that the Unicode extension is currently too big for debugging.

A secondary goal would be to add the capability to paste the Windows clipboard as a column block. There are two known ways to do this. One is by giving the tool a parameter to do so. The other is by doing a column block paste from the Windows clipboard if the text contains a marked column block, because this is what Visual Studio and VSCode do. The second way might need to be optional.

A tertiary goal would be to reproduce TSE's capability to reliably copy column blocks between TSE sessions.

UniView v2

This is a possible future project.

Two major improvements might be possible:

  • It might be possible to get rid of UniView's flickering line updates by using TSE's HookDisplay() command.
  • It should mostly be possible to make UniView work for the current line too.
    However, this implies taking over the backspace, delete, tab and horizontal cursor keys to compensate for one displayed Unicode character being implemented by multiple underlying bytes.
    I am not going to implement the tab key at first, and maybe not at all. It will be really hard to implement given all its configuration options and macro implementations.

These two improvements would again bring TSE major steps closer to being a full Unicode editor.

I do not plan to solve these issues:

  • Misaligned tab positions after a non-ANSI character.
  • A column block that only partially contains a non-ANSI character.
  • Sorting on non-ANSI characters.

UniCode Suite

This is a possible future project.

There already is a group of separately distributed extensions to make TSE more compatible with Unicode.

It would be nice to be able to distribute these as a coherent bundle.

(I have renamed the "Edit2" tool to "UniBrowse" in anticipation of this project.)


This is a possible future project.

In creating the Uniview extension I noticed how the parameters of the Windows TextOut API might be used to implement smooth scrolling in TSE.

One day I would like to try if this works, just for the fun of it.

These webpages are created and maintained with The SemWare Editor Professional