Thinking about React 15 support

[tbranyen]

I'd like to help contribute migrating this project to React 15, and I think we could greatly reduce the amount of code necessary. For instance, right now the code is doing a ton of dependency injection since we don't have screen in scope. What if this library looked something like this instead?

import React, { Component } from 'react';
import blessed from 'blessed';
import { Element, Box, render } from 'react-blessed';

export default class TerminalApp extends Component {
  render() {
    return (
      <Element>
        <Box width="100%" height="50%" top="0%">Top</Box>
        <Box width="100%" height="50%" top="50%">Bottom</Box>
      </Element>
    );
  }
}

const screen = blessed.screen({
  autoPadding: true,
  smartCSR: true,
});

render(<TerminalApp />, screen);

[DxCx]

hey @tbranyen any update on this?

[abritinthebay]

This is a much nicer interface

[Delapouite]

The focus can also be on React 16 now.

[geyang]

this would be nice. A provider component is the way to go!

[Yomguithereal]

The way I see it is the difference is that you explicitly require elements' dependencies. While I see the point, I find it a bit weird. You don't do:

import {div, br, table} from 'react-dom';

for instance, to load the driver's primitives.

The distinction enables you to separate primitives from components, no?

[tbranyen]

If it's easy to make that work, then I agree with that feedback. I'm actually really needing this now for a project at work so I can put some time into make it work the way I proposed. If you have some tips on how to preload React with those components so it works like react-dom does, then I'd be happy to do it that way.

[Yomguithereal]

If you have some tips on how to preload React with those components so it works like react-dom does.

I don't understand what you mean. This is already the case. Tou don't have to "preload" the components, they are not components but primitives.