FoxDev Studio (mark.png) (https://fonts.googleapis.com) (https://fonts.gstatic.com) (../fonts.googleapis.com/css2@family=Bricolage+Grotesque%253Aopsz,wght@12..96,600%3B12..96,800&family=IBM+Plex+Mono%253Awght@400%3B500&family=IBM+Plex+Sans%253Awght@400%3B500%3B600&display=swap.css) (_astro/nav.Ywq4w9bd.css) (_astro/index.DEArkqbm.css)  (index.html)  FoxDev Studio  (https://foxscript.org/docs) Documentation (index.html#architecture) How it is built (index.html#foxscript) FoxScript (index.html#download) Download (https://github.com/FoxDevCommunity/FoxDevStudio) GitHub   For Visual FoxPro 9 applications   Your FoxPro applications, at home on a modern machine. FoxDev Studio opens the projects, forms and tables you already have and runs them the way you remember: no rewrite, no conversion, no export step . (index.html#download) Download (https://foxscript.org/docs/getting-started) Get started (index.html#architecture) How it is built             Customer     Company  Western Trading Co. Credit limit  25,000.00  Save             It picks up where you left off Point it at a folder you have not opened in years, and what is there is what you get.     Your project, as it is Projects, forms, class libraries, menus and reports open straight from the files you already have. Nothing is migrated first, and nothing is left behind.           The designers you know Forms, classes, menus and reports are edited where you expect them to be, alongside the project manager, the Command Window and a debugger that stops on your line.     Your data stays your data Tables, indexes, memos and databases are read and written in place. What sits on disk afterwards is the same kind of file it was before.       Whatever it talked to, it still talks to The system calls, the automation objects and the old add-in libraries your application leans on keep working, so the parts nobody wants to touch stay untouched.    What it looks like The IDE, on Visual FoxPro's own sample projects. Every picture is a real session.  (screenshots/solution.png) (Visual FoxPro's Solution sample running on the Screen tab: its samples launcher form with an outline of ActiveX, Controls, Databases and Forms samples, beside a project explorer listing the project's forms, menus, programs, class libraries, databases, free tables and reports; the status bar says Waiting for events.) Visual FoxPro's own Solution sample, imported and running: its launcher form on the Screen tab, the project's 123 forms, 7 menus and 11 class libraries in the explorer, and the runtime waiting for events.  (screenshots/editor.jpg) (The program editor with a FormsUI sample open, the linter marking a syntax error inline on a FOR line, and the Output and Command windows below.) The editor lints through the runtime's own compiler, so what it underlines is what would fail.  (screenshots/debugger.png) (The debugger stopped on line 26 of the Solution sample's main program, one step past a breakpoint on line 25: the current line highlighted, and below it the Output window, the call stack, the locals, a watch box and the breakpoints list.) Stopped one step past a breakpoint in the Solution sample's main program: call stack, locals, watches, and the line it is on.  (screenshots/browser.jpg) (The table browser showing the 17 records of a database container, with its memo fields as links, beside a project explorer listing forms, menus, programs, class libraries and databases.) A database container in the table browser: 8 fields, 17 records, memos a click away.  (screenshots/http-server.jpg) (A FoxScript program registering HTTP routes with lambdas, calling a 32-bit encryption library from inside one, and the Output window reporting that the server is listening on port 8080.) FoxScript: lambdas answering HTTP routes, a 32-bit library called from inside one, listening on 8080.    Built to match, not to approximate Small differences are what break an old application: a number printed a column too wide, an event arriving a moment late, an error with the wrong number on it. So behaviour here is settled by asking Visual FoxPro itself and matching its answer, rather than by reading a reference page and hoping. What comes out of that is a runtime written from scratch: quick to start, self-contained, and straightforward about the corners it has not reached yet. 1,722 elements of the Visual FoxPro 9 language reference known to the runtime  1,534 of them exercised by a test that compares the answer with the product's  3 names it has not met yet; everything else runs, is ignored on purpose, or is refused by name     What Visual FoxPro 10 would have been Visual FoxPro stopped at version 9, and at 32 bits. This is the same language, rebuilt on a foundation that has not been frozen since 2007. Four pieces are what make that possible.  Where a call goes / and where the 32-bit world stops     64-BIT 32-BIT   The form on screen React, drawing straight from the tree below  repaints one control, not the form  The live object tree every control, with its properties and its events  THISFORM.lblGreeting.Caption = cMsg  The virtual machine your code, compiled to bytecode, run in WebAssembly  yields a request, never blocks  The host files, tables, COM, and 64-bit libraries in process  SET LIBRARY TO  fllhost.exe a 32-bit process, holding your .fll   64-bit, end to end The ceiling that came with 32 bits is gone Visual FoxPro is a 32-bit program, and that decides more than it appears to. It is why a table stops at two gigabytes, why a memo file stops at two gigabytes, and why a big report runs out of memory on a machine with plenty to spare. The limits are signed 32-bit numbers buried in the file handling, not a licensing decision anybody made. FoxDev Studio is 64-bit throughout . Every file offset is 64-bit and a table is never read into memory at all, so the same .dbf that used to stop dead carries on into the hundreds of gigabytes . One thing to know before you lean on it: a table grown past two gigabytes will not open in Visual FoxPro again. If you still work in both, that is a one-way door. The offset / and what it reaches       Visual FoxPro   2,147,483,647 bytes: the table stops at 2 GB the leading bit carries the sign, which is why it is 2 GB and not 4 FoxDev Studio  9,223,372,036,854,775,807 bytes: the offset is never what stops every byte of every read and write is addressed this way  What that buys one table Every square below is 2 GB: the whole of what a Visual FoxPro table could hold.                                                                                                                                                                                                                                                                                         2 GB 279 squares: one FoxDev table of 130-byte records, 558 GB. At 1 KB records it reaches 4.4 TB, which is 2,200 of them. what stops it now is the DBF header's own record count    The virtual machine A compiler, and a machine built to run what it makes Visual FoxPro compiled your program to p-code and shipped a runtime to execute it. This is the same arrangement, made again: a compiler and a bytecode interpreter written in Rust and compiled to WebAssembly , so one machine runs your code wherever the application runs. The editor checks what you type through that very compiler, so what it underlines and what the runtime refuses cannot drift apart. A running program is a fiber. When it needs something from the world outside (a message box, a modal form, the next record) it does not call out and block; it yields, the work is done while the machine is off the stack, and the answer is handed back. That is why MESSAGEBOX() stops your program without freezing the window behind it, why READ EVENTS waits without spinning, and whySetFocus can fire GotFocus , and Init can run while a form is still being built, in the order FoxPro always did it. (https://foxscript.org/docs/vm) How the machine works and (https://foxscript.org/docs/bytecode) what it runs .  The screen The form you see is the object tree, not a picture of it A running form is a live tree of objects with the properties you would expect, and the interface is drawn straight from that tree by React. Each object watches only itself, so THISFORM.lblGreeting.Caption = cMsg repaints one label rather than the whole form. On a dense screen that is the difference between instant and sluggish. The same tree is what the designer edits, one step earlier. There is no second model kept in step with the first, which is the usual place a form and its designer start telling different stories.  The 32-bit bridge Your old libraries still load, though nothing here is 32-bit An .fll is a 32-bit image, and every process in a 64-bit application is 64-bit, so nothing inside the application itself could ever open one. Rather than tell you it is impossible, SET LIBRARY TO starts a small 32-bit process whose only job is to hold your library , and the runtime talks to it. The calls are synchronous, because a program may call into a library halfway through an expression, and an answer that arrived later would not be an answer. It is measured against real libraries: the encryption library, FoxTools, and libraries built from Microsoft's own API samples. Nothing 64-bit needs the bridge: DECLARE ... DLL reaches a modern library in the same process, and automation objects are reached the way they always were. The old road stays open; it just is not the only one any more.    FoxScript: the same language, with more room Everything you have written still means what it always meant. FoxScript only adds on top: a block you can hand to something else to run later, and a way to answer a web request from the code that already knows your business.  server.prg / FoxScript  && your old add-in libraries load just as before SET LIBRARY TO "vfpencryption71.fll" ADDITIVE LOCAL oServer
oServer = FoxScript.Http.CreateServer()

oServer.Get("/api/v1/customers/:id" , LAMBDA (req, res) LOCAL lnId
    lnId = VAL (req.Params("id" )) SELECT * FROM customer WHERE cust_id = lnId INTO CURSOR c_cust IF RECCOUNT ("c_cust" ) > 0
        res.Status(200).Json(FoxScript.Data.CursorToJson("c_cust" )) ELSE res.Status(404).Json('{"error": "Not found"}' ) ENDIF USE IN c_cust ENDLAMBDA )

oServer.Listen(8080) READ EVENTS     Every line of that runs on the same runtime your forms do. The queries, the cursor and the library call are ordinary FoxPro; the lambda and the server are what FoxScript adds: no second language, no service to stand up beside it.(https://foxscript.org/docs/foxscript) The keywords and (https://foxscript.org/docs/http-api) the HTTP API are each written down in full.  Download The nightly is rebuilt from every push to main and published as a pre-release on GitHub. Unsigned, so the first launch asks you to confirm.  (https://github.com/FoxDevCommunity/FoxDevStudio/releases/tag/nightly)   Windows The installer (.exe ) and the runtime (.zip ), x64.  (https://github.com/FoxDevCommunity/FoxDevStudio/releases/tag/nightly)      Ubuntu and other Linux An AppImage and a .deb , x64.  (https://github.com/FoxDevCommunity/FoxDevStudio)   Source, on GitHub FoxDevCommunity/FoxDevStudio: the IDE, the VM, this site, and every release.    Read the documentation Each part of the product is written down, including the parts that are not there yet.  (https://foxscript.org/docs) Overview What FoxDev Studio is, and where each part of it is described.  (https://foxscript.org/docs/getting-started) Getting started Install the IDE, open a project, run a form, ship an executable.  (https://foxscript.org/docs/tooling) Required tooling What you need to run the IDE, and what you need to build it from source.  (https://foxscript.org/docs/vm) The virtual machine Fibers, host requests, and why the VM never blocks.  (https://foxscript.org/docs/bytecode) Bytecode The module format, how a program compiles, and what a frame holds.  (https://foxscript.org/docs/instructions) Instruction reference Every instruction with its operands and stack effect, generated from the VM source.  (https://foxscript.org/docs/foxscript) The new keywords LAMBDA, ENDLAMBDA, the FoxScript namespace and two new value types.  (https://foxscript.org/docs/http-api) The HTTP API FoxScript.Http, the Node side of it, and why it is shaped this way.    What is coming Work already mapped out, roughly in the order it is being built.  The last of the language A short list of corners is still open, each one checked against the original as it closes.  Reports The report designer and the report engine, band by band, measured the same way the rest was.  Tables past two gigabytes, as a format of their own The 64-bit offsets are there today; a container that is honest about the DBF header's limits comes next.  An installer for what you ship Your application handed to the people who use it as a single thing they can run, with nothing to set up first.    FoxDev Studio is an independent project, and one still growing. The(https://foxscript.org/docs) documentation says where it is and where it goes next. Visual FoxPro is a registered trademark of Microsoft Corporation, used here only to name the language being implemented.