You gotta be kidding right?
"ARM based superphone N900 running the x86 wine binary via a statically compiled arm qemu binary, within an x86 chroot."
So it's an ARM-based emulator of an entire PC (presumably a Linux based PC), running a Wine program which is emulating Windows programs. It's running like a stunned sloth as it is and they don't show *anything* complicated running at all. The second video shows a program - Progman.exe - that is from Windows 3.1 and just needs to display a couple of windows with a close button... it used to run BLINDING fast even on just an old 386. Watch the video, they can't even run that fast enough to have a click/drag recognised.
This is one of those "I do it because it's possible" projects that will never have any practical use whatsoever. You're emulating at least two ENTIRE layers within that single "test" - first is emulating every single bit of hardware of a PC (with a program with which my Dual-core can barely match 486/Pentium speeds unless I enable native acceleration - which you *can't* do on ARM), next is running that to the point of having a working Linux machine emulated, next is ON THAT EMULATED LINUX MACHINE running Wine which can add anything up to 50% more processing to every task you want to do even on a modern, native dual-core desktop.
If you really want to wait for about 30 minutes for a basic Windows program to load up, feel free. If you want to double-click, any two clicks within about 2 minutes of each other would probably be recognised as a double-click, the software is running so slow.