I’ll log a ticket to look at supporting union records in Delphi Compatibility Mode. i thought we did, but apparently no.
Logged as bugs://E27632.
I’ll log a ticket to look at supporting union records in Delphi Compatibility Mode. i thought we did, but apparently no.
Nice!
I can’t keep track of the tickets because I don’t have a license yet.
And I can’t update because I believe I don’t have the license either. When this version with this adjustment comes out, I will download a new trial version.
Can you mark here when these bugs have been fixed?
Is there any way to follow your bug tracker without having an active license? Because I will only be allowed to purchase licenses if I prove that I can compile the Delphi sources into Web Assembly.
You will see updates here in theforum when tracked issues get closed
Any news?
is still open, i’m afraid. i’ll chase up with the team if we can five this some prio.
Hi. We’re still working on this! Currently, our goal is to get Spring4D building - it’s a complex, high difficulty Delphi codebase. We’re finding all sorts of language quirks.
Compiling the VCL and FMX is a likely next goal.
We’re making a lot of progress, and our Delphi compatibility mode (with the legacy preprocessor) can handle a lot more Delphi code currently, but it’s not there yet.
In my view, FMX and the VCL will likely be easier targets. We’ve chosen Spring because it’s the most difficult codebase we know of and we want very high compatibility.
For FMX, I believe there’s a system of interfaces and backends so that you can write alternate implementations of the fundamentals for various platforms (Windows, macOS, Android, etc.) I would expect that when building for WASM, that WASM be regarded as one of these platforms. Technically WASM doesn’t need to be attached to a browser, so surfacing UI in the browser would be a wasm-in-browser platform. So there will definitely be some manual coding to do.
Thanks for the reply!
For FMX, I believe there’s a system of interfaces and backends so that you can write alternate implementations of the fundamentals for various platforms (Windows, macOS, Android, etc.) I would expect that when building for WASM, that WASM be regarded as one of these platforms. Technically WASM doesn’t need to be attached to a browser, so surfacing UI in the browser would be a wasm-in-browser platform. So there will definitely be some manual coding to do.
Exactly! But my objective is to put a FMX application in the browser.
So, I’m still waiting!
That’ll be a long wait 