The SemWare Editor

The SemWare Editor (TSE) is a text editor computer program for MS-DOS, OS/2, and Windows.

Starting in November 1985 as a shareware program called Qedit. Qedit was later modified to run as a Terminate and Stay Resident (TSR) program, and ported to OS/2^[1] and eventually evolved (via rewrite) to TSE. TSE was eventually ported to Windows.

TSE supports a Pascal-based macro language (SemWare Application Language or SAL), regular expression search and replace, keystroke recording and playback, full undo and redo, shortcut key assignment (both as configuration and on the fly) that allow extensive modification of the functionality of the text editor, and other features. Like its predecessor Qedit, TSE is used by programmers^[2] and others.

There are two online support discussion groups that include long time accomplished users and the developer, Sammy Mitchell of SemWare Corporation.

SemWare Corporation is based in Kennesaw, Georgia.

SemWare started as shareware, but became commercial software.

Qedit

Qedit was a versatile MS-DOS text editor requiring 50 KB of memory;^[3] fast I/O, search, and responsive; and a text-based macro language. Qedit implemented its engine and much of its application functionality in native code, with a small percentage of functionality implemented via the macro language, unlike Brief, Epsilon and other popular programmer editors of the time which implemented a native engine or core, with the bulk of the program implemented via their scripting languages.

Qedit stores all of the files being edited in RAM. Later versions of Qedit added support for the various systems of memory supported by MS-DOS: expanded memory (EMS), extended memory (XMS) and virtual memory, up to a maximum of 16MB.

Qedit was originally written in Pascal using the Borland Turbo Pascal compiler, and later converted to C and compiled with the Borland Turbo C compiler.

QEdit and TSEJr for OS/2

Qedit was ported to OS/2 initially as a 16-bit application for Microsoft's OS/2 1.x. This 16-bit OS/2 version of Qedit had version 1.x. Version 1.50 for 16-bit OS/2 is dated February 1990.^[4] By that date the "read me" file included with the software claimed "90,000 licensed users of QEdit products, worldwide" -all platforms-.

After IBM and Microsoft parted ways, IBM released a 32-bit version of OS/2 v2.0 in March 1992. Semware ported Qedit for 32-bit OS/2 with the release of Qedit Pro 3.0 for OS/2 on February, 1994 which sold for $99. Version 3.0 included multi-file operation, HPFS support and access to the OS/2 Clipboard. SemWare claimed "over 120,000 licensed users" on all platforms at that time.^[5]

The last version released for OS/2 was "TSE Junior/2" v4.00e released on February, 1997.^[6] It was functionally equivalent to TSE Junior v4.00e for DOS with the addition of access to OS/2's system-wide clipboard and HPFS (long filenames) support. It retailed at the time for $99 and was supplied with a copy of the DOS basic version.^[7]

The SemWare Editor (TSE)

Qedit was rewritten and significantly expanded, and eventually released as The SemWare Editor (TSE) 1.0. The initial release maintained the tradition of fast I/O and response, fast search, a simple text scripting language and the fundamental design of a native core with functionality split between native code and scripting.^[8]

New TSE features included a more powerful scripting language (SAL), regular expressions, a native Win32 port, SAL access to Win32 DLL entry points, a 'graphical' port using the native Windows GDI (previous versions employed the console window), optional native dialogs (e.g. Open), and graphical features such as window transparency.

TSE has at times been referred to as 'Tessie', derived from its acronym (TSE).

TSE used the codename 'RoadRunner' during initial development, until it was formally named TSE. Comments from its author, Sammy Mitchell, indicate the name change was forced due to a trademark dispute raised by another business.^[9]

User interface

Earlier versions of TSE operated in the console window in text-only mode with limited character sets and colors. Version 2.6 added a native Win32 port, but was still character-based (using the Win32 Console APIs). Version 4.0 included the Win32 application rewritten as a pixel-based graphical application (g32.exe) using the GDI. This is commonly misunderstood to be a console application, as it still appears textual despite being a native Win32 graphical application. Visually, g32 appears to work in lines and columns, though it is a graphical application (via WinMain and GDI APIs, not the Console API).

This text-like behavior simplified porting existing scripts and provided a common user experience; there was no attempt to rewrite it as a truly graphical, pixel-based application with multiple windows, MDI, fractional lines/columns and so forth.

The transition to a 'graphical' implementation brought several advantages by being a graphical application not tied to a Windows 'console', including a broader selection of fonts, native dialogs for Open, Save and Print (the text-mode prompts remain available via configuration option) and window resizing.

Qedit and TSE supported various screen modes (different numbers of columns and rows, e.g., 80 × 25) based on the underlying video display options; with the graphical version windows could be sized to any number of rows and columns. This occurred around the same time larger displays were becoming increasingly common.

SemWare Application Language

The SemWare Application Language (SAL) uses a Pascal-like notation supporting procedural functions and procedures, local and global variables, constants, a preprocessor including common #include and #ifdef keywords, iterative and recursive control structures, and many text-editing-specific functions.

For example:

proc Main()
integer I
for I = 1 TO 3
Warn( "hello world ", I )
endfor
end

Data types

SAL supports integer and string data types.

An integer in SAL is a 32-bit base-2 signed integral numeric; a string is a (declared) fixed-size array of characters, with a maximum definable length of 255 characters.

SAL APIs support creation of arbitrary buffers, including non-interactive buffers not visible to the user. Many functions are available to access and manipulate buffers and their contents, effectively acting as very large text containers.

Timeline

See also

• Comparison of text editors

References

External links

• Official website