framework7-react - npm Package Compare versions

Comparing version 0.8.2-beta-1 to 0.8.2-beta-2

dist/src/components/Framework7App.d.ts

		@@ -37,2 +37,6 @@ import * as React from 'react';
		onRouteChange?: (route: IFramework7Route) => void;
		stateKernel?: {
		setFramework7: (f7: any) => void;
		setRouter: (router: any) => void;
		};
		}
		@@ -39,0 +43,0 @@ export declare class Framework7App extends React.Component<IFramework7AppProps, Framework7> {

dist/src/components/Framework7App.js

		@@ -71,2 +71,6 @@ "use strict";
		});
		if (this.props.stateKernel) {
		this.props.stateKernel.setFramework7(this.framework7);
		this.props.stateKernel.setRouter(this.router);
		}
		};
		@@ -73,0 +77,0 @@ Framework7App.prototype.getFramework7 = function (callback) {

package.json

		{
		"name": "framework7-react",
		"version": "0.8.2-beta-1",
		"version": "0.8.2-beta-2",
		"description": "A React version of Framework7",
		@@ -5,0 +5,0 @@ "main": "dist/framework7-react/index.js",

README.md

		@@ -5,6 +5,8 @@ # Framework7 React

		Note that Framework7 React is still very new, so more complex examples beyond the kitchen sink aren't available yet. In the meantime, if you're new to Framework7, you should have a look at the [full iOS / Material Design kitchen sinks](http://framework7.io), [the demo apps](http://framework7.io/apps/), and [the example layouts](http://framework7.io/examples/) to get a feel for Framework7 and what is possible.

		## Getting started

		```
		npm install framework7-react
		npm install --save framework7-react
		```
		@@ -15,5 +17,34 @@

		## Building + running the kitchen sink

		Ensure that [gulp](https://www.npmjs.com/package/gulp) and [typings](https://www.npmjs.com/package/typings) are installed globally, then run the following:

		To build the framework itself:

		```javascript
		npm install
		typings install
		gulp
		```

		To build the kitchen sink:

		```javascript
		cd kitchen-sink
		npm install
		typings install
		gulp
		```

		Here's a shortcut for building both after the above two steps have already been completed at least once:

		```javascript
		npm run build
		```

		Once the framework and kitchen sink are built, run the kitchen sink by launching kitchen-sink/index.html in a browser.

		## Usage with Redux

		Firstly, as the author of [Redux points out](https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367#.nfg6gm6yl), Redux is not a requirement for building apps with React. In turn, Redux is not a requirement for building apps with Framework7 React—it is designed to be perfectly usable either way. However, as your app grows beyond a certain level of complexity, it is definitely recommended that you consider Redux (or some other state management library like [MobX](https://github.com/mobxjs/mobx)). For more information about using Redux with Framework7 React, have a look at [Framework7 Redux](https://github.com/bencompton/framework7-redux).
		Firstly, as the creator of [Redux points out](https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367#.nfg6gm6yl), Redux is not a requirement for building apps with React. In turn, Redux is not a requirement for building apps with Framework7 React—it is designed to be perfectly usable either way. However, as your app grows beyond a certain level of complexity, it is definitely recommended that you consider Redux (or some other state management library like [MobX](https://github.com/mobxjs/mobx)). For more information about using Redux with Framework7 React, have a look at [Framework7 Redux](https://github.com/bencompton/framework7-redux).

		@@ -28,3 +59,3 @@ ## FAQ

		The short answer is yes, but animated page transitions will not work. It is recommended that you instead use the router that is built into Framework7 React. The goal of the built-in router is to provide everything you need and leave no reason to use React Router. The main missing feature right now is support for the HTML5 History API with the browser back button and URL changes driving route changes, but the router is still a work in progress.
		The short answer is yes, but animated page transitions will not work. It is recommended that you instead use the router that is built into Framework7 React. The router is still a work in progress, but the goal of the built-in router is to provide everything you need and leave no reason to use React Router. One important missing feature right now is support for the HTML5 History API with the browser back button and URL changes driving route changes.

		@@ -41,4 +72,8 @@ #### Should I use React Native or Framework7 React for my project?

		#### Why should I use Framework7 React instead of React library XYZ?

		The main motivation for creating Framework7 React was the lack of React libraries that convincingly recreate the look and feel of iOS and Material in pixel-perfect detail with realistic animations, gestures, etc. If you want the benefits of a web app without having your app look like a web app, then Framework7 React might be a good choice for your project.

		#### I would like to contribute an enhancement or fix to a component, but I don’t see the React component in the code. What gives?

		Given that [Vue](https://vuejs.org) 2.0 and React are incredibly similar, it was decided that Framework7 React would automatically generate its React components from [Framework7 Vue’s](https://github.com/nolimits4web/Framework7-Vue) components. This makes it super easy to keep the two frameworks in sync and ensure that React and Vue users both get access to the same capabilities. In a nutshell, Vue components have `render` methods just like React components do, and just like in React, Vue component render methods call a `createElement` function and return the created elements for the framework to mount in the DOM and reactively update. Therefore, it is relatively simple to leverage the rendering logic in Vue components by substituting React’s createElement function for Vue’s createElement function. That is the basic principle at least. In practice, there is a bit more to it than that. It works surprisingly well, though, and many hours of testing have shown that rendering performance in Framework7 React is more or less equivalent to Framework7 Vue.

dist/src/components/Framework7App.js.map

Sorry, the diff of this file is not supported yet

framework7-react - npm Package Compare versions

Fixed alerts

Improved metrics