Safire›SafireIDE

SafireIDE

Work visually. Drop into source. Keep the same application truth.

SafireIDE is the primary professional working environment for Safire developers — combining visual RAD, source, data, events, diagnostics, tests, Source Vault and optional AI context.

Developer workspace

Designed for the full development day.

A full-stack business developer should be able to move from a database field to a form, event handler, query, test, build or history view without reconstructing the application in their head.

Solution and project navigation built around application objects.
Visual designers for windows, controls and future business artefacts.
Source editing for precise language-level control.
Contextual events, properties and developer commands.
Build, test and diagnostics integrated with the project.

One object, multiple views

Select the thing you are working on — not merely the file that contains it.

DATA

Data view

Schema, fields, relations, queries and database context.

DES

Design view

Window/control hierarchy, designer surface and modifier properties.

CODE

Source view

Readable Safire source, procedures and event handlers.

TEST

Proof view

Build output, diagnostics, tests and change evidence.

Visual design + source

Source truth without source-file tyranny.

Most developers should use the IDE 99% of the time. That should never mean surrendering the source.

Designer → SourceVisual actions persist through the canonical Safire model.

Source → DesignerSource changes are reflected back into the visual representation.

AI → Reviewable changeAI proposals remain inspectable before they become project truth.

Vault → HistoryChanges can be compared and traced through Source Vault.

Contextual development

Right-click should open the work around an object.

Controls, windows, tables, procedures and tests can expose context-specific development operations rather than forcing the developer to navigate a global tool maze.

CTL

Control

Properties, bindings, events, source, validation, tests and AI actions.

Table

Schema, relations, queries, usage, migrations, CRUD generation and test data.

PROC

Procedure

Callers, references, tests, diagnostics, review and refactoring.

WIN

Window

Control tree, event code, bindings, preview, tests and design review.

ERR

Failure

Affected source, last change, related tests, runtime diagnostics and likely repair.

HIST

History

Diff, why it changed, who changed it, tests and release provenance.

Event-oriented development

Open the code associated with the control.

The IDE should make the main events immediately visible and let developers add less-common events without leaving the design context.

Common events shown first.
Additional events available from the control's event catalogue.
Event code can appear in a central source pad or dedicated working view.
Right-click actions can move directly between design, source and event wiring.

AI as a workspace service

AI context should follow the work.

A selected table, window, control or procedure already provides a natural context boundary. Safire AI can use that context instead of requiring every prompt to rediscover the project.

AI in Safire

SafireIDE database diagram and AI assistant

Desktop architecture

Safire semantics above mature native infrastructure.

Safire Desktop V1 targets Windows x64 with wxWidgets beneath the public Safire application model. The developer works with Safire controls, events, binding, validation, themes and business concepts — not wxWidgets mechanics.

Safire sourceLanguage + project truth

SafireIDEDesigner + developer experience

Safire application / UI modelPublic semantics owned by Safire

Desktop runtimeSafire controls and services

wxWidgets / WindowsNative implementation beneath Safire

The IDE is where you work.

Visual productivity on top of explicit source and a coherent application model.

View current screenshots