Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
From
medium
Many of you have probably heard of Facebook’s React library and used it in your own work or projects. It’s extremely pop…
No comment yet.
Sign up to comment
Scoop.it!
Most modern front-end JavaScript frameworks provide some sort of support for component based development. This is an incredibly important step in the direction of development for the web. Components provide a way to write small parts with a consistent API that can easily be orchestrated as part of a larger screen, application or system. Component based development isn’t just the future of the web, though. It’s what you should be doing now, in any modern UI / application framework on the web.
Scoop.it!
Essence is a CSS framework that implements the guidelines from Google Material Design Specification using Facebook's react.js library. Use it to easily build super-fast and great looking web & mobile interfaces.
Jan Hesse's insight:
Scoop.it!
The component driven, performance focused approach of React is a perfect complement to the modularity and portability of native HTML Web Components. At first glance, React and Web Components might seem like two radically different solutions to the same problem. But when combined properly they complement each other to create an extremely powerful, expressive framework for developing complex web applications.
Scoop.it!
I recently had an interesting conversation with some very smart colleagues on the topic of UI component reusability on modern web frontend applications. This led me to spend a few hours on a lazy Sunday afternoon clarifying my thoughts on the status quo - and the road ahead - of web frontend architectures. Specifically, I find it interesting how the short-term future seems to somewhat contradict the assumed long-term future.
Scoop.it!
This is a collection of some of the most reusable React components built at Khan Academy. In the jQuery ecosystem there's a large collection of plugins that can be used for anything from modals to translation. We're trying to make it just as easy to jumpstart React applications with a well-tested, thoughtful, and beautiful library of components. Most of our components are bespoke, so if you're already invested in a UI framework like Bootstrap, Topcoat, or KendoUI, you should check to see if there's an existing React wrapper for your framework.
Scoop.it!
Today we’ll look at how to wrap React components using Custom Elements, allowing us to interop with Web Component-based libraries using the DOM as a simple configuration API. Similar to libraries like Polymer, React cares about composition, lifecycle events and modularity so seeing how well it fits with Web Components is an interesting thought experiment. As React doesn’t need to take over your whole app and components built with it can comfortably live inside existing ones, you may indeed run into situations where component built with different libraries need to both co-exist and interop.
Scoop.it!
From
github
Lightweight Mozilla X-Tag add-on which allows to use React.js components as custom HTML elements.
|
Scoop.it!
In this project I want to compare the usage and development of components in several frameworks. To test these frameworks I'll create multiple components from simple to complex to show the differences between these frameworks. I currently plan to look into the following frameworks:
Scoop.it!
From
github
Maple.js is a contemporary React based framework mixing ES6 with Custom Elements, HTML Imports and Shadow DOM. It has in-built support for SASS and JSX, including a Gulp task for vulcanizing your project. Maple is a seamless module that allows you to organise your React project in terms of webcomponents — with HTML Imports, Shadow DOM, and Custom Elements — allowing you to implement any Flux architecture you choose, and then compile with Mapleify for production.
Scoop.it!
So why would you want to put a Web Component in an app built with one of these frameworks? Web Components let you create elements that apps can interface with in the same way that they already interface with native elements. That means that a Web Component can be reused anywhere, in any framework. That’s the theory, at least. Let’s try it out. We’ll just be looking at Custom Elements, the heart of Web Components.
Scoop.it!
The component driven, performance focused approach of React is a perfect complement to the modularity and portability of native HTML Web Components. At first glance, React and Web Components might seem like two radically different solutions to the same problem. But when combined properly they complement each other to create an extremely powerful, expressive framework for developing complex web applications.
Scoop.it!
Scoop.it!
An important part of compontent-based development is that components can be composed out of other components. The rich text editor is a great example of this since it will be composed out of buttons, drop downs, some sort of rich view and so on. Another good example is the HTML5 video element which again contains buttons and also an element which renders content from a video data stream.
Scoop.it!
From
github
Cosmos is a JavaScript user interface framework that cares about data clarity and component autonomy. It prevents scaling complexity by enforcing a zero-bootstrap policy and by having data structures dictate code logic and not the other way around. Built on top of Facebook's React, Cosmos glues components together and provides a uniform structure between them. Components are self-contained, UI building blocks.
Scoop.it!
Last week I made a presentation for meet.js PL about React. meet.js is a free front-end meetup organized by web enthusiasts in 6 major Polish cities - Warsaw, Gdańsk, Poznań, Wrocław, Cracow and Katowice. In a nutshell, I presented why we chose React among other available options (ember.js, angular, backbone ...) in AgFlow, where I’m leading an application development. Also I try to highlight some problems with MVC pattern everywhere. I really like a way of React frontend components development. It makes more clear for us to implement use cases views. Enjoy!
|
