Joel de Guzman

> [Windows](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776913(v=vs.85)?redirectedfrom=MSDN) and [macOS](https://developer.apple.com/documentation/appkit/nssavepanel) interfaces are rather rich - what should I be looking at for unix systems? GTK+ 3 API? Yes GTK3 on Linux

> The eventual interface in elements can be a free function that takes 1 parameter: options struct. This way: > > * for each option elements can provide a very...

> This is going to take some time, but I can share my WIP spreadsheet if you want. Google sheet will be good.

Wow, that's a lot! Nice work collecting that. So basically, as always: Start with a minimal subset that is available on all platforms. (BTW. I wonder how you are able...

> I'm not able to test it on mac. I don't even have Obj-C skills. All from the sheet is from API documentation. I will left Mac implementation for you....

> Implementation question: most (if not all) platforms require to hold or pass some platform-specific state to create any modal window. > > Should we make the modal functions members...

It should be standalone. Elements require components that do not require a parent window. It's one of the fundamental requirements. The Element 'window' and 'app' classes are actually optional and...

> It should be standalone. Elements require components that do not require a parent window. It's one of the fundamental requirements. The Element 'window' and 'app' classes are actually optional...

> You might want to look: [02f50e1](https://github.com/cycfi/elements/commit/02f50e1cea77c5547091eab77cc5c05d79241f52) ```c++ auto scale = 1.0; ``` ??? Are you testing on visual studio on a HDPI machine? It will give me a lot...

> 1. I think it would be useful to expose these functions on the public API (on Windows only) Sure, but keep the header private. I usually do it in...