re-component v0.0.2

Re-Component

React components redefined.

This module separates component view render and logic while preserving its context, allowing to create new component model structure similar to other frontend frameworks.

Install

$ npm install --save re-component

Usage

Let's try to separate the concerns: mainly we have this logic and view.

// index.js
import component from 're-component';
import MyComponentLogic from './MyComponentLogic';
import MyComponentTemplate from './MyComponentTemplate.jsx';
import './MyComponentStyles.css';

// no, I want you to create it in css not here. Ok fine.
myComponentCustomStyles = {
  padding: 0;
  marginTop: '10px';  
}

export default component({
  logic: MyComponentLogic,
  template: MyComponentTemplate,
  styles: MyComponentCustomStyles, // oh you want some custom styles ?
});

Component Restructure

Ok. Use separation of concern, not really. I just want to feel it like it should be!

├── views
│   ├── MyComponent                 # Your awesome component.
│   │   ├── index.js                # Entry point  for your component as a whole
│   │   ├── MyComponentLogic.js     # Your logic here.
│   │   ├── MyComponentTemplate.jsx # Your template here.
│   │   └── MyComponentStyles.css   # Your css

Rules on creating each files

Not really. But it's simple. 1. You can remove your render method in your logic. This can make it for you. 2. Heard about arrow functions are already bound to its scope? but we want our react templates to still access it's own context (this) like we normally do. Yes, I want you to use normal function

```
import React from 'react';

export default function (props) { // please do
  // this - you'll get everything from the logic
  // props - ah normal props, but you can get it also from the context.
  return (<div></div>)
};
```

This idea has issues. Let me know what you think.