#colini

Quello che non vi raccontano – La risposta della società civile israeliana alla violenza dei coloni.Domani da alcune città israeliane partiranno dei pullman verso i Territori per fare blocco contro i coloni mentre i palestinesi raccolgono le olive.E’ una prassi abbastanza consolidata ma questa volta di fronte al susseguirsi degli episodi di violenza (impunita) dei “Ragazzi delle colline” (I…

€ 13,97 - Set di filtri LiveFresh - Set di filtri, colini e setaccci in acciaio inox a maglia fine, progettati per la Quinoa con comodi manici antiscivolo - in 3 formati

€ 13,97 (SCONTO DEL 53%!)

€ 12,97 - Set di filtri LiveFresh - Set di filtri, colini e setaccci in acciaio inox a maglia fine, progettati per la Quinoa con comodi manici antiscivolo - in 3 formati

€ 12,97 (SCONTO DEL 56%!)

€ 5,98 - iNeibo Kitchen infusore per tè e tisane/colino/filtro per te in silicone con setaccio in acciaio inox e un tappo a forma di foglia di Tè insieme ad un piattino, 100% silicone privo di BPA, (Verde)

€ 5,98 (SCONTO DEL 52%!)

New Post has been published on http://www.torontowebsitedesign.biz/toronto/why-javascript-and-the-internet-of-things/?utm_source=TR&utm_medium=Tumblr+Account&utm_campaign=SNAP%2Bfrom%2BToronto+Website+Design

Why JavaScript and the Internet of Things?

Updated:

JavaScript has proven itself worthy on both the client and server side world of web applications, but why does it have potential in the ever expanding Internet of Things (IoT)?

Over the past two years, I’ve covered the growing amount of technology that JavaScript developers can get involved with in my JavaScript Beyond the Web and JavaScript Beyond the Web in 2014 articles here at SitePoint, as well as in various presentations at conferences and meetups. There is a huge level of enthusiasm for JavaScript and the IoT which is great (nice to know I’m not alone in this passion), but many developers ask one very reasonable question – why JavaScript? What are the advantages of using JavaScript with the Internet of Things? I decided it’d be useful to explore this topic in a bit more detail and put a lot of my thoughts down in writing.

Much of the Internet already speaks JavaScript

The whole idea of the Internet of Things is a simple one. We want to connect a range of new devices to the Internet so they can speak to servers and devices around the world. While the next big IoT device that changes the world is likely to be something we don’t see coming (that’s just the nature of technology right?), we know the technology pillars that it is likely to stand upon – connecting devices to web APIs in new and unexpected ways to (hopefully) benefit society. What language can our web pages and web apps speak right now? JavaScript. It makes sense to extend the same standard platform to the Internet of Things, communicating to a larger range of devices using that same language.

We can share functionality

JavaScript’s ability to be everywhere is huge. When connecting up a network of devices to your server, having them all speak the same language makes life easier. If you’ve got a large number of different connected devices that all understand JavaScript and you’ve got a server running Node.js, you’ve reduced complexity and can share functions that do the similar functions across different devices. Say you have business logic in your app which you need to reuse for different devices and server responses. With JavaScript, you can reuse the same functions for calls to different devices with ease – build once and reuse.

Existing libraries, plugins, and APIs

JavaScript has a range of existing libraries, plugins, and APIs, many of which can be utilized in the Internet of Things. While the jQuery plugins of old aren’t the most reusable for non-client side code, there is an evolving world of npm modules in JavaScript that are reusable for a multitude of solutions on the client, server, and beyond.

JavaScript utility libraries like Underscore.js, lodash, traverse and Async can be perfect to use in a range of common situations across different devices. There are some very powerful functions in the above modules that would be useful to IoT projects.

Another example of a great JavaScript module that is perfect for IoT is Socket.io – a module providing real time event based communication across multiple devices.

New Post has been published on http://www.torontowebsitedesign.biz/toronto/getting-started-with-react-and-jsx/?utm_source=TR&utm_medium=Tumblr+Account&utm_campaign=SNAP%2Bfrom%2BToronto+Website+Design

Getting Started with React and JSX

Updated:

React is an open source library for building user interfaces. It lets you create views easily while making sure your UI stays in sync with the underlying data model. This article, targeted towards beginners, covers the basics of React and JSX syntax.

Getting Started with React

To get started, head over to the official React official website and download the React starter kit. It contains all the files you need to get started.

Once you have download the .zip, extract it to a location on your machine. You will see a directory named React-<version>. On my machine the name of the directory is react-0.12.0. Open it and go to the build directory. We are going to need the following two files:

JSXTransformer.js – Lets you create JavaScript objects through simple HTML.

react.js – The core React library.

Let’s create a file named index.html inside the directory react-<version> and add the following snippet:

[html] < !DOCTYPE html>

var Greeting = React.createClass( render: function() return (

Hello, Universe

) ); React.render( , document.getElementById('greeting-div') ); [/html]

The above snippet prints Hello, Universe on the UI. You should note the following points:

React follows component oriented development. The general idea is to break your whole UI into a set of components. In our case we have just one component named Greeting. In React, you create a component by calling React.createClass(). Every component has a render() method which returns markup to render. In the above snippet we simply returned <p>Hello, Universe</p>, which is then displayed in the view.

A component doesn’t do anything until it’s rendered. To render a component you call React.render() with the component to render as the first argument. The second argument is the HTML element where you would like to render your component. In our case we render our Greeting component into div#greeting-div .

You might be wondering what <Greeting/> really is? This syntax is known as JSX (JavaScript XML) which lets you build DOM nodes with HTML-like syntax. However, JSX is completely optional and you don’t need it in order to use React. But it has a lot of nice features and there is no reason not to take advantage of it.

Since the browser doesn’t understand JSX natively, we need to transform it to JavaScript first. This is handled by including the following script: