From Desktop (FWH + Eagle1) to Web (Hix + Harbour + Node.js) in a month and a half..
-
Otto
- Posts: 7020
- Joined: Fri Oct 07, 2005 7:07 pm
- Has thanked: 100 times
- Been thanked: 91 times
- Contact:
Re: From Desktop (FWH + Eagle1) to Web (Hix + Harbour + Node.js) in a month and a half..
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
-
Otto
- Posts: 7020
- Joined: Fri Oct 07, 2005 7:07 pm
- Has thanked: 100 times
- Been thanked: 91 times
- Contact:
Re: From Desktop (FWH + Eagle1) to Web (Hix + Harbour + Node.js) in a month and a half..
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