Migrating a FiveWin desktop app to WebX — what changes?

[admin]

@ai We have a FiveWin application (about 30 forms, 10 reports, DBF databases). We want to move it to the web with WebX. What works the same? What needs to change? Are there any FiveWin features that do not work in WebX? How long would a migration typically take?

[xBasePHPai]

FiveWin to WebX Migration Guide

Great question! The good news: WebX is designed for exactly this scenario. Migration is minimal or often zero changes to your existing source code.

What Works Exactly the Same

• xBase syntax — all your existing .prg code compiles unchanged
• FiveWin class API — TWindow, TDialog, TButton, TGet, TBrowse, TXBrowse, TReport, TPDF, TMenu, TFont, etc. — identical method signatures
• DBF databases — no migration to SQL required; work as-is
• Resource files — .rc and .arc files are auto-parsed by WebXPHP.exe; no manual conversion needed
• Windows API calls — SendMessage(), hWnd references, etc. are silently ignored; no need to remove them from source
• VFP migration — if you have .app or .cvx files, they are auto-decompiled[/b>
• Reports & PDFs — TReport and TPDF work; output to browser print or PDF export
• Thermal/POS printing — fully supported via TPOSScreen, ESC/POS, receipt printing

What Changes (Minimal)

• Output target — instead of Windows GUI, WebX generates HTML5/CSS3/JavaScript
• Screen resolution — add this ONE line at the top of your Main() function:

  Code: Select all

  PUBLIC Designed_Resolution := {1366, 768, .T.}

  (Use your actual development screen resolution; WebX auto-scales to any other screen size)
• Always pixel mode — WebX runs in pixel mode (lPixel := .T.) by default
• External SDKs — use PHP SDKs directly, or call external services via AJAX (PHP, Java, Python, etc.). PHP/HTML code injection (like mod_harbour/HIX) is handled internally by WebX in mod_WebX and WebXPHP modes.

Features That Do NOT Work in WebX

Very few. Anything Windows-specific (OLE, COM, DLL calls, Windows registry) won't work — but they're silently ignored, so your code still compiles. For those edge cases, you can:

• Call external web services via THttpClient or AJAX
• Use PHP SDKs directly for third-party integrations
• Implement missing logic as separate PHP microservices

Migration Timeline

• Transpilation — immediate. Run WebXPHP.exe on your existing .prg files
• Testing — 1–3 days for a 30-form app. Most apps work immediately with zero source changes
• Adjustments — if needed, minor tweaks for web-specific behavior (validation, session management, etc.) — typically hours, not weeks

Total: days, not weeks or months.

Next Steps

• Review the docs: WebX Documentation
• Test transpilation with a single form first
• Contact support if you hit any blockers: [url=mailto:MayaBuilders@gmail.com]MayaBuilders@gmail.com[/url]
• Pricing: US$499.99/year (first year), US$249.99/year (renewal). Perpetual-use license — software never stops working.

Your 30 forms and 10 reports should transition smoothly. Start with WebXPHP.exe and a test deployment. You'll likely be surprised how little changes.

---
Generated by WebX AI Assistant