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:
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?
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
Ajax (programming) Ajax is not a single technology, but a group of technologies. HTML and CSS can be used in combination to mark up and style information. The DOM is accessed with JavaScript to dynamically display, and allow the user to interact with, the information presented. JavaScript and the XMLHttpRequest object provide a method for exchanging data asynchronously between browser and server to avoid full page reloads. In 1996, the iframe tag was introduced by Internet Explorer to load or to fetch content asynchronously. In 1998, Microsoft Outlook Web App team implemented the first component XMLHTTP by client script. Google made a wide deployment of standards-compliant, cross browser Ajax with Gmail (2004) and Google Maps (2005).[6] The term "Ajax" was publicly stated on 18 February 2005 by Jesse James Garrett in an article titled "Ajax: A New Approach to Web Applications", based on techniques used on Google pages.[1] get-ajax-data.js: send-ajax-data.php: jQuery example
SVG with a little help from Raphaël Raphaël is a light-weight JavaScript library that renders dynamic SVG graphics including charts, graphs, vector-based animations and GUI components right into your web pages. Now, you’re probably thinking, I can already do this with jQuery, Google Charts, or even Flash! While this is true, Raphaël reveals new possibilities not currently available with these other technologies. Let’s learn how to create inline scalable vector images that work across browsers and degrade gracefully. Open language for an open web#section1 Issue № 310 The web is all about open standards and unencumbered technologies. But, what about Internet Explorer 6? JQuery#section2 What about jQuery? There are plenty of interesting jQuery graphics plugins, such as jqPlot, Flot, jQuery SVG, and others. Raphaël is smaller overall for creating basic vector graphics. It doesn’t have to be an either/or scenario. Dynamic Images#section3 Examples#section4 Progressive Enhancement#section5 Animations#section6 Conclusion#section9
Java EE & Java Web Learning Trail - NetBeans Tutorials, Guides and Articles What is a Java Web Application? A Java web application generates interactive web pages containing various types of markup language (HTML, XML, and so on) and dynamic content. It is typically comprised of web components such as JavaServer Pages (JSP), servlets and JavaBeans to modify and temporarily store data, interact with databases and web services, and render content in response to client requests. Because many of the tasks involved in web application development can be repetitive or require a surplus of boilerplate code, web frameworks can be applied to alleviate the overhead associated with common activities. What is Java EE? Java EE (Enterprise Edition) is a widely used platform containing a set of coordinated technologies that significantly reduce the cost and complexity of developing, deploying, and managing multi-tier, server-centric applications. Some of the fundamental components of Java EE include: