Blog. We received an email… “I heard about Forecast, but I couldn’t find it in the App Store. How do I get it?” “You don’t get it from the App Store: just go to on your phone, and you’ll be given instructions on how to download it.” “Wow, this is great! I didn’t know you could get apps outside the App Store!” We’ve had conversations like this dozens of times since launching Forecast.
And they’re right: if it looks and feels like an app, and lives on your home screen, it’s an App. I’d go as far as to say the best weather App in the world right now is a web app. I don’t think the reason is a technical one. So why does it feel as if the average native app is so much better than the average web app? The reason, I think, is this: it’s easy to make web pages.
And this, in turn, leads many serious developers to abandon the web in favor of native app development. When creating a web app you should avoid replicating the default iOS styling and interactions. By Adam Grossman. Pro HTML5 Programming | About This Book. How I Learned To Enjoy JavaScript. Eleven months ago I would have cringed at the thought of having to build large web applications, like the ones I'd usually built in Flex, using JavaScript. Over the years my JS usage became less and less; embed a SWF, fix an IE bug. At the same time the opportunity to work on a big web app that would need to be written in JavaScript was becoming a real possibility. I began to research what the latest JavaScript techniques, tools and best practices were being used by the JavaScript community. What I've learned over the last eleven months is that I am also capable of enjoying big development in JavaScript, even after being mainly an ActionScript developer for close to 10 years.
And even after being so adamantly opposed to dynamic loosely typed languages like JavaScript after having grown so accustomed to a strict-type language like ActionScript. The first thing that I noticed in the modern JavaScript world was that there are about as many frameworks as there are JavaScript developers. Writing Testable Frontend Javascript Part 1 – Anti-patterns and their fixes | Shane Tomlinson. This is the first of a two part introduction to writing testable Javascript UI code. The first article presents a basic sample application containing several common anti-patterns and their solutions.In the second article, the application will be refactored using the described techniques, a simple XHR mock will be presented, and add a test suite will be added to help future developers maintain the code. Front end development comes with a set of challenges that are rarely discussed in articles about unit testing.
Self initialization, encapsulated logic, DOM event handlers, XHR requests, and nested callbacks all make testing difficult. Fortunately, writing front end code so that it can be tested is straight forward, but it does require a little knowledge and thought. Common coding practice – Easy to understand, difficult to test While short, this contrived example uses several common anti-patterns. Anti-patterns that make this application difficult to test Externalize all Javascript ... ...
HTML / CSS. jQuery. Emoji cheat sheet for Campfire and GitHub. Top 10 Things to Know about TypeScript. Introduction TypeScript is a superset of JavaScript that provides typed nature to your code. TypeScript can be used for cross-browser development and is an open source project. This article is intended to give you a quick overview of the top 10 features of this new scripting language. You can download TypeScript here.
The remainder of this article assumes that you are already familiar with some object oriented language such as C# and are acquainted with the general vocabulary of object oriented programming. 1. TypeScript code consists of plain JavaScript code as well as certain keywords and constructs specific to TypeScript. The above code uses TypeScript specific keywords such as class and data types such as number and string. Var Customer = (function () { function Customer() { } Customer.prototype.addCustomer = function () { return 0; }; return Customer; })(); As you can see this is just the plain JavaScript and can be used in any browser that understands JavaScript. 2. 3. 4. 5. 6. 7. Ressources pour développeurs Open Web HTML5. CSS Font-Size: em vs. px vs. pt vs. percent | Kyle Schaeffer. One of the most confusing aspects of CSS styling is the application of the font-size attribute for text scaling.
In CSS, you’re given four different units by which you can measure the size of text as it’s displayed in the web browser. Which of these four units is best suited for the web? It’s a question that’s spawned a diverse variety of debate and criticism. Finding a definitive answer can be difficult, most likely because the question, itself, is so difficult to answer.
Meet the Units “Ems” (em): The “em” is a scalable unit that is used in web document media. An em is equal to the current font-size, for instance, if the font-size of the document is 12pt, 1em is equal to 12pt. So, What’s the Difference? It’s easy to understand the difference between font-size units when you see them in action. As you can see, both the em and percent units get larger as the base font-size increases, but pixels and points do not. Em vs. The Verdict The winner: percent (%). Addendum (January 2011) Tables. 17.1 Introduction to tables This chapter defines the processing model for tables in CSS. Part of this processing model is the layout. For the layout, this chapter introduces two algorithms; the first, the fixed table layout algorithm, is well-defined, but the second, the automatic table layout algorithm, is not fully defined by this specification.
For the automatic table layout algorithm, some widely deployed implementations have achieved relatively close interoperability. Table layout can be used to represent tabular relationships between data. Authors specify these relationships in the document language and can specify their presentation using CSS 2.1. In a visual medium, CSS tables can also be used to achieve specific layouts. Authors may specify the visual formatting of a table as a rectangular grid of cells. Example(s): Here is a simple three-row, three-column table described in HTML 4: Note, however, that the borders around the rows overlap where the rows meet. Table element consecutive. Slides, vidéo et exemples de ma présentation des Microsoft Days et du ReMix11 sur HTML5 - David Rousset.
Dev Center - HTML5. The HTML5 / CSS3 Zone. Welcome to TypeScript. HTML5 & CSS3 Fundamentals: Development for Absolute Beginners. 10 minutes, 20 seconds 35 minutes, 14 seconds 29 minutes, 21 seconds 25 minutes, 25 seconds 48 minutes, 58 seconds 20 minutes, 18 seconds 6 minutes, 59 seconds 15 minutes, 30 seconds 13 minutes, 0 seconds 27 minutes, 27 seconds. The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)
By Joel Spolsky Wednesday, October 08, 2003 Ever wonder about that mysterious Content-Type tag? You know, the one you're supposed to put in HTML and you never quite know what it should be? Did you ever get an email from your friends in Bulgaria with the subject line "???? ?????? ??? I've been dismayed to discover just how many software developers aren't really completely up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff. But it won't. So I have an announcement to make: if you are a programmer working in 2003 and you don't know the basics of characters, character sets, encodings, and Unicode, and I catch you, I'm going to punish you by making you peel onions for 6 months in a submarine. And one more thing: In this article I'll fill you in on exactly what every working programmer should know.
A Historical Perspective The easiest way to understand this stuff is to go chronologically. And all was good, assuming you were an English speaker. Unicode Hello Next: Validator.nu. Can I use... Support tables for HTML5, CSS3, etc. HTML5: Edition for Web Authors. W3C Working Group Note 28 May 2013 This Version: Latest Published Version: Latest Editor's Draft: Previous Versions: Editors: Robin Berjon, W3C Travis Leithead, Microsoft Silvia Pfeiffer Erika Doyle Navara, Microsoft Edward O'Connor, Apple Inc. Previous Editor: Ian Hickson, Google, Inc. Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Abstract This document has been discontinued and is only made available for historical purposes.
This document is a strict subset of the full HTML5 specification that omits user-agent (UA) implementation details. This document is an automated redaction of the full HTML5 specification. Status of This document Browsable version-control record of all changes: