DataType/omi - omi - 红山开源项目托管

Go to file

dntzhang 6d6449234a add omi-element-ui		2018-10-23 06:16:31 +08:00
assets	add logos	2018-10-20 01:30:46 +03:00
docs	Merge pull request #100 from MrGrabazu/patch-1	2018-10-23 00:54:52 +08:00
packages	add omi-element-ui	2018-10-23 06:16:31 +08:00
.editorconfig	standart code styling	2018-10-21 22:56:05 +03:00
.eslintrc	eslintrc (#93 )	2018-10-22 12:39:56 +03:00
.gitignore	add omi-element-ui	2018-10-23 06:16:31 +08:00
CONTRIBUTING.md	standart code styling	2018-10-21 22:56:05 +03:00
LICENSE	standart code styling	2018-10-21 22:56:05 +03:00
README.CN.md	update readme & build	2018-10-23 05:41:20 +08:00
README.md	update readme & build	2018-10-23 05:41:20 +08:00

README.md

English | 简体中文

Omi: Next Generation Web Framework in 4kb JavaScript

Merge JSX, Web Components, Proxy, Store, Path Updating together

Why Omi?

Tiny size. (4kb gzipped)
Supports TypeScript.
Reactive data-binding
Based on Shadow DOM
Easy to debug via Omi DevTools Extension [Install from Chrome WebStore]
Compliance with browser trend and API design.
Merge JSX and Web Components into one framework.
Work well with mobx by omi-mobx (No need to call this.update()).
Web Components can also be a data-driven view, UI = fn(data).
JSX is the best development experience (code intelligent completion and tip) UI Expression with least grammatical noise.
The original Path Updating system. Proxy-based automatic accurate update, low power consumption, high degree of freedom, excellent performance, easy integration of requestIdleCallback
Say goodbye to this.update method when using store system! It will automatically update UI partially when data is changed.
Look at Facebook React vs Web Components，Omi combines their advantages and gives developers the freedom to choose the way they like.
Shadow DOM merges with Virtual DOM, Omi uses both virtual DOM and real Shadow DOM to make view updates more accurate and faster.
With a Store system, 99.9% of projects don't need time travel, and not only Redux can travel, please don't come up on Redux, Omi store system can meet all projects
Scoped CSS's best solution is Shadow DOM, the community churning out frameworks and libraries for Scoped CSS (using JS or JSON writing styles such as Radium, jsxstyle, react-style; binding to webpack using generated unique className filename-classname-hash, such as CSS Modules, Vue), are hack technologies; and Shadow DOM Style is the perfect solution.

Compare TodoApp by Omi and React, Omi and React rendering DOM structure:

Omi	React

On the left is Omi, the right side is React, and Omi uses Shadow DOM based style isolation and semantic structure.

Why Omi?
Add Omi in One Minute
Getting Started
- Install
- Hello Element
- TodoApp
- Store
  - Summary：
- Lifecycle
Component Ecosystem
Debugging
Omi Mobx
Browsers Support
Links
Contribution
License

Add Omi in One Minute

This page demonstrates using Omi with no build tooling.

<!DOCTYPE html>
<html>

<head>
  <meta charset="UTF-8" />
  <title>Add Omi in One Minute</title>
</head>

<body>
  <script src="https://unpkg.com/omi"></script>
  <script>
    const { WeElement, h, render, define } = Omi

    class LikeButton extends WeElement {
      install() {
        this.data = { liked: false }
      }

      render() {
        if (this.data.liked) {
          return 'You liked this.'
        }

        return h(
          'button',
          {
            onClick: () => {
              this.data.liked = true
              this.update()
            }
          },
          'Like'
        )
      }
    }

    define('like-button', LikeButton)

    render(h('like-button'), 'body')
  </script>
</body>

</html>

You can also use like-button tag directly in HTML：

<body>
	<like-button />
</body>

Getting Started

Install

$ npm i omi-cli -g               # install cli
$ omi init your_project_name     # init project, you can also exec 'omi init' in an empty folder
$ cd your_project_name           # please ignore this command if you executed 'omi init' in an empty folder
$ npm start                      # develop
$ npm run build                  # release

Directory description:

├─ config
├─ public
├─ scripts
├─ src
│  ├─ assets
│  ├─ elements    //Store all custom elements
│  ├─ store       //Store all this store of pages
│  ├─ admin.js    //Entry js of compiler，will build to admin.html
│  └─ index.js    //Entry js of compiler，will build to index.html

CLI's auto-created project scaffolding is based on a single-page create-react-app to be converted into a multi-page one, with configuration issues to see create-react-app user guide

Hello Element

Define a custom element by extending WeElement base class and name it using @tag decorator:

import { tag, WeElement, render } from "omi";

@tag("hello-element")
class HelloElement extends WeElement {
	onClick = evt => {
		// trigger CustomEvent
		this.fire("abc", { name: "dntzhang", age: 12 });
		evt.stopPropagation();
	};

	css() {
		return `
        div {
          color: red;
          cursor: pointer;
        }`;
	}

	render(props) {
		return (
			<div onClick={this.onClick}>
				Hello {props.msg} {props.propFromParent}
				<div>Click Me!</div>
			</div>
		);
	}
}

Using hello-element:

import { tag, WeElement, render } from "omi";
import "./hello-element";

@tag("my-app")
class MyApp extends WeElement {
	static get data() {
		return { abc: "", passToChild: "" };
	}

	// bind CustomEvent
	onAbc = evt => {
		// get evt data by evt.detail
		this.data.abc = ` by ${evt.detail.name}`;
		this.update();
	};

	css() {
		return `
      div {
        color: green;
      }`;
	}

	render(props, data) {
		return (
			<div>
				Hello {props.name} {data.abc}
				<hello-element
					onAbc={this.onAbc}
					prop-from-parent={data.passToChild}
					msg="WeElement"
				/>
			</div>
		);
	}
}

render(<my-app name="Omi v4.0" />, "body");

Tell Babel to transform JSX into Omi.h() call:

{
	"presets": ["env", "omi"]
}

The following two NPM packages need to be installed to support the above configuration:

"babel-preset-env": "^1.6.0",
"babel-preset-omi": "^0.1.1",

If you don't want to write CSS in JS, you can use to-string-loader, For example, the following configuration:

{
  test: /[\\|\/]_[\S]*\.css$/,
  use: [
    'to-string-loader',
    'css-loader'
  ]
}

If your CSS file starts with "_", CSS will use to-string-loader., such as:

import { tag, WeElement render } from 'omi'

// typeof cssStr is string
import cssStr from './_index.css'

@tag('my-app')
class MyApp extends WeElement {

  css() {
    return cssStr
  }
  ...
  ...
  ...

TodoApp

Here is a relatively complete example of TodoApp:

import { tag, WeElement, render } from "omi";

@tag("todo-list")
class TodoList extends WeElement {
	render(props) {
		return (
			<ul>
				{props.items.map(item => (
					<li key={item.id}>{item.text}</li>
				))}
			</ul>
		);
	}
}

@tag("todo-app")
class TodoApp extends WeElement {
	static get data() {
		return { items: [], text: "" };
	}

	render() {
		return (
			<div>
				<h3>TODO</h3>
				<todo-list items={this.data.items} />
				<form onSubmit={this.handleSubmit}>
					<input
						id="new-todo"
						onChange={this.handleChange}
						value={this.data.text}
					/>
					<button>Add #{this.data.items.length + 1}</button>
				</form>
			</div>
		);
	}

	handleChange = e => {
		this.data.text = e.target.value;
	};

	handleSubmit = e => {
		e.preventDefault();
		if (!this.data.text.trim().length) {
			return;
		}

		this.data.items.push({
			text: this.data.text,
			id: Date.now()
		});
		this.data.text = "";
		this.update();
	};
}

render(<todo-app />, "body");

Store

Say goodbye to this.update method when using store system! It will automatically update the UI partially when data is changed. The powerful Store architecture is high-performanced since all the data is mounted on the store, except for components that rely on props to determine the state of the component.

export default {
	data: {
		items: [],
		text: "",
		firstName: "dnt",
		lastName: "zhang",
		fullName: function() {
			return this.firstName + this.lastName;
		},
		globalPropTest: "abc", // Change it will refresh all elements without changing the components and page declaring data dependency.
		ccc: { ddd: 1 } // Change it will refresh all elements without changing the components and page declaring data dependency.
	},
	globalData: ["globalPropTest", "ccc.ddd"],
	add: function() {
		if (!this.data.text.trim().length) {
			return;
		}
		this.data.items.push({
			text: this.data.text,
			id: Date.now()
		});
		this.data.text = "";
	}
	// Default value is false, set to true will update all instances when data changing.
	// updateAll: true
};

Custom Element requires declaring dependent data so that Omi stores compute the dependency path based on the data declared on the custom component and update it locally as needed. Such as:

class TodoApp extends WeElement {
	// If you use store, the data is only used to declare dependencies.
	static get data() {
		return { items: [], text: "" };
	}
	// ...
	handleChange = e => {
		this.store.data.text = e.target.value;
	};

	handleSubmit = e => {
		e.preventDefault();
		this.store.add();
	};
}

The logic of data is encapsulated in the store definition method (such as store.add).
Views are only responsible for passing data to store, such as calling store.add or setting store.data.text on top.

You need to inject store from the root node at render time to use this store:

render(<todo-app />, "body", store);

→ Store Source Code

Summary：

store.data is used to list all attributes and default values (except the components of the view decided by props).
The static data of the element is used to list the attributes of the dependent store.data (Omi will record path) and update on demand.
If there are few simple components on the page, updateAll can be set to true, and components and pages don't need to declare data, and they don't update on demand
The path declared in globalData refreshes all pages and components by modifying the value of the corresponding path, which can be used to list all pages or most of the public properties path

Lifecycle

Lifecycle method	When it gets called
`install`	before the component gets mounted to the DOM
`installed`	after the component gets mounted to the DOM
`uninstall`	prior to removal from the DOM
`beforeUpdate`	before `render()`
`afterUpdate`	after `render()`

Component Ecosystem

I believe you can easily convert web components elements to omi elements.

Debugging

Using Omi DevTools you can simply debug and manage your UI without any configuration. Just install and debug.

Since Omi uses Web Components and Shadow-DOM, it doesn't need to have another elements panel such as React or Vue has. It just adds a panel to the Elements' sidebar and it's powerful as much as React and Vue DevTools.

Omi Mobx

You can also give up the store system and use omi-mobx to create response views, such as:

import { tag, WeElement } from "omi";
import { observe } from "omi-mobx";

@observe
@tag("my-app")
class MyApp extends WeElement {
	install() {
		this.data.name = "omi";
	}

	onClick = () => {
		this.data.name = "Omi V4.0";
	};

	render(props, data) {
		return (
			<div onClick={this.onClick}>
				<h1>Welcome to {data.name}</h1>
			</div>
		);
	}
}

Browsers Support

Omi 4.0+ works in the latest two versions of all major browsers: Safari 10+, IE 11+, and the evergreen Chrome, Firefox, and Edge.

→ Polyfills

If you want to be compatible with IE11, use the Omi file of → this project. This project uses JSON Diff + Timer instead of Proxy.

You can dynamically load the JS of this project in the IE11 environment, and the proxy version is still used in other environments.

You can also give up the store system and use omi-mobx to be compatible with IE11.

Contribution

Fork it (https://github.com/Tencent/omi/fork)
Create your branch (git checkout -b my-urgent-hotfix)
Commit your changes (git commit -am 'Fixed something')
Push to the branch (git push origin my-urgent-hotfix)
Create a new Pull Request

Please contact us for any questions:

@f
@dntzhang

README.md Unescape Escape