description: web application based on a single web page and client-side logics
16 results
by Imran Bashir · 28 Mar 2018
also available via npm. It is also available via GitHub at https://github.com/nexusdev/dapple. Meteor This is a full-stack development framework for single-page applications. It can be used for Ethereum DApp development. There is a development environment available in meteor, and it allows easier and easy development of complex
by James Higginbotham · 20 Dec 2021 · 283pp · 78,705 words
retrieving deeply nested graph structures. Over time, it has become a popular choice by front-end developers that need to bridge backend data stores with single-page applications (SPAs) and mobile apps. All GraphQL operations are tunneled through a single HTTP POST or GET-based URL. Requests use the GraphQL query language to
by Sam Newman · 14 Nov 2019 · 355pp · 81,788 words
have improved, so has the sophistication of the code running in browsers improved. Many web-based user interfaces now make use of some form of single-page application framework, which does away with the concept of an application consisting of different web pages. Instead, you have a more powerful user interface, where everything
…
, partly because the exact way you make this work will vary based on the SPA frameworks being used. But if you find yourself with a single-page application that you want to break apart, you’re not alone, and there are many people out there sharing techniques and libraries to make this work
by Adam Freeman · 25 Mar 2014 · 671pp · 228,348 words
the different ways you can create both components and explain the wide range of built-in services that AngularJS provides. This includes support for simplifying Single-Page Application development, Ajax and RESTful APIs, and unit testing. Are There Lots of Examples? There are loads of examples. The best way to learn AngularJS is
…
kind of web application you build. In broad terms, there are two kinds of web application: round-trip and single-page. Understanding Round-Trip and Single-Page Applications For a long time, web apps were developed to follow a round-trip model. The browser requests an initial HTML document from the server. User
…
because each HTML document has to be self-contained (leading to a lot of the same content being included in each response from the server). Single-page applications take a different approach. An initial HTML document is sent to the browser, but user interactions lead to Ajax requests for small fragments of HTML
…
where AngularJS delivers benefit. AngularJS jQuery Round-Trip Single-Page Figure 3-1. AngularJS is well-suited to single-page web apps AngularJS excels in single-page applications and especially in complex round-trip applications. For simpler projects, jQuery or a similar alternative is generally a better choice, although nothing prevents you from
…
using AngularJS in all of your projects. There is a gradual tendency for current web app projects to move toward the single-page application model, and that’s the sweet spot for AngularJS, not just because of the initialization process but because the benefits of using the MVC pattern
…
core language features. I also introduced promises and the AngularJS support for JSON, both of which are essential for working with Ajax and implementing the single-page application model that I described in Chapter 3. I am not able to provide a complete description of JavaScript in this book, but the features I
…
����������������������������������������������������������������������������������������������������������������������� 37 Getting the Data via Ajax������������������������������������������������������������������������������������������������������������������������������������� 41 Summary�������������������������������������������������������������������������������������������������������������������������������������44 ■■Chapter 3: Putting AngularJS in Context�������������������������������������������������������������������������45 Understanding Where AngularJS Excels�������������������������������������������������������������������������������������45 Understanding Round-Trip and Single-Page Applications����������������������������������������������������������������������������������� 45 Understanding the MVC Pattern��������������������������������������������������������������������������������������������������47 Understanding Models����������������������������������������������������������������������������������������������������������������������������������������� 49 Understanding Controllers����������������������������������������������������������������������������������������������������������������������������������� 50 Understanding Views������������������������������������������������������������������������������������������������������������������������������������������� 51 Understanding RESTful Services�������������������������������������������������������������������������������������������������51 Common Design Pitfalls��������������������������������������������������������������������������������������������������������������53 Putting the
by Harihara Subramanian · 31 Jan 2019 · 422pp · 86,414 words
schemes and the situations or business cases you would choose those specific schemes for, with the following table: Schemes / Flow Client type Brief description Implicit Single-page application (SPA) such as Google Fonts. Application requests access tokens from the gateway and the user grants permission Client-credentials Machine-to-machine non-interactive programs
…
not entirely controlled by server-provided pages. Generally, but not limited to, APIs that dynamically inject attacker-controllable data to a page and JavaScript frameworks. Single-page applications are vulnerable to DOM XSS. XSS protection needs to filter malicious content from user input and also needs encoding (escape). Cross-site request forgery Cross
by Rodrigo Branas · 20 Aug 2014 · 180pp · 37,187 words
, REST, and JSON Creating an HTTP facade Headers Caching Interceptors 67 68 69 70 74 75 76 76 76 82 84 85 85 Creating a single-page application 87 Logging Timeout Asynchronous with a promise-deferred pattern 96 96 98 Installing the module Configuring the routes Rendering the content of each view Passing
…
"> </body> </html> There is another way to attach a controller to a specific view. In the following chapters, we will learn how to create a single-page application using the $route service. To avoid undesired duplicated behavior, remember to avoid the ngController directive while using the $route service. [ 20 ] Chapter 2 Nested controllers
…
services for our daily development. In the following topics, we will explore how to perform communication with the backend, create a logging mechanism, support timeout, single-page application, and many other important tasks. Communicating with the backend Every client-side JavaScript application needs to communicate with the backend. In general, this communication is
…
API, as follows: config.js app.config(function ($httpProvider) { $httpProvider.interceptors.push('httpTimestampInterceptor'); $httpProvider.interceptors.push('httpUnauthorizedInterceptor'); }); [ 86 ] Chapter 4 Creating a single-page application In the past few years, the single-page application, also known as SPA, has been growing in popularity among frontend developers. It improves customers' experiences by not requiring the page to
…
, 118, 119 services, AngularJS components creating 69 creating, with AngularJS service 74 creating, with factory function 70-73 creating, with provider 75, 76 testing 125 single-page application. See SPA singleRun property 142 SPA about 87 asynchronous promises, resolving 93-95 location, changing 92 module, installing 87 parameters, passing 91 routes, configuring 87
by James Sugrue · 15 Dec 2013 · 290pp · 119,172 words
is what desktop applications have always benefited from. Now that Ajax had proved itself and the JavaScript ecosystem was providing more robust libraries and frameworks, single-page applications were easier to implement. These applications are not without their challenges. For a single page to deal with different stages in the application life cycle
…
and idiosyncrasies, have led a significant majority of developers to work on HTML5-based web apps that behave in a similar fashion to native apps. Single-page applications enable such applications to be built and made available directly from web sites, rather than requiring users to acquire the app through the app store
…
on their device. The Continuing Need for Structure As browser-based applications continue to dominate, the architecture behind single-page applications becomes much more significant. With so much logic now residing in the client side, it’s clear that the practices and patterns that have applied
by Patrick Mulder · 18 Jun 2014 · 190pp · 52,865 words
, browsers, and DOM manipulation, as well as a basic knowledge of web applications. Also, there are a number of resources available to go deeper into single-page application development. The JavaScript Language To learn JavaScript, there are a number of good resources available: JavaScript Garden This is an open source resource on programming
…
build your API yourself. This will be the topic of the next chapter. Conclusion In this chapter, you made quite some progress toward a full, single-page application that fetches data from a remote data store. To prevent developing a full backend at this stage, we saw a strategy to mock a RESTful
by Addy Osmani · 21 Jul 2012 · 420pp · 79,867 words
concerns in your application, leaving you with code that is more maintainable in the long term. Developers commonly use libraries like Backbone.js to create single-page applications (SPAs). SPAs are web applications that load into the browser and then react to data changes on the client side without requiring complete page refreshes
…
. The entire Backbone source can be read and understood in just a few hours. When Do I Need A JavaScript MVC Framework? When building a single-page application using JavaScript, whether it involves a complex user interface or is simply trying to reduce the number of HTTP requests required for new Views, you
…
more interactive, an MV* framework may be overkill. There certainly are complex Web applications where the partial rendering of views can be coupled with a single-page application effectively, but for everything else, you may find yourself better sticking to a simpler setup. Maturity in software (framework) development isn’t simply about how
…
and the general responsiveness of the user experience. A trend to improve perceived latency in the past few years has been to move towards building Single Page Applications (SPAs) - apps which after an initial page load are able to handle subsequent navigations and requests for data without the need for a complete reload
…
. Recall that Controllers respond to requests and perform appropriate actions which may result in changes to the Model and updates to the View. In a single-page application, rather than having requests in the traditional sense, we have events. Events can be traditional browser DOM events (e.g., clicks) or internal application events
…
('name'); console.log(names); // logs: ['John', 'Harry', 'Steve'] RESTful Persistence Thus far, all of our example data has been created in the browser. For most single page applications, the models are derived from a data store residing on a server. This is an area in which Backbone dramatically simplifies the code you need
by Brad Green and Shyam Seshadri · 15 Mar 2013 · 196pp · 58,122 words
applications create their HTML by assembling and joining it with data on the server, and then shipping the finished pages up to the browser. Most single-page applications—also known as AJAX apps—do this as well, to some extent. Angular is different in that the template and data get shipped to the
…
that looks like Figure 2-4. Figure 2-4. Focus directive Validating User Input Angular automatically augments <form> elements with several nice features suitable for single-page applications. One of these nice features is that Angular lets you declare valid states for inputs within the form and allow submission only when the entire
…
. The Templates Let us start by taking a look at the outermost, main template, which is the index.html. This is the base of our single-page application, and all the other views are loaded within the context of this template: <!DOCTYPE html> <html lang="en" ng-app="guthub"> <head> <title>GutHub - Create
…
’s text is shown (a very boring “Loading…” in this case) as needed. Link href Values The hrefs link to the various pages of our single-page application. Notice how they use the # character to ensure that the page doesn’t reload, and are relative to the current page. AngularJS watches the URL
…
cart example brief explanation, An Example: Shopping Cart discount application, Observing Model Changes with $watch Simple optimization, Compilation single-instance objects, Organizing Dependencies with Modules single-page applications, Angular vs. other apps, Client-Side Templates singleton objects, Organizing Dependencies with Modules Smalltalk, Model View Controller (MVC) Socket.IO, Using Socket.IO–Using Socket
by Olga Filipova · 13 Dec 2016 · 292pp · 66,588 words
by Andrea Passaglia · 27 Apr 2017 · 550pp · 84,515 words
by Mitchel Kelonye · 19 Oct 2014 · 266pp · 38,397 words
by David N. Blank-Edelman · 16 Sep 2018
by Callum Macrae · 23 Feb 2018 · 296pp · 41,381 words
by Mark Bates · 2 Jun 2012 · 323pp · 65,306 words