Proton Native – React Native for the desktop

Post by pjmlp » Thu, May 03, 2018, 9:12 AM UTC

flukus wrote: post #243

pjmlp wrote: post #224

Earlier quoted context omitted.

Because of productivity, and UI/UX workflows while prototyping. Why should I spend 30 coding something away that is doable in a few seconds with a couple of mouse clicks? It is not good to generalize, but most coders I have meant without any sense of UI design never used graphical tooling for doing UIs.

> Why should I spend 30 coding something away that is doable in a few seconds with a couple of mouse clicks? Because maintainability is more important than instant gratification. If you can do both then great, but IME visual designers are a maintenance headache.

Post by superrad » Thu, May 03, 2018, 9:54 AM UTC

mherrmann wrote: post #249

bb101 wrote: post #248

Earlier quoted context omitted.

Doesn't QT cost $459 per month per developer[1] for use in commercial applications? That price is prohibitive for anyone but established enterprise. [1] https://www1.qt.io/buy-product/

No. In many cases, you can use Qt under the LGPL and thus for free. This is especially true when you use it via Python bindings such as PyQt.

Post by mlsarecmg » Thu, May 03, 2018, 10:04 AM UTC

westoncb wrote: post #245

mlsarecmg wrote: post #244

Earlier quoted context omitted.

This seems like a misunderstanding of what React is. JSX is not a template. It is a DSL or superset with direct access to the presentational layer. It gets "transpiled" away in the building phase. React components are not imperative but declarative, they reflect state instead of inflating layout. Layout inflating (QT, Android), MVC/MVVM (XAML), and views being functions of state (React) are paradigm changes. View = f…

There is no reason you couldn't use the example QML above in place of JSX and still receive the same benefits. It would still be `View = fn(state)`; it's just a different syntax for specifying `fn`.

    const A = ({ text }) => {text}
    const B = () => 

     // -> hello

    const canBeDisabled = Component => props => props.disabled ? null : 
    const ComposedB = canBeDisabled(B)

     // -> hello
     // -> null

    class C extends Component {
        state = { count: 0 }
        up = () => this.setState(state => ({ count: state.count + 1 })
        render() {
            return {this.state.count}
        }
    }

     // -> 0, clicks count up reactively

Post by mighty_bander » Thu, May 03, 2018, 10:41 AM UTC

richard_todd wrote: post #168

sjmulder wrote: post #165

Earlier quoted context omitted.

On Windows 10, Notepad uses 2 MB and Wordpad 12 MB. I'm quite surprised that the latter can fit a full, Ribbon equiped word processor in so little memory. Not that I'd be concerned about a few tens of MB nowadays but on the whole we're consuming computing resources at the same rate faster hardware is put out (Gates' law). I have a Pentium 3 running NT4 sitting on the same desk and it is faster at many tasks than my i…

I recently experienced Visual Studio 6 in a Win2k VM, and it was sickening how fast it was compared to modern tools. Same with Office2k apps, and all using an order of magnitude less memory. There has to be a better way than the path we are on, software-wise.

Post by jventura » Thu, May 03, 2018, 11:03 AM UTC

zengid wrote: post #2

This runs on libui-node, which is a binding to the libui library. https://github.com/parro-it/libui-node https://github.com/andlabs/libui