Migrating to React 0.14 and simplification

[mikaelbr]

Great news! The latest React changes plays beautifully with Omniscient.js! By using Reacts stateless functions, Omniscient can be added without changing anything and just work as memoizaltion of your functional views.

Additionally, this transition means there is no difference between non-JSX and JSX. We no longer need to handle JSX explicitly.

This PR does the following:

• Removes documentation for and implementation of and statics in shouldComponentUpdate. Instead, use a ignore higher order component. There is still support for defining your own isIgnorable but it is undocumented, and deactivated by default.
• Removes .jsx and .withDefaults({ jsx: true }). No longer needed!
• Removes omniscient/native and React Native optionalDep. No longer needed with the separation of React and React-dom.

What remains

• Rewrite and simplify documentation. Do a complete overhaul to show the simplicity behind the architecture (functional UI, one way communication, stateless, optimized through memoization). One can write normal React components and simply wrap in Omniscient component to get improved performance, with almost zero effort!
• Anything more? This will be a breaking change, so we should think hard about if there are any other changes that makes sense.

[mikaelbr]

There's also this:

• Check out Reordering items in list cursor will confuse updates on captured items. #89 and think if we need to have a goto-solution for best way for "talking back to parents".

Something you want to check out / champion, @torgeir?

[dashed]

@mikaelbr @torgeir Do you have an idea of an idiom to solve #89?

redbadger/immutable-cursor#5 presents some ideas which may be of interest.

---

Also, one idea I like to throw around is to encourage the practice of not passing cursors to the components. And instead have a reducing function that will resolve cursor props into "immutable" props which will then be passed to the wrapped components.

Something like:

var Greet = component(function (name){
  return React.DOM.div({}, 'Hello from ' + name);
}, {
    propTypes: {
        name: React.PropTypes.string.isRequired,
    },
    assignNewProps({guestCursor}) {
        return {
            name: guestCursor.get('name', '')
        };
    }
});

I found this to relieve the cognitive load of keeping track of cursor state, and ensure invariants (e.g propTypes) are well kept on every component render.

[torgeir]

@mikaelbr This looks good! Loving that the path of react is aligning with that of omniscient :)

Additionally, we need a way to handle event handlers - to look into the delegate/delegee-stuff that operates on statics today to keep event handlers up to date even if components don't have their render called (introduced in https://github.com/omniscientjs/omniscient/issues/67)¨

As far as I remember, there's no immediate resolution to #89 (without relying on keypath), as two cursors pointing to the same data in separate structures (keypaths) are not considered equal. Without cursors this behaves pretty much like what you'd expect.