![]()
Resize image in purebasic code#In addition, you will also get bug reports about your app being broken on some windows installations but not others and you will spend way too much time trying to figure out the issue, only to come to the conclusion that you can't really do anything other than change your code back to the older feature-set. That means they will quickly fall behind from the current latest Chromium, and will throw bugs at some point in the future, when you rely on newer Chromium features. In addition, while Windows may now have an up to date version of Edge based on Chromium, which it now uses to render it's webviews, do you know that these Edge installations are not auto updated like Chrome/Firefox for Enterprise installations? (Can't seem to find a link, will add one later). There have been instances where the native webview on MacOS had bugs that were not resolved until the next major release of OSX. Resize image in purebasic mac#This is just too much work and will end up diverting attention from developing core features of your app to fixing rendering bugs instead.Īctually this is not just a Windows issue, it's also something that impacts Mac OS. Primary reason for this is that these webviews are only updated with OS updates.Įnd result is you will have to bend over backwards to get your UI working as expected on all these native webviews. Basic things that would work in IE10 are known to break on desktop webviews. Most native webview components lag behind the embedded chromium instance Electron uses by a lot. Sorry for yelling, but that really is that terrible an idea. DO NOT USE A NATIVE WEBBROWSER CONTROL FOR YOUR DESKTOP APP's UI. And in a vast majority of cases the response to that question is going to be 'No'.īut the second part of this comment, I disagree with even further. Instead you should ask if your users would care that it uses Electron, and more whether they would be sufficiently put off to look for alternatives. Whether or not your user's will notice is debatable in itself, but you shouldn't really factor that into your decision making. Resize image in purebasic how to#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) 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. Resize image in purebasic software#I've also seen a number of other expensive, high-end, "professional" software using the FEATURE_BROWSER_EMULATION registry key trick. * I've been making a living from building/maintaining my desktop application for about 5 years and had no regrets setting it up this way. 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. 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 |