Bonnes pratiques

Facebook Twitter
Erreur de chargement de la page - Vimperator
This is another one I've wanted to write forever. Man, I've tried a bunch of times. No ruck. Not Rucky. Programming's Dirtiest Little Secret Programming's Dirtiest Little Secret
Home | The Anti-IF Campaign Home | The Anti-IF Campaign What Is the Anti-IF Campaign? The goal of the Anti-IF Campaign is to raise awareness of effective use of software design principles and practices, first of all removing bad, dangerous IFs. The Campaign accomplishes this by:
The Photoshop Etiquette Manifesto for Web Designers
Signs of a poorly written jQuery plugin Signs of a poorly written jQuery plugin So far with every single workshop I’ve given, both for advanced JavaScript and jQuery for Designers, this question (or some variation thereof) has come up: How do you know if the plugin is good to use? It’s always dependant on the problem they’re trying to solve, but in lieu of a better jQuery plugin ranking system, here’s a couple of tips that should raise a red flag. Consider the following: $.fn.myplugin = function () { var me = $(this).each(function() { return $(this).bind('someEvent', function () { // does something }); });
A Plugin Development Pattern I've been developing jQuery plugins for quite a while now, and I've become rather comfortable with a particular style of plugin development for my scripts. This article is meant to share the pattern that I've found especially useful for plugin authoring. It assumes you already have an understanding of plugin development for jQuery; if you're a novice plugin author, please review the jQuery Authoring Guidelines first. There are a few requirements that I feel this pattern handles nicely: Claim only a single name in the jQuery namespace Accept an options argument to control plugin behavior Provide public access to default plugin settings Provide public access to secondary functions (as applicable) Keep private functions private Support the Metadata Plugin A Plugin Development Pattern
I would like to thank Rebecca Murphey for inspiring me to open-source this mini-book and release it for free download and distribution - making knowledge both open and easily available is something we should all strive for where possible. I would also like to extend my thanks to the very talented Alex Sexton who was kind enough to be the technical reviewer for this publication. I hope that it helps you learn more about design patterns and the usefulness of their application to JavaScript. Volume 2 of Essential JavaScript Design Patterns is currently being written and will be more detailed than this first edition. Essential JavaScript Design Patterns For Beginners Essential JavaScript Design Patterns For Beginners
v.8 ... et pourquoi pas ? © 2009 - Webdesigner/Intégratrice xHTML-CSS-JS Depuis 2004, nous vous accompagnons dans vos projets. Brief & Conseil Ensemble, nous analysons vos besoins et vos problématiques afin de définir au mieux les réponses à y apporter. Conception Graphique & Technique Nous nous chargeons de la mise en œuvre des réponses graphiques et techniques correspondantes. Développement Wordpress v.8 ... et pourquoi pas ? © 2009 - Webdesigner/Intégratrice xHTML-CSS-JS
The Essentials of Writing High Quality JavaScript The Essentials of Writing High Quality JavaScript Twice a month, we revisit some of our readers’ favorite posts from throughout the history of Nettuts+. This tutorial was first published in October, 2010. The brilliant Stoyan Stefanov, in promotion of his book, "JavaScript Patterns," was kind enough to contribute an excerpt of the book for our readers, which details the essentials of writing high quality JavaScript, such as avoiding globals, using single var declarations, pre-caching length in loops, following coding conventions, and more. This excerpt also includes some habits not necessarily related to the code itself, but more about the overall code creation process, including writing API documentation, conducting peer reviews, and running JSLint. These habits and best practices can help you write better, more understandable, and maintainable code—code to be proud of (and be able to figure out) when revisiting it months and years down the road.
This chapter is about writing style sheets with style. By showing you case studies and how they are constructed, we hope to give you a sense of how CSS can be used to encode the visual presentation you want to achieve. Also, more importantly, if you follow the guidelines in this chapter your documents will behave well on a wide range of web devices. For example, they will scale gracefully from one screen size to another. Use ems to make scalable style sheets Chapter 4 The amazing em unit and other best practices Chapter 4 The amazing em unit and other best practices
JavaScript Garden Function Declarations and Expressions Functions in JavaScript are first class objects. That means they can be passed around like any other value. One common use of this feature is to pass an anonymous function as a callback to another, possibly an asynchronous function. JavaScript Garden
JavaScript Guide - MDC Doc Center
Dive Into Python
PEP 8 -- Style Guide for Python Code
Table of Contents - Dive Into HTML5
Duck typing Duck typing When I see a bird that walks like a duck and swims like a duck and quacks like a duck, I call that bird a duck.[1] In duck typing, a programmer is only concerned with ensuring that objects behave as demanded of them in a given context, rather than ensuring that they are of a specific type. For example, in a non-duck-typed language, one would create a function that requires that the object passed into it be of type Duck, in order to ensure that that function can then use the object's walk and quack methods. In a duck-typed language, the function would take an object of any type and simply call its walk and quack methods, producing a run-time error if they are not defined.