Migrate from IntraWeb to sgcHTML — Delphi web UI components | eSeGeCe

Migrate from IntraWeb to sgcHTML

IntraWeb by Atozed Software is one of the longest-serving Delphi web frameworks: VCL-style forms are designed in the IDE and rendered server-side as HTML, and a limited edition even ships with RAD Studio. It is mature and familiar to Delphi developers. Teams running IntraWeb applications typically look at sgcHTML when they want modern, responsive Bootstrap 5 markup, lighter partial page updates and WebSocket realtime, all while staying in the Delphi language and IDE they already know.

What Changes Architecturally

In the classic IntraWeb model, as Atozed Software describes it, VCL-style forms are designed in the RAD Studio IDE and rendered server-side as HTML, with one stateful session per user. The model is mature and familiar. The generated markup predates modern Bootstrap layout, so a responsive, mobile-first result typically needs additional CSS work. sgcHTML keeps the server-side rendering idea and changes the pieces around it.

Bootstrap 5 markup out of the box

Every component renders clean, semantic Bootstrap 5 HTML. Pages are responsive and mobile-first by default, restyle with any Bootstrap theme, and light and dark theming is built in.

htmx partial updates

Instead of full form round-trips, the browser requests HTML fragments through htmx (~14 KB) and the server returns exactly the piece of the page that changed.

State becomes your choice

There is no mandatory per-user UI object tree in server RAM. Pages render statelessly, and you decide what session state, if any, your application keeps.

Realtime and hosting built in

WebSocket push is part of the same component set through the sgcHTMX engine. The components run in the sgcWebSockets server or in WebBroker, DataSnap and RAD Server hosts, and a pure managed .NET implementation is also available.

IntraWeb Concepts and Their sgcHTML Equivalents

The concepts carry over cleanly. Here is where each familiar IntraWeb building block lands in sgcHTML.

IntraWeb conceptsgcHTML equivalent
IWForm designed in the IDEA page composed with TsgcHTMLPageBuilder and node components
IW controls (TIWEdit, TIWGrid, TIWButton)TsgcHTMLComponent_Form, TsgcHTMLComponent_Grid, TsgcHTMLComponent_Chart and the rest of the 89-component catalog
DB-aware IW controls27 data-aware components bound directly to a TDataSet / DataSource
OnAsyncClick callbackshtmx fragment routes that return component HTML
Per-user session objectsStateless pages plus whatever session policy you choose
ServerController deploymentA single sgcWebSockets server executable, or a WebBroker / DataSnap / RAD Server host
Custom templates and CSSBootstrap 5 theming with light and dark modes built in
Timers and polling for live dataWebSocket broadcast of HTML fragments (hx-swap-oob)

What You Keep

A migration to sgcHTML replaces the UI layer, not your investment.

Your code base and IDE

You keep working in RAD Studio with Delphi or C++ Builder. sgcHTML components are native classes compiled into your server binary.

Your data modules

Existing TDataSet logic, data modules and database drivers plug straight into the 27 data-aware components. No new data layer is required.

Your deployment habits

Deploy a single self-contained executable or service, just as you do today. No external runtime is needed.

Your team's language skills

You write Object Pascal or C#; sgcHTML writes the HTML, CSS and JavaScript. No JavaScript is required from the developer.

A Pragmatic Migration Path

You do not need a big-bang rewrite. Four steps, screen by screen.

1

Inventory the screens

List the IWForms, the controls on each, the datasets behind them and which screens need live data.

2

Map each screen

Match every screen to sgcHTML components using the table above and the component gallery with all 89 components.

3

Rebuild page by page

Since sgcHTML serves standard HTTP, both servers can run side by side behind the same reverse proxy while you move one screen at a time.

4

Wire interactivity and push

Add htmx interactions where screens post and refresh, and WebSocket push where the application needs live data.

We Help You Migrate

You do not have to do this alone. Tell us about your IntraWeb application, the screens, the data behind them and the realtime behaviour you need, and the eSeGeCe team helps you plan the migration and propose a component mapping. If you prefer, we rebuild the application for you through sgcCustomization HTML, one-time packages from €149.

sgcHTML itself includes full source code, is licensed per developer from €299 and requires sgcWebSockets Professional or Enterprise.

See It Running

Five complete applications, every one built only with sgcHTML + sgcWebSockets, live on the eSeGeCe demo server.

ERP

A full ERP web application: customers, providers, products, invoices and reports.

Open the live demo →

Admin CRUD

A compact admin console with CRUD screens, live search and role-based access.

Open the live demo →

Live Monitor

A realtime operations dashboard whose KPIs are pushed live over WebSockets.

Open the live demo →

Customer Portal

A customer self-service portal with orders, profile and support.

Open the live demo →

Helpdesk

A support-ticket helpdesk with reply threads, attachments and an admin dashboard.

Open the live demo →

To be fair: staying on IntraWeb is a reasonable choice when you already have a working IntraWeb application, a team fluent in its VCL-style server-side form model, and internal tools with a modest number of concurrent users. If you want to weigh the options with evidence, our neutral comparison page puts sgcHTML, IntraWeb and the other Delphi web frameworks in a side-by-side matrix with sources.

Best value: All-AccessEvery eSeGeCe product, Premium Support included, from €1,059/year.
See All-Access pricing

Try sgcHTML on One Screen

Download the free trial with all 89 components and rebuild a single IntraWeb screen as a Bootstrap 5 page. That first page tells you more than any comparison table.