Skip to content

Latest commit

 

History

History
executable file
·
86 lines (62 loc) · 3.47 KB

README_EN.md

File metadata and controls

executable file
·
86 lines (62 loc) · 3.47 KB
Raw

Epage

A schema-based visual page configuration tool. Forms, pages, etc. can be configured based on popular front-end component libraries.

English Introduction | 中文介绍

Documents

Official website: http://epage.didichuxing.com

Demo

Install

# install vue vuex iview vuedraggable in advance
npm install epage -S
# or yarn add epage

Release

  This repository is the core dependency of the designer and renderer. To view the change log, please visit CHANGLOG. For more renderer andd other open source code, see: https://github.com/epage-team。

Usage

import { render } from 'epage-core'
import Epage from 'epage'
import pcWidgets, { entry as PCEntry } from 'epage-iview'
import h5Widgets, { entry as H5Entry } from 'epage-vant'
import 'iview/src/styles/index.less';
import 'vant/lib/index.less'
import 'epage/src/style/main.less'
import 'epage-iview/src/style/main.less'
import 'epage-vant/src/style/main.less'


const el = document.getElementById('root')
// Instantiate Designer. Render is the renderer. widgets is the widget to be registered
// About Render and widgets can visit https://github.com/epage-team/epage-iview
const config = {
  el,
  pc: {
    widgets: pcWidgets,
    Render: render.VueRender,
    component: PCEntry
  },
  // Only needed when the mobile terminal is designed at the same time
  h5: {
    widgets: h5Widgets,
    Render: render.VueRender,
    component: H5Entry
  }
}
new Epage(config)

more usage CHANGELOG#v0.7.0

Design Concepts

Describing page functions, presentations, and interactions in a schema way, generating the schema in a visual way and ultimately generating the expected page.

The project originated from the process form scenario. The custom development of each form is too costly and poorly maintainable. The most important thing is that the implementer wants to configure the generated form by visual means. Based on such a scenario, during the development process, we found that the form scenario is very similar to some other pages (such as list pages, detail pages, chart reports, etc.) from a certain perspective, and should be configured visually to reach the component Reuse, flexible configuration, easy maintenance, etc. Of course, in the process of using, we found that the complexity of the business is far from being covered by the basic components, so we need to have strong extensibility in order to customize the business components. Some projects even use different front-end frameworks   Earlier in the development of epage, we carried out the design based on the native dom node rendering, so that the designer and the renderer were separated to achieve multiple designs at one time. How to develop widget?

Communication Group

QQ group( 1128074461 )

License

MIT