In Embarcadero's Delphi XE 2 folder you can look at "FMX.Context.Mac.pas", which has the initialization code for Mac.
I've written about this before. The curious thing is that they use latest headers for Mac but outdated OpenGL headers on Windows. My guess about using DirectX is probably the compatibility. For OpenGL to work nicely you need to use latest video drivers, which inexperienced users will rarely have. For instance, my partner's relatives have Eee PC which has stock drivers in Windows XP and OpenGL applications run in software mode, while Direct3D has no problems (though it is still buggy somewhat).
As I've said before, FireMonkey is no match for VCL or even LCL, and it seems to be in infant stages. However, it does have benefits, especially if they use it to its full potential.
Sorry, but you are not being objective. Your opinion seems to be biased towards OpenGL, which in no way better than DirectX and you can't do more with it. Both are just APIs to the underlying hardware, nothing more. In fact, on new Windows installation you'll most likely DO LESS with OpenGL, because on Vista/7 you are stuck with OpenGL 1.4 when using Microsoft drivers, while DX10/11 is still readily available.
I seriously doubt it that FireMonkey will be forgotten any time soon. But I do think you should read the source code first (since documentation for FireMonkey is nonexistent) before making such immature claims.
You *do* have access to low-level API functions in FireMonkey, both in OpenGL and DirectX. First, you can use their TContext3D, which contains most low-level API functions wrapped. Look for "FMX.Context.DX9.pas" and "FMX.Context.Mac.pas" specifically. Second, you can just hook into Direct3D/OpenGL to use them directly, exactly as Asphyre does it.
Bookmarks