[HN Gopher] Show HN: Proton Native V2 - Create Cross Platform De...
       ___________________________________________________________________
        
       Show HN: Proton Native V2 - Create Cross Platform Desktop Apps with
       React
        
       Author : kusti8
       Score  : 39 points
       Date   : 2020-01-19 15:25 UTC (7 hours ago)
        
 (HTM) web link (proton-native.js.org)
 (TXT) w3m dump (proton-native.js.org)
        
       | stevesimmons wrote:
       | > Currently, Proton Native is headed by one high school senior
       | with not enough time.
       | 
       | Well done!
        
       | sansnomme wrote:
       | See also: https://github.com/tauri-apps/tauri
        
         | jbverschoor wrote:
         | That uses webviews.
        
       | kusti8 wrote:
       | Proton Native is a way to make cross-platform desktop apps with
       | React, without using Electron or any sort of web browser. Your
       | React code gets translated into Qt or wxWidgets API calls and
       | runs directly on the machine.
       | 
       | After a long time, Proton Native V1 was starting to show it's
       | age. So I ended up making a complete rewrite that includes a lot
       | of the most requested features including flexbox, styling, hot
       | reloading, and components with the same API as React Native.
       | 
       | For those of you who value native components, I've also been
       | working on an experimental wxWidgets backend. There are only a
       | few components, but I hope to implement all the components of the
       | Qt backend soon.
       | 
       | Let me know of any questions you have and thanks!
       | 
       | Previous discussion:
       | https://news.ycombinator.com/item?id=16978901
        
       | newsbinator wrote:
       | Well done! I'd love to see something like this for VueJs.
        
       | satvikpendem wrote:
       | I've been tinkering with React Native and it looks like you can
       | do something quite similar to Proton Native here, while also
       | targeting mobile platforms. Here is how you can cover the gamut
       | of platforms:
       | 
       | - iOS and Android - React Native - Web - React Native Web - macOS
       | - Apple's Project Catalyst (run iPad apps on macOS) - Windows -
       | React Native Windows by Microsoft - Linux - none yet, you could
       | use Electron but that's undesirable
       | 
       | Perhaps one could instead use Proton Native for desktop and React
       | Native for mobile, I wonder what the code sharing capabilities
       | are for that.
        
       | Klonoar wrote:
       | > But those components are not native, meaning they are drawn by
       | Qt instead of using the components provided by the OS.
       | 
       | In the case of macOS, this is no longer true - when Apple finally
       | kicked Carbon fully, Qt (IIRC, in 5.13 or something? 5.12 and
       | prior used HIThemes, which was... showing age) switched to
       | rendering true AppKit behind the scenes. There's a few custom
       | controls where they render their own, if no AppKit equivalent
       | exists, but otherwise it's AppKit all the way down.
       | 
       | As someone who used to decry Qt as not native, I'll be the first
       | to admit it's fine now - if something looks "off" on macOS, it's
       | probably moreso the implementing the author doing something
       | different than the underlying framework.
        
       ___________________________________________________________________
       (page generated 2020-01-19 23:00 UTC)