fw:mpa: a multi-page WebApp and website framework.
fw.mpa is designed to be a real-time web framework suitable for both apps and websites. It minifies the differences of the structure of web-apps (including Cordova apps) and websites.
The key idea of this framework is preventing page reloading when page switches. It's slightly similar to PJAX, but the framework manages the browser history and providing an page model that is easy to understand.
Currently, fw.mpa requires node.js on server side, and works on major browsers. It also provides simple database binding, and i18n support.
Apps and websites based on fw.mpa should follow a Parent/Child page model. This model splits a page into several sub-pages with parent and child relationships. A legal page address is pointed to a child-most sub-page, and every sub-page may have a "parent" sub-page. Parent sub-pages always init before child sub-pages. When a child sub-page need to be switched to another child sub-page, the parent sub-page is not rebuilt.
Here is a clear example to show how this page model works.
- The framework keeps a stack which contains the current sub-pages. When framework inits, the stack is inited empty.
- The page address is pointed to sub-page C. C's parent is B, and B's parent is A. Then A is inited first and pushed into the stack.
- When A is fully loaded and inited, B follows.
stack: [A, B]
- When B is fully loaded and inited, C follows and the whole page is loaded.
stack: [A, B, C]
- Later, a page switching is required (e.g. user clicked an button). The new page address is pointed to D. D's parent is A. Then C in the stack is poped and unloaded.
stack: [A, B]
- B is also unloaded.
- A is D's parent, so A is not changed. D is loaded and inited, and the whole page is loaded.
stack: [A, D]
The cooperation of sub-pages in a web page is not defined by the framework. A clear way is that parent/child sub-pages control parent/child nodes in DOM tree.
fw.mpa is a real-time framework. It means that live connections are kept between servers and browsers. There are two ways of communication between servers and browsers: RPC and server events.
- RPC: the client can make calls to functions on servers, and can get result when needed.
- Server events: the server can push messages to clients.
A live connection is built automatically when a sub-page is inited. If disconnected unexpectedly, a new connection will be built for the sub-page.
fw.mpa uses sockjs as low level connector. It means that Websockets is used when available, and almost all browsers are supported including IE6.
- Configuring Framework
- Configuring App
- Basic Directory Binding
- Client Coding
- Basic Routing
- RPC Functions
- Running Apps
- Multi-Apps in One Instance
- Client Moduling Suggestions
- Using Templates
- I18n Support
- Sessions and Database Binding
- Real-Time Server Messages
- Server Modules
- Special Pages
- Server Side Rendering
- Packaging WebApps
- Version Management
- Advanced Directory Binding
- Advanced RPC
- Client Submodules
- Advanced Routing
- Client Loading Features
- API List
- Full Framework Configuration Options and Default Values
- Full App Configuration Options and Default Values
The MIT License (MIT)
Copyright 2014-2015 Fu Boquan (LastLeaf), MIT License.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.