Far better and easier to just use a custom widget toolkit that works consistently across all your target OSes. So many actually-native apps use custom widgets anyway nowadays that your app will hardly look foreign for doing so.
Far better and easier to just use a custom widget toolkit that works consistently across all your target OSes. So many actually-native apps use custom widgets anyway nowadays that your app will hardly look foreign for doing so.
Making the HTML widgets look and behave exactly like native Cocoa components is probably not going to happen, but definitely I can do better than Swing or GTK.
Anyone that has spend a few hours of their life reading either the "Rich Filthy Clients" Sun blog posts or the book that came out of it, should be able to write quite good Java Swing applications.
With CSS even getting something basic like hardware acceleration, is a matter of playing with Z transforms and hopping that the user is running the right browser, with the right version on the right operating system and it will pick up those CSS hints and accelerate them.
Even then, the amount of CSS tricks is limited, because each browser and GPU makes it different and it cannot be queried for.
Technical capabilities are not the obstacle. The problem is that you're trying to reverse engineer and build a faithful emulation of a complex set of software components in a completely different language and runtime. And unlike emulating a legacy system, OS toolkits are a moving target. They get tweaked constantly, and often overhauled completely with each new release.
Anyway, cloning macOS UI is not my primary goal. I just want to build a widget toolkit that could be themed however I want.