background preloader

JSON Formatter & Validator

JSON Formatter & Validator
Related:  Javascript

JSONLint - The JSON Validator. User Experience quotes and articles to inspire and connect the UX community | inspireUX BNOTIONS We laughed, we learned and we connected with hundreds of developers at the jQueryTO 2013 conference in downtown Toronto. The 2-day conference attracted the top talent in the city and beyond, featuring cutting edge presentations and a stellar speaker lineup, which included Paul Irish and Addy Osmani from the Chrome team and some of the biggest names in the jQuery developer community. (Slides for all the speaker’s presentations follow below.) We used Google+ as a social platform during the event and asked everyone to “check-in” and use “party mode,” so we could crowd-source photos from the conference. Over 2 days, more than 150 photos were uploaded from attendees! A collection of great photos from jQueryTO 2013 “A huge thank you to the 500+ devs that stayed to watch my paint performance keynote at +jQueryTO. We want to thank all the volunteers for their help in running an awesome conference. Louis Lazaris – When jQuery and CSS3 3,181 views

25 great free UX tools There might be no such thing as a free lunch but thanks to the wonders of Open Source software, freeware and trial software there most certainly is such a thing as free software. In this article I list 25 great free UX tools, including tools to help with prototyping, annotating, screen grabbing, site mapping, usability testing, accessibility and analytics. Prototyping tools Pencil Pencil is a nice little Open Source tool for creating prototypes, UI mockups, and UX diagrams, such as user journeys. Pencil – A free prototyping and diagramming tool LucidChart LucidChart is an online tool for creating diagrams, UI mockups and prototypes. LucidChart – A prototyping and diagramming tool with a free trial version Balsamiq Balsamiq is another online UI prototyping tool and like LucidChart it’s not fee but does allow you to create simple single pages for free using the trial version (just click on the ‘take a tour’ link). Balsamiq – A prototyping tool with a free trial version Serena Prototype Composer

Frontend Single Point of Failure | Dean Hume At this year's Velocity Europe conference, I watched a great talk by Google's Patrick Meenan about 3rd party scripts and frontend Single Point of Failure (SPOF). A single point of failure is a part of a system that, if it fails, will stop the entire system from working. Quite often, you may add 3rd party scripts such as jQuery, social sharing buttons or Ad tracking scripts to your website with the best intentions, but depending on the way that these scripts are loaded you could potentially create a frontend single point of failure that can block the entire site! If these 3rd party scripts are not implemented and deployed properly they pose a significant risk for the websites that host them. Once you have downloaded and added the plugin to Chrome, simply navigate to your desired webpage. Click on the plugin and you will be presented with a list of the blocking scripts. As you surf the web with this plugin enabled, you may notice how many websites have blocking scripts on their pages!

Thinking Async Here's the rub: when you load JavaScript from a third party you should do it asynchronously. You might want to load your own scripts asynchronously too, but for this article let's focus on third parties. There are two reasons for this: If the third-party goes down or is slow, your page won't be held up trying to load that resource.It can speed up page loads. At Wufoo, we just switched over to an asynchronous embed snippet. Let's explore this whole async thing. Uhm. There is a little terminology involved here that will help us understand the umbrella "asynchronous" term. "Parser blocking" - The browser reads your HTML and when it comes to a <script> it downloads that entire resource before moving on with the parsing. To prevent problematic parser blocking, scripts can be "script inserted" (i.e. insert another script with JavaScript) which then forces them to execute asynchronously (except in Opera or pre 4.0 Firefox). The HTML5 Way The Classic Async Way Ad Networks Couple of things to note here:

Separating JavaScript download and execution Not too long ago, I wrote a post entitled, Thoughts on script loaders[1], in which I discussed my thoughts on the continuing introduction of script loaders such as LABjs and ControlJS. In that post I also mentioned what I thought was the main problem that led to existence of these libraries. That problem is the inability of the developer to control the download of JavaScript files as separate from its execution. After a conversation with Steve Souders about ControlJS, I put together a proposal for a delayed script execution model in browsers[2]. Background Traditionally, JavaScript execution immediately followed download of the external JavaScript file. As a recap, adding defer to a <script> causes JavaScript to download immediately but hold off on executing until the entire DOM has been loaded (before DOMContentLoaded). Developers discovered that creating a script element dynamically using JavaScript caused a different behavior. The problem Requirements The original proposal Proposal v2.1

Yeoman - Modern workflows for modern webapps La gestion des événements en JavaScript Cet article est une introduction aux notions nécessaires pour bien comprendre et utiliser les événements en JavaScript. JavaScript est un langage événementiel : le développeur a un contrôle limité sur le flux d'exécution du code, qui est déterminé principalement par les interactions avec l'environnement (activation d'un lien, mouvement de la souris, chargement du contenu du document, …). La gestion des événements est un sujet essentiel dans le cadre de ce langage. Elle reste pourtant assez mal comprise, en partie à cause des lacunes et erreurs d'implémentation des différents navigateurs. Cet article présente les trois grandes familles d'interfaces qui sont aujourd'hui à notre disposition : Le DOM niveau 0, standard de facto hérité de Netscape ; il s'agit de l'interface la plus largement supportée mais aussi la moins puissante. Les concepts présentés dans la suite de l'article sont communs à ces trois familles, sauf indication contraire. L'objet Event target type stopPropagation preventDefault

Review of JS Frameworks — Journey Through The JavaScript MVC Jungle When writing a Web application from scratch, it’s easy to feel like we can get by simply by relying on a DOM1 manipulation library (like jQuery412) and a handful of utility plugins. The problem with this is that it doesn’t take long to get lost in a nested pile of jQuery callbacks and DOM elements without any real structure in place for our applications. In short, we’re stuck with spaghetti code3. Fortunately there are modern JavaScript frameworks that can assist with bringing structure and organization to our projects, improving how easily maintainable they are in the long-run. What Is MVC, Or Rather MV*? These modern frameworks provide developers an easy path to organizing their code using variations of a pattern known as MVC4 (Model-View-Controller). Models represent the domain-specific knowledge and data in an application. JavaScript ‘MVC’ frameworks that can help us structure our code don’t always strictly follow the above pattern. When Do You Need A JavaScript MV* Framework?

Feature sniffing Internet Explorer - Snippets Pretty much all web developers should know by now that browser sniffing is evil. If you don’t know why, you should definitely read Richard Cornford’s excellent treatise Browser Detection (and What to Do Instead). Feature detection, where you look for the specific feature you want to use, is much safer; taken to the extreme, it can end up like the rather clever Modernizr project. But what if you really do just want to know if your code has the misfortune to be running on IE7? Ideally, you should use Microsoft’s conditional comments to handle that, for example here’s how to load a script segment specifically for IE7: But what about handling browser differences deep in the middle of a big script? Of course, you could always resort to the evil browser sniffing, looking at the user agent to see what you’re running on, but that way is fraught with peril as discussed at length by Cornford and others. But there is another way. Here’s a table of some browser properties you can check for.

Écrire du JavaScript véloce et à faible empreinte mémoire Par Addy Osmani Vous devriez plutôt vous poser ce type de questions : Que puis-je faire pour rendre mon code plus efficient ? Quelles optimisations communes sont faites par les moteurs JavaScript ? Quelles sont les limites de l’optimisation de ces moteurs ? Le ramasse-miette est-il bien capable de libérer la mémoire comme je m’y attend ? Les sites véloces, comme les voitures de course, nécessitent des outils spécialisés. Nombreux sont les pièges quand on souhaite produire du code rapide et économe en mémoire. Comment fonctionne JavaScript au sein de V8 ? Bien qu’il soit possible d’écrire des applications volumineuses sans comprendre le fonctionnement des moteurs JavaScript, n’importe quel conducteur vous dira qu’il a déjà jeté un œil sous le capot au moins une fois. Un compilateur de base qui parcourt votre JavaScript et génère du code machine avant qu’il soit exécuté, plutôt que d’exécuter du bytecode ou simplement de l’interpréter. Le ramasse-miette Les mythes du déréférencement Les timers

Get all functions of an object in JavaScript