JSX support has officially landed in TypeScript! A big thanks to Ryan Cavanaugh and François de Campredon for making this happen. In this post I want to explore how to use JSX and how to make use of TypeScript's #1 feature: static type checking.
WebRx is a browser-based MVVM-Framework that combines functional-reactive programming with declarative Data-Binding, Templating and Client-Side Routing.
Microservices are becoming more and more popular and many are choosing to transition away from monolithic architecture. However, this approach was mostly limited to back-end services. While it made a lot of sense to split them into smaller independent pieces that can be accessed only through their APIs, same did not apply to front-end. Why is that? I think that the answer lies in technologies we’re using. The way we are developing front-end is not designed to be split into smaller pieces.
Data bindings in ReactJS required much more code than in AngularJS, so we build a component to help. This post explains how to create deep-path data bindings quickly in ReactJS.
The move to React was great—we’ve enjoyed working with it and it has helped us accomplish our goals quickly. However, since our tech team comes from a background in AngularJS, we found React’s data bindings to be much less convenient.
Data bindings in React required us to code separate ‘binding’ methods, which we weren’t used to with its counterpart, Angular. In Angular, we would simply add a model attribute to our components and the job was done.
One of the many benefits of React is its ability to render components on both client and server. This tutorial aims to teach you how to create isomorphic apps using React and Flux architecture. We will also create a simple blogging app to understand how exactly Flux and React fit together.
The presentation is designed for developers with all levels of experience, from those who had never heard of Angular before to those who are advanced Angular developers and want to learn how to integrate KendoUI.
I also posted the full slide deck and source code that I used in the presentation to GitHub.
I’m going to share how we transitioned to Flux and give some insight into why each part of the architecture is valuable. I’ll also show a couple examples similar to real problems we faced here at Kapost. I do assume the reader has some knowledge of React, a rough idea of what Flux is, and doesn’t mind reading a lot of code. If you are unfamiliar with React and Flux, check out the React documentation and the basic introduction to Flux. (Unfortunately the Flux docs are like a shoddy professor—giving a vague lecture and basic example, then running off and expecting you to solve the hard problems with no office hours.) I’ll try to explain the parts in more detail below.
#0 Series Introduction - AngularJS For Everyone #1 Two-way Data Binding - AngularJS For Everyone #2 Repeating Over Data With ng-repeat - AngularJS For Everyone #3 Basic Filtering In Angular - AngularJS For Everyone #4 Our First Controller - Angular For Everyone #5 Adding A Form Event - Angular For Everyone #6 Controller As Syntax - AngularJS For Everyone #7 Using Filters In Angular Templates - AngularJS For Everyone #8 Conditional Classes With ngClass - AngularJS For Everyone #9 ngIf vs ngShow & ngHide - AngularJS For Everyone #10 Properly Including Images With ngSrc - AngularJS For Everyone #11 Including Templates and Inline SVG with ngInclude - AngularJS For Everyone #12 Adding External Modules - AngularJS For Everyone #13 Animating With Angular Part 1 - AngularJS For Everyone
In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed directly into source or machine code. It is a description or template for how to solve a problem that can be used in many different situations. Patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.
The 23 Gang of Four (GoF) patterns are generally considered the foundation for all other patterns. They are categorized in three groups: Creational, Structural, and Behavioral. This small web application explains these patterns and gives examples on how you can use these patterns in TypeScript.
Now, I cannot possibly do a better job explaining this than Victor Savkin already has in his article: Angular 2 Template Syntax, so I am not going to try. I highly encourage you to go take a look at that article to get an in-depth explanation of the new data binding and template syntax within Angular 2.
Instead, what I want to focus on is the 90% case, and the implications that has in terms of how you build your applications.
Scala.js opens a big world of frontend development to Scala fans. Most of the time Scala.js project ends up being an independent browser or Node.js application. But there are cases, where you would want to make a library for general frontend developers.
There’re some interesting gotchas in writing Scala.js library such way, that it will be natural to use for an average JS developer. In this article we will develop a simple Scala.js library (code) to work with Github API and will focus on the idiomaticity of it’s JS API.
In this post I will:
Via Jan Hesse
Today, we’ll be building a realtime collaborative to-do application, where task status is synced in realtime across all connected devices as their state is changed. We’ll use Polymer to build our application, and PubNub to send and receive updates between connected devices, and to sync state.
Note: This tutorial tries to stay editor independent, meaning the concepts apply to TypeScript specifically and not to an editor. When necessary, screenshots showing relevant information will be of VS Code. VS Code is a free, cross platform editor hat has excellent built in TypeScript support.
React Native's architecture has opened up many possibilities for re-inventing the clunkier aspects of UX construction on traditional platforms, making it easier and faster to build world-class experiences. This talk will walk through building an advanced gestural UI leveraging the unique power of the React Native layout and animation systems to build a complex and fluid experience.
Just a router router 5 is just a router, nothing else. It won't take care of updating your view, and makes no demands regarding you app structure or how your code is organised.Component trees in mind router5 is built to be framework agnostic, and was designed to provide a more flexible and scalable solution for Single Page Applications routing, especially those made of a component tree.Be functional and reactive router5 exposes simple methods and mechanisms to observe route changes and react to them. You can then use it with your favourite stream implementation, FRP library, in a flux-like architecture, etc...
Via Jan Hesse
Sharing your scoops to your social media accounts is a must to distribute your curated content. Not only will it drive traffic and leads through your content, but it will help show your expertise with your followers.
How to integrate my topics' content to my website?
Integrating your curated content to your website or blog will allow you to increase your website visitors’ engagement, boost SEO and acquire new visitors. By redirecting your social media traffic to your website, Scoop.it will also help you generate more qualified traffic and leads from your curation work.
Distributing your curated content through a newsletter is a great way to nurture and engage your email subscribers will developing your traffic and visibility.
Creating engaging newsletters with your curated content is really easy.