FiveTech Support Forums

Hi everyone,

I would like to share with the community the progress of my project SEM Web. I have been part of the xBase world since 1993, starting with Clipper, and migrating to FiveWin between 1998 and 2000. After more than 25 years of developing my ERP for Windows using the Harbour + FWH + C++ stack, I took on the challenge of bringing it to the web without losing our roots: Harbour.

In just one and a half months (started in January 2026), I have successfully migrated the complete POS/Cashier module. A key factor in this transition has been the data layer. In my desktop version, I use the excellent Eagle1 library by Manu Expósito to manage MariaDB/MySQL. Taking the core concepts of Eagle1 and with the help of Antigravity, I developed a Node.js API to serve as the bridge for this new web environment.

Modules already operational on the web:

Inventory: Real-time queries.

• Electronic Invoicing (FEL): Full integration with FEL certifiers for Guatemala.

• Cashier/POS: Openings, closings, and cash flow management.

• Restaurant POS: Dynamic table control for orders.

• Sales: Quotations and Orders.

Tech Stack:

• Backend: Harbour + Hix Web Server.

• Data Layer: Node.js API (inspired by Eagle1) + MariaDB/MySQL.

• Frontend: HTML5, CSS3, JavaScript, and Bootstrap (developed with Antigravity).

The transition has been incredibly smooth. The business logic I’ve perfected over decades in Windows now lives in the cloud, proving that our experience with Harbour is a powerful foundation for modernization.

Here are some screenshots of the interface:

For me, this is the beginning of making my dream of migrating my application to the web a reality, using the language I have always used and understood: Harbour.

I want to thank Carles for his incredible work with Hix, Manu for Eagle1, and Antonio Linares for FiveWin and Harbour.

Best regards.

Carlos.

Mi enhorabuena. Y por supuesto me uno a los agradecimientos.

Gracias tocayo.
Yo ya voy llegando a los 60 años, y con estas nuevas herramientas (Hix + Harbour + Antigravity), he podido optimizar mis tiempos de desarrollo, ya que no solo para la Web he utilizado la IA, me ha servido tambien para mi sistema con FWH para Windows, los clientes siguen pidiendo cambios :D

Saludos.

Carlos

Hi Carlos,

Your progress with Hix/Node.js is visually very strong. Many of us are currently facing the same challenge: taking our legacy MDI windows—often with 50+ input fields—and making them 'mobile-first' for devices like the iPhone.

I’d like to bring the conversation back to the 'Think Tank' roots of this forum. Instead of just looking at the finished product, could you share a 'Before & After' comparison?

It would be highly educational to see:

A screenshot of the original FiveWin desktop screen.

How you transformed that specific complex workflow into a user-friendly mobile interface.

In the age of AI, the code itself is becoming a commodity. The real 'gold' is the architectural logic and UI transformation. Are we looking at a full functional migration, or a focused dashboard approach? This insight would be a great contribution to the community.

Best regards, Otto

Hola Otto,

Como ya he comentado, he mantenido mi desarrollo de mi sistema con FWH+Harboour y C++, durante 25 años mas o menos,
y me di cuenta de que una migración 1:1 de una pantalla de escritorio a la web no era tan fácil hacerlo.
Mi enfoque no ha sido un simple panel de control, sino una migración funcional completa basada en dos bases principales:

1. Desacoplamiento estratégico (el puente API)
   En lugar de intentar replicar la lógica MDI, desarrollé una API de Node.js inspirada en Eagle1 de Manu Expósito.
   Esto me permitió mantener la lógica de negocio pesada en el backend y, al mismo tiempo, entregar datos optimizados con formato JSON al frontend.

2. Componentización móvil
   Usando Bootstrap y Antigravity, y cambiando mi enfoque escritorio a web, multidispositivo, agrupando datos para que el usuario solo vea lo que necesita en ese momento.
   Flujos de trabajo modales: Desglosar procesos complejos (como un pedido o una factura de FEL) en interacciones modales paso a paso.

Como he hecho lo anterior? pues, toda mi logica de negocio que tengo en mi desarrollo de FWH, lo tengo por separado, utilizando Eagle1 y todo el diseño de las interfaces con FWH, con esto, le dado esa base de la logica del negocio a Antigravity y la API de Node.js que ya utilizaba con FWH mas todo el codigo de la certificación de facturas electrónicas a Antigravity, lo cual, casi lo ha traslado integramente este codigo de Harboour a la Web, que Hix la procesa sin problemas.

Entonces, la parte del front end, Antigravity se ha encargado según mis requerimientos. No quería una tablero administrador con las opciones en un menu vertical a la derecha, yo quería un menú horizontal, parecido al menú de mi aplicación con FWH, para que no vieran los clientes tantos cambios en la versión web, y al utilizar Bootstrap, tengo la parte de reponsive para dispositivos moviles resuelto.

Como bien dices, Otto, en la era de la IA el código es una mercancía; el verdadero valor está en la lógica arquitectónica.
Al separar mi lógica de negocio (Backend en Harbour/Node.js) del diseño (Frontend con Bootstrap), logré que el sistema fuera moderno sin perder
la robustez que mis clientes han confiado durante décadas, pero esto, no lo hubiera logrado sin la ayuda de Hix, ya que sigo trabajando con el mismo lenguaje que he utilizado por tanto tiempo y lo he podido reutilizar, gracias al tabajo de Carles con Hix.

Aquí están las capturas de la versión 'Before' (FWH Desktop) para que puedan apreciar el cambio hacia el 'After' (Hix Web).

Saludos cordiales.

Carlos.

--------------English------------------------------------

Hi Otto,

As I’ve mentioned, I’ve maintained my system development with FWH + Harbour + C++ for about 25 years. I quickly realized that a 1:1 migration from a desktop screen to the web was not a simple task. My approach hasn't been just a basic dashboard, but a full functional migration based on two main pillars:

1. Strategic Decoupling (The API Bridge)
   Instead of trying to replicate the MDI logic, I developed a Node.js API inspired by Manu Expósito’s Eagle1. This allowed me to keep the heavy business logic in the backend while delivering optimized JSON data to the frontend.

2. Mobile Componentization
   By using Bootstrap and Antigravity, and shifting my focus from desktop to a multi-device web approach, I’ve grouped data so that users only see what they need at any given moment.
   Modal Workflows: I broke down complex processes (like a restaurant order or a FEL invoice) into step-by-step modal interactions.

How did I achieve this? Well, all the business logic in my FWH development is kept separate using Eagle1. I provided that business logic base to Antigravity, along with the Node.js API I was already using with FWH and all the electronic invoicing (FEL) certification code. Antigravity essentially migrated this Harbour code to the web, and Hix processes it without any issues.

For the frontend, Antigravity handled it according to my specific requirements. I didn’t want a standard admin dashboard with a vertical menu on the right; I wanted a horizontal menu, similar to my FWH application, so my clients wouldn't feel such a drastic change in the web version. By using Bootstrap, I’ve also resolved the responsiveness for mobile devices.

As you rightly said, Otto, in the age of AI, code is a commodity; the true value lies in the architectural logic. By separating my business logic (Backend in Harbour/Node.js) from the design (Frontend with Bootstrap), I managed to create a modern system without losing the robustness my clients have trusted for decades. However, I couldn't have achieved this without Hix, as it allows me to continue working with the same language I’ve used for so long and reuse it thanks to Carles’ work.

Here are the screenshots of the 'Before' (FWH Desktop) version so you can appreciate the transition to the 'After' (Hix Web).

Carlos, Thanks for sharing the 'Before' screenshots, Carlos. Seeing the 'Ingreso de Factura' screen with its 30+ fields really highlights the scale of the challenge: how do you transform that high-density desktop workflow into something manageable on an iPhone?

To bring this back to a 'Think Tank' level, it would be great to understand:

How did Antigravity help you break down these massive forms into mobile-friendly 'Modal Workflows'?

With the Node.js API bridge, how do you handle complex business logic (like FEL certification) while maintaining the snappy response time desktop users expect?

The transition from a dense MDI to a responsive web interface is the core struggle for many here, and seeing how you prioritized fields for the mobile view would be a huge contribution. If we don't have Antigravity, how does your Node.js + Hix stack actually help the rest of us solve the '50-field problem'? However, I’m concerned about long-term maintenance. You’ve built a multi-layered stack: Harbour logic, a Node.js API bridge, and an Antigravity-generated frontend. How do you maintain this without going crazy? Best regards, Otto

Otto.
Par mi, en mi lógica, resoví el problema que planteas con un "Procesamiento Asíncrono" por así decirlo.

Mientras que la API de Node.js se encarga de la comunicación con el Servicio de Administración Tributaria de Guatemala (SAT) para la certificación FEL, el frontend se mantiene ágil, y gracias a que Hix comprende Harbour tan bien, no tengo que reescribir las reglas de validación principales, simplemente las "puenteo".

Y a tu pregunta, ¿Cómo evitar la locura?, la respuesta es Antigravity + Gemini 3 Flash

No me tengo que volver loco! en este tiempo que estamos viviendo, ya tenemos la ayuda de Antigravity y los agentes IA asociados a el, no hay porque preocuparse por eso. Como bien dijo Antonio Linares en otro post, ahora somo administradores o arquitectos del software que creamos, y la IA + Antigravity hacen el trabajo duro.

Yo ahora, en lo que Antigravity hace el trabajo que le pido, yo puedo levantarme e ir a hacer un café de la región de Cobán de acá de Guatemala, que tanto me gusta, y cuando regreso a mi computadora el trabajo esta hecho, solo será de seguir puliendo detalles, y esto, a mi edad, es un gran alivio, y no he perdido el gusto ni el animo de desarrollar aplicaciones o mejorar lo que ya he hecho, al contrario, ahora puede hacer mas de lo que hacía antes.

Resumiendo:

• Harbour (El Alma): Todas mis reglas fiscales y cálculos comerciales se almacenan aquí. Si la ley cambia, las modifico en un solo lugar.

• Node.js (El Mensajero): Solo gestiona el transporte de datos y la seguridad de la API externa.

• Bootstrap/JS (La Cara): Gracias a Antigravity, el frontend se construye con componentes estándar. Si necesito cambiar un botón, no toco la lógica de negocio.

Al mantener el "Alma" (Harbour) separado de la "Cara" (Interfaz Web), el mantenimiento es mucho más sencillo que en nuestras antiguas aplicaciones MDI monolíticas, donde la interfaz de usuario y la lógica solían estar entrelazadas.

Saludos cordiales.

Carlos.

------------------- English --------------------------------------------------------------------

Otto,

To address your concerns, I solved the performance issue with what I call "Asynchronous Processing."

While the Node.js API handles the communication with the Guatemala Tax Authority (SAT) for the FEL certification, the frontend remains snappy. Since Hix understands Harbour so perfectly, I don’t have to rewrite my core validation rules—I simply "bridge" them.

Regarding your question, "How to avoid the madness?", my answer is: Antigravity + Gemini 3 Flash.

In the era we are living in, we have the help of Antigravity and its associated AI agents; there’s no need to worry about being overwhelmed. As Antonio Linares recently mentioned in another post, we have become the managers or architects of the software we create, while the AI and Antigravity handle the heavy lifting.

Now, while Antigravity performs the tasks I request, I can get up and brew a cup of Cobán coffee (a region here in Guatemala that I love). By the time I return to my desk, the work is done, and I only need to polish the details. At my age, this is a massive relief. I haven't lost the passion or the drive to develop; on the contrary, I can now achieve much more than I used to.

To summarize my architecture:

• Harbour (The Soul): All my fiscal rules and business calculations are stored here. If the law changes, I modify it in one single place.

• Node.js (The Messenger): It strictly manages data transport and external API security.

• Bootstrap/JS (The Face): Thanks to Antigravity, the frontend is built with standard components. If I need to change a button, I don’t have to touch the business logic.

By keeping the "Soul" (Harbour) separated from the "Face" (Web UI), maintenance is actually much simpler than in our old monolithic MDI applications, where the UI and logic were often tangled together.

Best regards,

Carlos

Querido Carlos,

Como detalle técnico, si desinstalas Antigravity y lo descargas e instalas nuevamente, ya puede usar Gemini 3.1 que es una auténtica maravilla :!: :idea:

https://forums.fivetechsupport.com/viewtopic.php?t=46349

Carlos, the idea of brewing coffee while AI handles the migration sounds like a dream, but for a system with 30+ fields per screen, it sounds like a maintenance nightmare in the making.

To move from a 'showcase' to a real 'Think Tank' contribution: Why not set up an online demo? > If you have truly achieved a full functional migration of complex FEL invoicing in just 30 days, let the community test it. A live demo would prove if the 'Asynchronous Processing' and the Node.js bridge actually hold up under real-world multi-user pressure on an iPhone. Let's see the 'Soul' and the 'Face' in action together.

Best regards, Otto

Dear Otto,

You still underestimate the current AI coding power... :wink:

Antonio Linares wrote:

Querido Carlos,

Como detalle técnico, si desinstalas Antigravity y lo descargas e instalas nuevamente, ya puede usar Gemini 3.1 que es una auténtica maravilla :!: :idea:

https://forums.fivetechsupport.com/viewtopic.php?t=46349

Estimado Antonio, si!! ya he actualizado Antigravity y me he dado cuenta de lo que dices, Gemini 3.1 es una marvilla.
Pero tambien he probado Claude Sonet 4.6 y te digo, no se queda atras tampoco.

Saludos cordiales.

Carlos

Otto wrote:

Carlos, the idea of brewing coffee while AI handles the migration sounds like a dream, but for a system with 30+ fields per screen, it sounds like a maintenance nightmare in the making.

To move from a 'showcase' to a real 'Think Tank' contribution: Why not set up an online demo? >
If you have truly achieved a full functional migration of complex FEL invoicing in just 30 days, let the community test it. A live demo would prove if the 'Asynchronous Processing' and the Node.js bridge actually hold up under real-world multi-user pressure on an iPhone. Let's see the 'Soul' and the 'Face' in action together.

Best regards,
Otto

Dear Otto,

As I mentioned before, for me, it was a long-held dream to bring my years of development to the web. With these tools, I have already begun to make that dream a reality. And as Antonio pointed out, you are still underestimating the current power of AI-assisted programming.

I am currently working on putting this first phase into production for a client here in Guatemala. This coming March, they will be working fully with my web system in a production environment, with many concurrent users working regularly on the platform.

Give me some time until next month to prepare a sandboxed online demo so you can test what I have developed directly from your smartphone or any device you prefer. Your feedback will be very helpful in further testing and improving the system.

Best regards,

Carlos

Carlos, Without a real online demo that we can stress-test here in the forum, your 'Release Candidate' remains nothing more than a visual design study. I'm not saying it doesn't work—it's up to you to put a demo online and prove it.

Best regards, Otto

Carlos, Fair enough. I have given this date to my AI agent, which is now scheduled to automatically post a follow-up here in March to check on that demo. I'm not saying it doesn't work—it's up to you to put it online and prove it. We’ll let the agents handle the reminder. Best regards, Otto

Dear Otto,

What AI agent do you use that is able to post on these forums ?