html5-boilerplate/doc/faq.md at v4.0.1 · h5bp/html5-boilerplate Basic Compiler Graphs In this section we describe the set of core compiler specific graphs and algorithms implemented in MLRISC. Mostly of these algorithms are parameterized with respect to the actual intermediate representation, and as such they do not provide many facilities that are provided by higher abstraction layers, such as in MLRISC IR, or in SSA. Dominator/Post-dominator Trees Dominance is a fundamental concept in compiler optimizations. functor DominatorTree (GraphImpl : GRAPH_IMPLEMENTATION) : DOMINATOR_TREE The functor implements dominator analysis and creates a dominator/post-dominator tree from a graph . We annotated each node in a dominator tree with three extra fields of information, which is useful for other algorithms: level is the nesting level of the tree. To create a dominator tree and a postdominator tree from a graph, the following function should be called. val dominator_trees : ('n,'e,'g) graph -> ('n,'e,'g) dominator_tree * ('n,'e,'g) postdominator_tree The query methods are as follows:
Twitter Bootstrap Bootstrap is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions. It is the No.1 project on GitHub with 65,000+ stars and 23,800 forks (as of March 2014) [1] and has been used by NASA and MSNBC, among many others.[2][3] Bootstrap was developed by Mark Otto and Jacob Thornton at Twitter as a framework to encourage consistency across internal tools. Before Bootstrap, various libraries were used for interface development, which led to inconsistencies and a high maintenance burden. "... The first deployment under real conditions happened during Twitter's first Hackweek.[5] Mark Otto showed some colleagues how to accelerate their project's development with the help of the toolkit. In August, 2011 Twitter released Bootstrap as open source. Bootstrap is compatible with the latest versions of all major browsers. <!
Creating Offline HTML5 Apps with AppCache AppCache is the acronym for Application Cache. As the name suggests AppCache is a technique for implementing offline HTML5 web applications. Well, you might think that it is a contradiction to the traditional web app concept because web pages are always downloaded and served to the users. So, how can you load pages if you are offline? The answer is no, we can’t. This is how AppCache works. So, in this tutorial I will explain how AppCache works in detail and how one can build awesome HTML5 apps that work offline. Note: Before going any further check out the compatibility table to know which browsers support AppCache feature. The Fundamentals: You might be thinking how the whole process works and how the browser decides which pages to cache. In order to start the process of caching you just need to point the browser to this manifest file. Inside the manifest file you can add a list of resources that need to be cached. AddType text/cache-manifest .manifest What Goes Inside The Manifest?
Mockups Take a second. Let it sink in. The first impression might be disorienting. There are very few interface elements on the screen. Getting your ideas out should be effortless. Our sweet spot: the ideation phase Mockups really shines during the early stages of designing a new interface. Mockups is zenware, meaning that it will help you get "in the zone", and stay there. Mockups offers the same speed and rough feel as sketching with pencil, with the advantage of the digital medium: drag & drop to resize and rearrange elements, make changes without starting over, and your work is clear enough that you'll make sense of them later. See what you can build with Mockups Download the samples above, or find more on Mockups To Go, our community-contributed stencils site. Designed for collaboration Your whole team can come together around the right design using Mockups. Mockups intentionally makes your wireframes scream both This is not final! Learning UX Design Keyboard Shortcuts Go really, really fast.
Introduction to Offline Web Applications Using HTML5 Introduction In this article I will walk you through the offline storage functionality that is available in HTML5 web applications. I will also provide sample code to demonstrate the feature. The advantage of building offline web applications is that users can still use the web applications without network connectivity. Offline web applications are made possible using the concept of caching. Current Browser Support As HTML is a client-oriented technology, the features that are supported always depend on the client browser itself. Chrome 5.0 and moreSafari 4.0 and moreFireFox 3.5 and more Most surprisingly, even including IE9, there is no such support available on Internet Explorer. Cache manifest file and the caching mechanism The entire offline caching operation revolves around the manifest file. Cache manifest file has the below distinct sections: CACHE - In this section the developer can mention the relative URLs of the resources that need to be cached. Below is a sample manifest file:
Developers Read our docs Docs are organized by language, from .NET to Swift. Create your app Getting started is simple and quick from the App Console. Test your ideas It's easy to prototype and test examples with our API Explorer. Learn from our examples Photo Watch uses our Swift SDK to let users see their Dropbox photos on Apple Watch. Simple Blog Demo uses our .NET SDK to create a simple blogging platform for uploading and downloading files. Back up and Restore uses our Python SDK to back up user settings and then restore them to a specific point in time. Find out what's new What's new Jul 21, 2016Stack Overflow Documentation for Dropbox APIsWe’re excited to announce that we’ve been working with Stack Overflow on the launch of their new Stack Overflow Documentation. Jun 28, 2016API v1 is now deprecated As of today, Dropbox API v1 is deprecated. Apr 11, 2016Announcing the v1 to v2 migration guideUPDATE JUNE 29, 2016 This post now has been updated to include new information about open issues.
Why I’m Done Making Desktop Applications [Editor's note: now available in Belorussian translation and Polish translation.] Breaking up has always been difficult for me. I tend to fall in love with being in love, and continue a relationship well past the point of futility. And so it is with my oldest love, writing desktop software. I’m sorry, desktop apps. A bit of background: for the last three years I’ve sold Bingo Card Creator, a desktop app which pretty much does what it says on the tin. What Changed My Mind Over roughly the same period my day job has changed and transitioned me from writing thick clients in Swing to big freaking enterprise web apps. If I were starting out today, I would, without a shadow of a doubt, write a web app instead of a desktop app, for these reasons: The Shareware Funnel Is Lethal I could go into more detail if I wanted, but that is seventeen different opportunities for the shareware developer to fail. Is it any wonder why shareware has typical conversion ratios of 1% or less? Visitor to Free Trial:
code quality - What makes an application scalable? Creating a Web App from Scratch - Part 1 of 8: Basic Idea and Design Today we begin Part 1 of an 8-Part series on building a web application from absolute scratch to a complete product. I am going to kick things off by introducing the idea, and then I will be handling the design, UI, and general front-end stuff. We are going to be going back and forth from here over to my friend Jason Lengstorf's site Copter Labs. Jason will be handling the back-end stuff like application planning and database stuff. It's Easy, Right? What we're going to create is a "list app". First of all, it needs to work and it needs to work well. Through this whole 8-part series, we are going to create an app that hopefully does all these things pretty well. The Big Idea This "list app" is going to be called Colored Lists. Sketch It Out No need to get fancy right away. Looks like a list to me. Early UI Planning Click-to-editDrag and dropTwo-click deleteAutomatic saving (after any action) All this stuff basically adds up to a whole bunch of AJAX. The Screens "Features" Moving On Share On