Est. 1993 Beginner

NeoBook

A visual, code-light authoring tool from NeoSoft for building standalone Windows applications, electronic publications, kiosks, and multimedia presentations without traditional programming.

Created by NeoSoft Corp.

Paradigm Visual, event-driven authoring with an integrated action/scripting command language
Typing Dynamic, weak (variables are essentially string-based)
First Appeared 1993
Latest Version NeoBook 5.8.7 (final NeoSoft release); continued as VisualNEO for Windows under SinLios (2018–present)

NeoBook is a visual authoring tool from NeoSoft Corp. for building standalone applications, electronic publications, kiosks, and multimedia presentations on Windows (and originally MS-DOS) — without writing conventional code. Rather than a general-purpose programming language with a compiler and a syntax to master, NeoBook is a page-based, drag-and-drop environment in which authors place buttons, text, images, and media on “pages” and attach behavior through a built-in action command language. Its entire design goal is to put the ability to build distributable software in the hands of beginners and non-programmers.

NeoBook belongs to the family of 1990s multimedia authoring environments — conceptual neighbors of HyperCard, Asymetrix ToolBook, and Macromedia Authorware — but with a distinctive emphasis on producing small, self-contained executables that could be freely distributed.

History & Origins

NeoBook first appeared in the early 1990s as an MS-DOS product. NeoSoft Corp., the same small US software house behind the companion paint program NeoPaint (whose first version dates to 1992), published NeoBook as a shareware tool for “electronic publishing”: assembling text, graphics, and menus into a single program that anyone could run and pass along. The earliest surviving releases carry copyright dates beginning around 1993, and by 1994 interactive CD-ROM content built with NeoBook was shipping on the cover discs of PC Gamer magazine — an early, visible demonstration of what the tool was for.

The DOS line matured through NeoBook Pro 2.x (for example version 2.1f, distributed widely in the mid-1990s). With version 3, released around 1997, NeoSoft rebuilt NeoBook as a 32-bit Windows application, following its users from DOS onto the Windows desktop. The product continued to evolve through the NeoBook 5 generation in the 2000s — marketed variously as NeoBook Rapid Application Builder and NeoBook Professional Multimedia — ultimately reaching version 5.8.7.

In 2018, NeoSoft reached an agreement with SinLios Soluciones Digitales S.L. of Spain to take over development, sales, and marketing of the NeoBook, NeoPaint, and NeoAppBuilder product lines. SinLios rebranded NeoBook as VisualNEO for Windows, under which the engine continues to be developed and sold today.

A note on dates: NeoBook’s exact first-release year is not firmly documented. The earliest releases carry copyright dates from around 1993, and the tool was clearly in use by 1994, so it is best described as an early-1990s product. The metadata sometimes cited as “1997” corresponds to the first Windows edition (NeoBook 3), not the original DOS release.

Design Philosophy

NeoBook’s guiding idea is authoring, not programming. Everything about it is organized to lower the barrier between an idea and a runnable, distributable program:

  • Visual and page-based. A NeoBook publication is a stack of pages. Authors lay out objects — buttons, text fields, images, media players — directly on a page in a WYSIWYG designer, much like a desktop-publishing or slide tool.
  • Behavior through actions, not source files. Instead of writing a program in a text editor, an author attaches action commands to objects and events (“when this button is clicked, do these things”). The action language reads as plain, keyword-led instructions rather than dense code.
  • Self-contained output. A finished publication compiles into a single standalone executable that needs no runtime install and no separate interpreter, making it trivial to hand someone a working program on a disc or download.
  • For non-programmers first. The whole environment is pitched at hobbyists, educators, marketers, and small businesses — people who want to ship an interactive CD, an e-book, a kiosk, or a small utility without becoming software engineers.

Key Features

Visual page designer

The core of NeoBook is its layout canvas. Authors drag objects onto pages, set their properties, and arrange navigation between pages. The model is closer to building a slideshow or a desktop-published document than to editing a codebase.

Action command language

Logic in NeoBook is expressed as action commands — a scripting layer made of readable, keyword-led statements attached to events such as button clicks, page entry, or timers. Commands cover navigation, variables, file and clipboard operations, math and string handling, conditional logic, and external program control. Variables are referenced by name (conventionally wrapped in brackets) and are essentially string/text values, dynamically and weakly typed — a deliberate simplification for non-programmers. A simple action might display a message and move to another page:

AlertBox "Welcome" "Hello, World!"
GotoPage "MainMenu"

(Exact command names and syntax vary across NeoBook versions; the above is illustrative of the action style rather than a guaranteed-runnable script.)

Multimedia support

NeoBook was built for multimedia: importing and displaying graphics, playing audio and video, and managing transitions and effects between pages. This is what made it attractive for CD-ROM titles, kiosks, and presentations in an era when bundling media into an easy-to-run package was genuinely hard.

Standalone executable output

A signature feature is compilation to a standalone Windows (originally DOS) EXE. The author’s pages, media, and actions are packaged into one distributable program, which is a large part of why NeoBook was so widely used for shareware front-ends and cover-disc menus.

Plugins and extensibility

Later Windows versions supported plugins (NeoBook’s .nbp plugin modules and publication source files), letting third parties and power users extend the action vocabulary — for example with additional file formats, database access, or system integration — without changing the core tool.

Evolution

NeoBook’s history tracks the broader migration of personal computing:

EraEditionPlatformNotes
Early–mid 1990sNeoBook / NeoBook Pro 1.x–2.xMS-DOSShareware e-publishing; cover-disc menus
~1997 onwardNeoBook 332-bit WindowsFirst Windows edition
2000sNeoBook 5 (RAD / Pro Multimedia)WindowsModernized authoring, plugins, app-building focus
2018–presentVisualNEO for WindowsWindowsRebranded and continued by SinLios

Across these generations the central metaphor never changed — visual pages plus action commands compiling to a standalone program — even as the surrounding platform moved from DOS to modern Windows.

Current Relevance

NeoBook today lives on as VisualNEO for Windows, maintained by SinLios Soluciones Digitales. It remains a niche tool, but a durable one: it still appeals to the same audience it always served — people who want to build small Windows applications, installers, kiosks, and interactive media quickly and visually, and ship them as a single EXE. A long-running user community (the former NeoSoft support forums, now archived and continued under the VisualNEO name) preserves decades of plugins, examples, and know-how.

In the wider landscape, NeoBook is also a window onto a particular moment in computing history — the CD-ROM and shareware era, when “multimedia authoring” was a category of its own and tools like NeoBook, HyperCard, and ToolBook let non-programmers ship interactive software.

Why It Matters

NeoBook matters less as a programming language in the strict sense and more as an example of a powerful idea: software authoring for everyone. By replacing source files with a visual canvas and a friendly action vocabulary, and by compiling the result into a single, freely distributable executable, NeoBook let a generation of educators, hobbyists, magazine publishers, and small businesses build and ship real interactive programs without learning to code. Its longevity — from MS-DOS shareware in the early 1990s through a Spanish rebrand as VisualNEO three decades later — is a testament to how much demand there has always been for that lower barrier to making software.

Timeline

1993
NeoBook for MS-DOS is published by NeoSoft Corp. as a visual e-publishing tool for non-programmers; the earliest surviving releases carry copyright dates beginning around 1993.
1994
Interactive CD-ROM content built with NeoBook ships with PC Gamer magazine, an early high-profile use of the tool for cover-disc menus.
1995
NeoBook Pro 2.x (for example version 2.1f) circulates widely as MS-DOS shareware, compiling publications into self-contained executables.
1997
Around 1997, NeoBook 3 — the first 32-bit Windows edition — is released, moving the product from DOS to the Windows desktop (exact date uncertain).
2007
The NeoBook 5 series (marketed as 'NeoBook Rapid Application Builder' and 'NeoBook Professional Multimedia') modernizes the product for contemporary Windows.
2013
NeoBook 5.8.x updates continue; the published version history is maintained into March 2013, with the line eventually reaching 5.8.7.
2018
NeoSoft transfers the NeoBook, NeoPaint and NeoAppBuilder product lines to SinLios Soluciones Digitales S.L. of Spain, which begins rebranding NeoBook as VisualNEO.
2019
Development continues under SinLios as VisualNEO for Windows, carrying the NeoBook engine forward with year-based version numbering.

Notable Uses & Legacy

PC Gamer magazine cover discs

Interactive CD-ROM menus and content distributed with PC Gamer in its 1994 editions were built with NeoBook, showcasing its role in early consumer CD-ROM publishing.

CD-ROM and shareware front-ends

NeoBook was widely used to build the autorun menus, installers, and browse-the-disc front-ends that fronted shareware compilations and CD-ROM collections in the 1990s.

Electronic books and courseware

Because publications compiled into a single distributable EXE, NeoBook was a popular choice for e-books, catalogs, encyclopedias, and self-paced educational courseware aimed at non-technical authors.

Kiosks and presentations

Its visual, page-based model and standalone output made NeoBook a practical tool for information kiosks, point-of-sale displays, and interactive multimedia presentations.

Running Today

Run examples using the official Docker image:

docker pull
Last updated: