Use the same functions and logic you wrote on Windows to make your Swift functions. Do the back end stuff in native code.Ĥ) You can then re-use most of the UI code you wrote to easily port over to macOS. Add this meta tag to the HTML file to ensure the WebBrowser control knows to use new versions of IE to render the UI: (and/or look up how to add the FEATURE_BROWSER_EMULATION registry key)ģ) Use the built in script calling functions to transfer settings back and forth between the UI and main app in JSON. To the user, it'll feel like any other native app. Disable right clicking and highlighting using HTML/JS. NET for Windows and WebView using macOS to display your UI. Instead, use the native WebBrowser control in. Your users WILL notice and complain about performance. If you require a UI that is pretty heavy, here is my pro* tip to save time when developing for both Windows and macOS.ġ) Buy a basic HTML template online for your app's dashboard.Ģ) Don't use Electon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |