Mobile Web

Todays web front-end applications architecture. All resources shared at the end of presentation. Full sources on: https://lnkd.in/gyQuFKK https://lnkd.in/gZK8Sp3

This document discusses Single Page Applications (SPAs) and the JavaScript framework Backbone.js. It defines SPAs as web apps that handle interactions on the client-side without needing to reach the server. The document discusses why SPAs are useful for providing a fluid user experience but can increase code complexity. It introduces Backbone components like Models, Collections, Views and the Router that help manage this complexity by enforcing structure and separating concerns. Examples are provided of how to decompose user interfaces into Views and use Backbone to encapsulate state, add routing, and follow best practices like view-model associations and event-driven communication between components.

This document discusses AJAX (Asynchronous JavaScript and XML). It defines AJAX as standards-based presentation using XHTML, CSS for dynamic display, DOM for interaction, XML/XSLT for data interchange, and asynchronous retrieval of XML data using XMLHttpRequest and JavaScript binding. It describes the components of AJAX including HTML, CSS, DOM, XMLHttpRequest object. It explains asynchronous processing in AJAX and how AJAX works by fetching data from servers in the background without page refreshes. It provides examples of XMLHttpRequest and discusses advantages like faster page loads and new interface types and disadvantages like initial slowness and compatibility issues.

AJAX stands for Asynchronous JavaScript and XML. It is a technique for building interactive web applications where data can be updated asynchronously in the background without interfering with the display and behavior of the existing page. AJAX uses a combination of technologies like XHTML, CSS, DOM, XML, XSLT, JavaScript, and the XMLHttpRequest object to retrieve data from the server asynchronously in the background without loading the entire web page. This allows web pages to be more interactive and provides a better user experience.

This document summarizes AIDA/Web, a Smalltalk-based web application framework, and SWAZoo, a related project. AIDA/Web provides a Model-View-Controller architecture for dynamic web applications, supports web elements, session management, security, and persistence. SWAZoo aims to merge various Smalltalk web projects into a single toolkit, and includes an HTTP server, virtual servers, resource hierarchy, URL resolution, and HTTP request parsing capabilities. The document concludes by asking about Smalltalk's role in e-commerce.

This document discusses Web 2.0 and AJAX technologies. It defines Web 2.0 as focusing on user participation, sharing, and collaboration using technologies like blogs, wikis, and AJAX. AJAX is defined as using asynchronous JavaScript and XML to update parts of a web page asynchronously without reloading the entire page. Examples of popular AJAX applications are given like Gmail and Google Maps. The technologies used in AJAX like XMLHttpRequest are discussed along with the asynchronous request-response process and browser support. Security considerations for both server-side and client-side AJAX applications are also covered.

From DevConnections Las Vegas, Apr 19, 2011 Whether it’s dashboards, content publishing, or day-to-day collaboration, SharePoint’s web pages usually contain lots of web parts. Using traditional post-back techniques to refresh a single web part’s content is both slow and visually annoying. This session will cover what’s possible using AJAX, custom web services, the client object model and jQuery to spice up the SharePoint web parts that you’re cooking. Boom!

This document provides 11 best practices for ASP.NET MVC architecture and development. It recommends deleting unused account controller code, isolating controllers from external dependencies, using an inversion of control container, avoiding magic strings, following the POST-REDIRECT-GET pattern, separating domain and view models, not using code behind in views, bundling and minifying scripts/CSS, leveraging areas, caching data, and questions the use of repositories on top of a unit of work. It also outlines common MVC layers including models, data access with repositories, a service layer, and presentation layer.

This document provides an introduction to ASP.NET MVC, covering the basics of MVC including models, views, controllers, routing, security, and more. It discusses how MVC fits into today's web development with frameworks built on top of HTTP. The "good parts" of MVC are highlighted, like separation of concerns, testability, and clean HTML output. Examples are provided throughout to demonstrate key MVC concepts.

Single page applications (SPAs) provide a desktop-like user experience by dynamically loading content within a single web page rather than linking between multiple pages. Key characteristics of SPAs include chunking of HTML and data, use of MVC patterns for controllers, templating for views, routing for navigation without page reloads, real-time communication with servers, and local storage of data. Challenges for SPAs include search engine optimization due to lack of JavaScript execution, maintaining browser history state, and managing the page lifecycle of progressively loading content.

The document discusses using HTML hypermedia APIs and adaptive web design together. HTML hypermedia APIs use standard HTML to build APIs that follow the hypermedia constraint, where clients interact by following links and submitting forms. Adaptive web design allows a single codebase to work across different devices by responding to features and making content and layout fluid. The document argues that HTML hypermedia APIs and adaptive web design work well together by allowing the same code and templates to be used for both the web interface and API, with separate URLs and optimizations for different perspectives. A demo is shown of a kanban board application built with this approach.

This document provides an overview of Java Server Pages (JSP) technology. It discusses that JSP allows developers to create dynamic web pages using Java code and HTML/XML. Key points covered include JSP elements like scripting elements, directives, actions; accessing request and response objects; session tracking mechanisms; and file uploading using HTML forms.

This document discusses combining HTML hypermedia APIs with adaptive web design to create rich experiences despite platform fragmentation. It advocates using HTML elements like <a>, <link>, and <form> to define hypermedia controls and semantics. Content should be enhanced progressively based on capabilities. APIs and the web can be unified by treating the API as another representation of web resources, following HTTP specifications. Responsive design patterns like fluid layouts and conditional loading adapt to different contexts.

This document discusses unobtrusive JavaScript and how it separates JavaScript behavior from HTML markup. Unobtrusive JavaScript allows web pages to degrade gracefully when JavaScript is disabled, as the functionality is not coupled to the document structure. It provides an example of unobtrusive JavaScript that is completely separate from the markup and reusable. The document recommends using frameworks like jQuery to select elements and enhance the user experience with JavaScript after the site functions without it.

This document discusses various architectures and technologies for building web applications, including thick vs thin client architectures, MVC patterns, client vs server-side templating, RESTful vs RPC APIs, single page vs multi-page applications, and offline capabilities using technologies like AppCache and IndexedDB. It also briefly mentions responsive design, frameworks like Bootstrap and HTML5 Boilerplate, and pushing the capabilities of web applications.