background preloader



12 superbes ressources HTML / CSS / JS réalisées sur CodePen CodePen est un formidable outil qui regroupe de nombreuses ressources pour développeurs, intégrateurs et webdesigners qui sont en quête d’inspiration. À l’image des vagues du web, Megaptery vous propose une sélection de 12 superbes ressources réalisées sur CodePen. CodePen, c’est quoi ? Conçu par Chris Coyier (créateur de CSS-Tricks), CodePen est un éditeur de code en ligne (tout comme jsFiddle et CSSDeck) composée de 4 vues distinctes : le HTML, le CSS, le JavaScript, et une zone de prévisualisation « en live » permettant de partager facilement des travaux avec d’autres développeurs, qui peuvent à leur tour les éditer et les améliorer. Vous l’aurez compris, CodePen est une véritable mine d’or de ressources front-end. Voici une sélection de 12 réalisations HTML / CSS / JS de qualité accompagnées d’une brêve description. CSS circular reveal Description : un effet original d’apparition d’une image au rollover de façon circulaire. Color Wheel Manette NES 3D

❍ IcoMoon IcoMoon is striving to build and provide the best iconography and icon management tool for perfectionists. IcoMoon's icon library features only the very best icon sets out there. All of our icons are designed on a precise pixel grid. The IcoMoon app lets you build and use your own icon sets in many different formats including SVG, Polymer, PDF, XAML, CSH, icon font or simple PNG/CSS sprites. IcoMoon was first built and released back in the November of 2011. IcoMoon was also the first to solve a big problem with icon fonts: Compatibility with screen readers. IcoMoon is constantly improving and it offers many unique features. With over 4000 free and open source icons available in IcoMoon's library, and by allowing you to generate crisp icon fonts and SVG sprites locally/offline, this service is far ahead of any similar one. IcoMoon is created and maintained by Keyamoon and it is currently operating under Roonas. Need to contact us?

Billet de Train pas cher - Troc billets de train | Web Après plusieurs mois de travail intense, la plateforme technique qui supporte MDN vient de changer. Originellement basée sur la solution DekiWiki de la société MindTouch, la documentation de Mozilla vient de passer sous une solution 100% maison : Kuma. Kuma est un projet codé à l’aide de Python/Django et est directement inspiré de la plateforme qui supporte déjà SUMO (le support utilisateur de Firefox) connu sous le nom de Kitsune. Comme tous les projets Mozilla, Kuma est 100% open source. Le code est disponible sur GitHub et vous êtes largement invité à proposer patches et fixes si vous en avez envie Le principal intérêt pour MDN de passer sur une plateforme ouverte et développée par Mozilla est simple : Pouvoir maîtriser les évolutions à apporter à la plateforme pour garantir la meilleure expérience utilisateur possible sur MDN. Quoi de neuf ? Si la plateforme, très jeune, souffre encore de quelques bugs en cours de résolution, les premières améliorations sont déjà visibles. Et après ?

Pricing Community Unlimited public projects and unlimited developers 1 shared builder queue and 1 shared runner queue Commercial For companies and organizations $399 / year Personal For individual developers $149 / year Academic For institutions, teachers, and students Classroom For educational institutions, trainers, and classes Open Source For open source projects Unlimited private projects Unlimited public projects 1 Dedicated builder queue 1 Dedicated runner queue Unlimited developers Additional Queue Includes 1 builder and 1 runner for more power $499 / queue / year Organizational Add-On Multiple admins , team profiles and dashboards $999 / org / year All Premium Subscriptions Always Include: FREE Hosting No Set-up Fee Project Templates Premium Support Codenvy SDK Premium plan guarantees: Powerful grid architecture Load balancing 99.9% uptime Unlimited bandwidth Unlimited storage No advertisements Codenvy Enterprise Private installation on your own hardware or IaaS Codenvy ISV What is a workspace?

Films, bandes-annonces et séances - Cinémur Tavmjong Bah's Blog | A blog about Inkscape, SVG, and other worldly matters… The SVG Working Group had a four day face-to-face meeting in Sydney this month. Like last year, the first day was a joint meeting with the CSS Working Group. I would like to thank all the people that donated to Inkscape’s SVG Standards Work fund as well as to the Inkscape general fund that made my attendance possible. Joint CSS and SVG Meeting Minutes CSS Stroke and Fill Specification The CSS working group would like to allow the use of the SVG ‘stroke’ and ‘fill’ properties on CSS text as well as other places in CSS (e.g. box border). Text Issues Next we covered a whole slew of text issues I raised dealing with flowed text in SVG. Strategy for using CSS in SVG for wrapping The first issue was to agree on how SVG and CSS are related. The CSS/HTML code: The result: Wrapped text in HTML. The CSS/SVG code: Wrapped text in SVG 2. It was pointed out at a discussion on Day 2, that the use of ‘shape-outside’ in SVG was not consistent with the CSS model. How is the first line placed in a wrapped shape?

HTML5 Please - Use the new and shiny responsibly Creating Task Handlers  |  App Engine standard environment for Java  |  Google Cloud Platform This page describes how to create a task handler, the code that handles a push task. App Engine executes tasks by sending HTTP requests to your application. You must provide a request handler to execute your task code. The mapping from the request URL to the code is declared in your service's web.xml, just like any other request handler. Writing a push task request handler The Task Queue service creates an HTTP header and sends it to an instance of the worker service specified by the task's target. Your handler does not need to be written in the same language that created and enqueued the task if you write it in a separate service. When you write you handler, follow these guidelines: The code should return an HTTP status code within the range 200–299 to indicate success. The response is only seen by the Task Queue service to determine if the task succeeded. User-supplied data can be delivered in the request as a query string or as a payload in the request body. Securing task handler URLs

Reading local files in JavaScript Introduction HTML5 finally provides a standard way to interact with local files, via the File API specification. As example of its capabilities, the File API could be used to create a thumbnail preview of images as they're being sent to the server, or allow an app to save a file reference while the user is offline. The spec provides several interfaces for accessing files from a 'local' filesystem: File - an individual file; provides readonly information such as name, file size, mimetype, and a reference to the file handle. When used in conjunction with the above data structures, the FileReader interface can be used to asynchronously read a file through familiar JavaScript event handling. Selecting files The first thing to do is check that your browser fully supports the File API: // Check for the various File API support.if (window.File && window.FileReader && window.FileList && window.Blob) { // Great success! Using form input for selecting Example: Using form input for selecting.

CodeMirror HTML5test - How well does your browser support HTML5? lihaoyi/scala.rx JavaScript is Sexy | Learn modern web application development with JavaScript