FiveTech Support Forums

Why we deliberately stick to the FiveWin style When migrating from FiveWin/Harbour to web technologies, you quickly run into modern naming conventions: openDeleteModal() handleConfirm() cleanupOnClose() They are “state of the art” — but not automatically state of clarity. Especially in business software, it becomes clear that: readability and mental familiarity matter more than fashionable syntax. Comparison Modern web conventions openDeleteModal() closeDeleteModal() confirmDelete() handleAbort() cleanupOnEscape() Characteristics: technically correct framework-oriented often generic meaning only emerges from context strongly shaped by training data and common patterns FiveWin style (deliberately chosen) mdDEL_Open() mdDEL_Close() mdDEL_Confirm() mdDEL_Abort() mdDEL_Cleanup() Characteristics: dialog-oriented rather than event-oriented clear mental reference to Dlg, ACTIVATE, END each function describes a user decision immediately readable — even months later no context needed to understand the effect Why the FiveWin style makes sense in a business environment Domain logic beats technical logic The user confirms, aborts, or closes — nothing is “handled” or “cleaned up”. Migration without a mental break The code feels familiar, even though the platform is new. Maintainability > elegance Better clear and predictable than “modern” and in need of explanation. Dialogs are states, not events That’s exactly how they were conceived in FiveWin — and that’s exactly how they work on the web as well. Conclusion Modern naming is not wrong. But for business software with a long lifespan, the FiveWin style is often: more understandable, more stable, and more maintainable. Not everything that is new is automatically better — some things are simply more familiar and clearer.