FiveTech Support Forums

Hello Bayron,

Congratulations. Very interesting. I have added a link on clipper2web.com.

Best regards,

Otto

🔧 Complete Function Library (220+ Functions)
Core Clipper Functions: STR(), LEN(), SUBSTR(), AT(), STRTRAN(), VAL(), UPPER(), LOWER()
xHarbour HB_ Extensions*: HB_MD5(), HB_SHA256(), HB_BASE64ENCODE(), HB_FILEEXISTS(), HB_UTF8TOSTR()
Array Operations: ARRAY(), AADD(), ADEL(), AINS(), ACLONE(), ATAIL(), AFIELDS() with full indexing
Database Functions: Complete DBF support with USE, SEEK, SKIP, DBGOTO(), RECNO(), EOF()
String Functions: ALLTRIM(), PADL(), PADR(), STUFF(), LEFT(), RIGHT(), CHR(), ASC(), SPACE(), TRANSFORM(), SOUNDEX()
File I/O: FOPEN(), FREAD(), FWRITE(), FCREATE(), FERASE(), MEMOREAD(), MEMOWRIT() with complete parameter support
Directory Functions: DIRECTORY(), ADIR(), CURDIR(), DISKSPACE(), MAKEDIR() with security controls
System Functions: MEMORY(), DISKSPACE(), CURDIR(), ISINTERNET(), ISPRINTER(), PROCNAME(), PROCLINE()
Math Functions: ABS(), INT(), ROUND(), SIN(), COS(), TAN(), SQRT(), CEILING(), FLOOR(), MOD(), MAX(), MIN()
Date/Time: DATE(), DTOC(), CTOD(), YEAR(), MONTH(), DAY(), CDOW(), CMONTH(), DOW(), TIME(), SECONDS()
CONDITIONAL STATEMENTS: NESTED iF, DO CASE, SWITCH, CODEBLOCKS

BROWSERS, etc.
Native .DBF handling... no Mod's to install, as much copy and paste as possible...

Same code, different products..... the rendering is off a little bit, due to the translation from php, javascript, etc to rendered html.....
No stress tests have been implemented yet... so be patient,,,,, only rendering tests, with few commands... but we have the assembly line already formed, and the process logic, its not yet fully implemented... or all functions tested yet..., just implemented.... but if you use the commands in the sample file... you can see that the process is live already.....
AND I KNOW, I NEED TO PLAY WITH THE COLORS A LITTLE BIT... work in progress.....

Please review this Harbour language PRG file and generate an entire structure with php, javascript, css, ajax, sql, etc. to translate the Harbour and FiveWin commands to php commands, and trying to stay away from Python, to have a copy and paste project

Provide a clear, single “generation brief” that includes the target stack, the exact Harbour/FiveWin features to translate, concrete I/O examples, and the acceptance text “STRESS TEST PASSED!” as a required output, so the generator can produce a complete, copy‑paste PHP project and self-test execution. Below is a ready-to-use prompt template filled with your stress-test details and OOP mappings.

Dear Antonio,

May I ask for your expert opinion? ChatGPT suggests the following regarding a transpiler approach from Harbour/FiveWin to web technologies:

Yes, for a narrow set of commands (DIALOG / SAY / BUTTON / GET / BROWSE + simple ACTION(...)), a lightweight parser → AST → renderer can be very efficient. The advantage is that you feed real PRG code and get HTML/JS output; migration of many small dialogs becomes quick.

But: full FiveWin semantics (events, owner-draw, resources, third-party controls) is large. Especially with complex workflows, a functionality/UX-first rebuild is more robust: keeping the same use cases, but designed web-natively (responsiveness, accessibility, SPA-state).

Pragmatic mix:

– A small transpiler for standard controls & layouts (covering ~90% of dialogs).

– For special cases, rebuild them specifically with a proper web UX.

Do you think this assessment makes sense, or would you recommend another path?

Best regards,

Otto

Dear Otto,

I would try with Grok Code Fast and with Gemini 2.5 Pro also. Kimi and DeepSeek may help too.

The more output Byron posts here, the easier AIs will guess the prompts.

AIs are great on reverse engineering: "What do I have to ask you to get this ?"

He seems to be using Claude...

> Do you think this assessment makes sense, or would you recommend another path?

If we provide some little examples to the AI (we can ask the AI to build them) then we can ask for a prompt to generalize them

Using FiveWin and Harbour I can build a window for Windows doing this: DEFINE WINDOW oWnd ; ACTIVATE WINDOW oWnd. How could I port that code to php so a window is shown on an internet browser ?

Desktop-style windows like FiveWin’s DEFINE/ACTIVATE WINDOW don’t exist in the browser; to “show a window” on the web, build an HTML page served by PHP and render a modal/dialog or panel with HTML/CSS/JavaScript, while PHP handles server-side logic and data. In other words, replace GUI windows with web UI components and serve them over HTTP.

What changes conceptually
FiveWin creates native Windows GUI; the web uses HTML/CSS/JS rendered by the browser and HTTP to communicate. PHP generates HTML or JSON on the server; JavaScript controls dialogs, forms, and events on the client.

Minimal “window” in a browser
Use an HTML page plus a modal/dialog to simulate a window. The modal is opened by JavaScript and styled with CSS; PHP can echo the HTML or return data to fill it.

Example structure

index.php: outputs a page and a “window” (modal) container.

php
<?php
// index.php
$title = "My Web Window"; // could come from DB/business logic
?>
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title><?= htmlspecialchars($title) ?></title>
<style>
body { font-family: sans-serif; }
.overlay { display:none; position:fixed; inset:0; background:rgba(0,0,0,0.4); }
.window { width:480px; margin:10% auto; background:#fff; border-radius:6px; box-shadow:0 8px 24px rgba(0,0,0,.2); }
.window-header { padding:10px 14px; background:#1976d2; color:#fff; border-top-left-radius:6px; border-top-right-radius:6px; display:flex; justify-content:space-between; align-items:center; }
.window-body { padding:16px; }
.btn { padding:8px 12px; border:0; border-radius:4px; background:#1976d2; color:#fff; cursor:pointer; }
.btn.secondary { background:#777; }
</style>
</head>
<body>
<h1>Home</h1>
<button class="btn" id="openWin">Open Window</button>

<div class="overlay" id="overlay">
<div class="window">
<div class="window-header">
<span><?= htmlspecialchars($title) ?></span>
<button class="btn secondary" id="closeWin">X</button>
</div>
<div class="window-body" id="winBody">
Loading...
</div>
</div>
</div>

<script>
const overlay = document.getElementById('overlay');
const openBtn = document.getElementById('openWin');
const closeBtn = document.getElementById('closeWin');
const winBody = document.getElementById('winBody');

openBtn.addEventListener('click', async () => {
overlay.style.display = 'block';
// Fetch server content (simulates filling a window)
const res = await fetch('window_content.php');
winBody.innerHTML = await res.text();
});

closeBtn.addEventListener('click', () => {
overlay.style.display = 'none';
});
</script>
</body>
</html>
window_content.php: returns the inner HTML; it could query DBFs or SQL and render data.

php
<?php
header('Content-Type: text/html; charset=utf-8');
// Example dynamic content:
echo '<p>This content came from PHP on the server.</p>';
echo '<form method="post" action="save.php">
<label>Name <input name="name" required></label>
<button class="btn" type="submit">Save</button>
</form>';
Mapping key FiveWin ideas to the web
DEFINE WINDOW/ACTIVATE WINDOW → HTML document plus a modal/dialog/panel; open/close via JavaScript.

Controls (buttons, textboxes) → HTML form elements; enhance with JS or a UI framework (Bootstrap, Material UI, or native <dialog>).

Events (ON INIT, ON CLICK) → JavaScript event listeners; server calls via fetch/AJAX to PHP endpoints.

Data access (DBF/Indexes) → Serve through PHP: either migrate to MySQL/PostgreSQL or expose Harbour data via CGI/mod_harbour and fetch via HTTP.

Alternative: Keep Harbour and serve via HTTP
Harbour can run as CGI or behind an HTTP server to emit HTML directly, letting existing Harbour code drive web responses; mod_harbour and simple CGI samples exist. This avoids full PHP rewrites but still produces web pages.

Practical paths to choose
PHP-centric: Rebuild UI in HTML/CSS/JS; use PHP for routing and data; simulate windows with modals/panels. Best for long-term web-native UX.

Harbour-centric: Use Harbour as CGI/mod_harbour to generate HTML; progressively enhance with JS. Minimizes language migration at first.

Hybrid: PHP serves pages; Harbour services run behind HTTP APIs, returning JSON that PHP or JS consumes. Useful during phased migrations.

Local testing and serving
Serve pages via a web server (Apache/Nginx) or PHP’s built-in server; access over http://localhost:PORT or LAN IP:PORT, ensuring firewall/port config allows access.

If a concrete translation of a small FiveWin window (title, button, input, event) to PHP/HTML/JS is desired, a focused code sample can be provided that mirrors DEFINE WINDOW/ACTIVATE WINDOW behavior using a modal and click handlers.

IMO, unless you apply AI, it would be a huge and endless effort

And even using AI, there is a lot to supervise, test and fix