admin Comment(0)

Recipes with Practical Concepts and Techniques For Rapid Web Application Development Updated Continuously; Paperback N/A; eBook HTML , PDF, ePub, Mobi (Kindle); Language: English; ISBN/ASIN: JavaScript Frameworks (jQuery,, AngularJS,,. Read and Download Links. The 15 best ebooks, such as ANGULARJS, AngularJS, Learn With, Pro This book provides source code for download; you can download the source code for . Over 90 hands-on recipes to architect performant applications and. Ebooks give you a structural and organized way to learn a new topic, Recipes With AngularJS is written by Frederik Dietz and is available to.

Language: English, Spanish, Portuguese
Country: Lithuania
Genre: Fiction & Literature
Pages: 497
Published (Last): 22.10.2015
ISBN: 470-6-79856-309-3
ePub File Size: 25.50 MB
PDF File Size: 15.15 MB
Distribution: Free* [*Free Regsitration Required]
Downloads: 32309
Uploaded by: SHELLEY

Each recipe solves a specific problem and provides a solution and in-depth src = " 4 angularjs//" > 5 Make sure you actually download the javascript file and load it via script tag. AngularJS Recipes Download. 15 About this eBook; An Introduction to AngularJS; How AngularJS Extends HTML; ng-init directive for. Read the best free ebooks about AngularJS framework. AngularJS is a toolset for building the framework most suited to your Recipes with

It gives Javascript developers a highly structured approach to developing rich browser-based applications which, leads to very high productivity. If you are using Angular. Each recipe solves a specific problem and provides a solution and in-depth discussion of it. All code examples in this book can be found on Github. And of course the whole development team behind Angular. In order to get your first Angular. You can check out a complete example on github.

There are also sections on how to use KarmaJS to test your applications, how to use Firebase, miscellaneous tricks and troubelshooting you can use. AngularJS Succinctly contains 10 chapters of problems, solutions and in-depth discussion to help you grasp the idea of Angular quickly.

Learn the basics on using controllers, directives and filters all the way to integrated platforms like Ruby and Node. All code examples are hosted on GitHub; you can grab them there to practice on your own.

It carries plenty of learning materials from multiple sources, from official documentations, videos, other books and plenty of screencast by Egghead. Adopting a gradual easy to advanced way of building simple applications with Angular, this book contains plenty of checklists for you to keep track of what you have learned. You will need to create a skeleton app, build, test the run features, and before you know it, you have an Angular app powered by Rails.

The book contains an introduction, four chapters and a concluding chapter. Please enable JavaScript in your browser to enjoy a better experience. Show Comments. This gives us a handful of nice methods including query , get , save , remove and delete to work with our resource.

In the example above we implement several controllers to cover the typical use cases. The get and query methods expect three arguments, the request parameters, the success and the error callback. The save method expects four arguments, the request parameters, the POST data, the success and the error callback. This allows you to easily fetch a resource and update it as in the following example:.

It is important to notice that the get call immediately returns an empty reference - in our case the post variable. Note that having an empty reference means that our post will not be rendered in the template.

Once the data is returned though, the view automatically re-renders itself showing the new data. What if your response of posts is not an array but a more complex json? This typically results in the following error:. Angular seems to expect your service to return a JSON array. We only change the configuration of the query action to not expect an array by setting the isArray attribute to false. Then in our controller we can directly access data.

This way you can easily reuse the same model in different controllers and test it more easily. As an example we will take the Twitter search API here. The HTML template lets you enter a search term in an input field and will render the search result in a list. It is a placeholder that is replaced with the real callback function, generated by Angular.

As an example, we want to call three services in sequence and combine the result of them. Let us start with a nested approach:. We call the get function three times to retrieve three JSON documents each with an array of strings. The all function combines multiple promises into a single promise and solves our problem quite elegantly. It is rather contrived but should give you an idea of how to use then to sequentially call functions and pass data along.

Since the all function returns a promise again we can call then on it. By returning the tmp variable it will be passed along to the then function as tmpResult argument. Before finishing this recipe let us quickly discuss an example where we have to create our own deferred object:. Using the defer method we create a deferred instance.

The function will immediately return the promise and therefore not render any result in our HTML template.

4 Free ebooks to learn AngularJS | jQuery By Example

After one second, the timer will execute and return our success or failure response. This deferredTimer can be triggered in our HTML template by wrapping it into a function defined on the scope:. Our startDeferredTimer function will get a success parameter which it passes along to the deferredTimer. The then function expects a success and an error callback as arguments which we use to set a scope variable deferredTimerResult to show our result. Note that it slightly changed from the previous recipe as the TwitterAPI is pulled out of the controller and resides in its own service now.

4 Free ebooks to learn AngularJS

Since we now have a clear separation between the service and the controller, we can simply inject the TwitterAPI into our beforeEach function. After the search is triggered we flush the httpBackend in order to return our mockData. Have a look at the ngMock. We will first look into client-side routing with hashbang URLs since it is the default mode, and then later, look at the new HTML5-based routing.

The route configuration is implemented in app. This example is based on the Angular Seed Bootstrap again and will not work without starting the development server.

The otherwise defined route redirects us from index. Take a closer look at the index. It shows a list of persons and therefore defines a ng-controller directive inside the template. Now for each person we also render a link to show the details via!

The controller will be scoped to the partial, which basically resembles our index. Let us come back to the ng-view directive. It is automatically bound to the router definition. Therefore you can currently use only a single ng-view on your page. For example, you cannot use nested ng-view s to achieve user interaction patterns with a first and second level navigation. Let us look into the HTML5-based approach next. We will use the same example but use the Express framework to serve all content and handle the URL rewriting.

There are no changes except for the html5Mode method, which enables our new routing mechanism. The Controller implementation does not change at all.

We have to take care of the partial loading though. Our Express app will have to serve the partials for us.

The initial typical boilerplate for an Express app loads the module and creates a server:. The Express route definition loads the partial with given name from the partials directory and renders its content. First we define the rendering of the index page, which contains the ng-view directive:. Let us quickly check the partials again. Note that they use the Jade template engine, which relies on indentation to define the HTML document:. Have a look at the complete example on Github and start the Express app with node app.

The redirect ensures that we actually end up at our root URL, which then kicks in our Angular app. Everything our app needs is loaded once from the server and cached client-side. If you have a hard time understanding the server implementation, I suggest you read the excellent Express Guide. Additionally, there is going to be an extra chapter, which goes into more details on how to integrate Angular.

When the user selects a menu item the client-side navigation will kick in as expected.

Table of Contents

The menuClass function is bound using the ngClass directive and updates the CSS class automatically for us depending on the current route. Redirect to a login page if the user is not yet logged in. Next we will define a login form to enter the username, skipping the password for the sake of simplicity:.

But, it exemplifies how to generally handle access to specific areas of your web app. When you open the app in your browser you will be redirected to the login app in all cases.

Only after you have entered a username can you access the other areas. The run method is defined in Module and is a good place for such a route change listener since it runs only once on initialization after the injector is finished loading all the modules.

Note that in order to skip this behavior when already navigating to the login page, we have to explicitly check the next templateUrl. Every website eventually uses some kind of form for users to enter data.

Angular makes it particularly easy to implement client-side form validations to give immediate feedback for an improved user experience. You wish to create a form to enter user details and capture this information in an Angular. Use the standard form tag and the ng-model directive to implement a basic form:. The novalidate attribute disables the HTML5 validations, which are client-side validations supports by modern browsers. In our example we only want the Angular.

The controller binds the form data to your user model and implements the submit function:. The initial idea when using forms would be to implement them in the traditional way by serialising the form data and submit it to the server.

Instead we use ng-model to bind the form to our model, something we have been doing a lot already in previous recipes. The submit button state is reflected in our wasSubmitted scope variable, but no submit to the server was actually done. The default behavior in Angular. We want to handle the submission in an application-specific way.

In fact there is even more going on in the background and we are going to look into the behavior of the form or ng-form directive in the next recipe. Let us start with the same form but let us add some HTML5 attributes to make the input required:.

It is still the same form but this time we defined the name attribute on the form and made the input required for the firstname. When starting with a fresh empty form, you will notice that Angular adds the css class ng-pristine and ng-valid to the form tag and each input tag. When editing the form the ng-pristine class will be removed from the changed input field and also from the form tag. Instead it will be replaced by the ng-dirty class.

Very useful because it allows you to easily add new features to your app depending on these states. In addition to these two css classes there are two more to look into. The ng-valid class will be added whenever an input is valid, otherwise the css class ng-invalid is added. Note that the form tag also gets either a valid or invalid class depending on the input fields.

Initially, the firstname and lastname input fields are empty and therefore have the ng-invalid css class, whereas the age input field has the ng-valid class. In the debug output we can check the validity and specific error for each named form input and the form itself.

With angularjs ebook download recipes

For validation, Angular provides built-in directives including required , pattern , minlength , maxlength , min and max.

You wish to show validation errors to the user by marking the input field red and displaying an error message. The CSS classes ensure that we initially show the fresh form without any classes. When the user starts typing in some input for the first time, we change it to either green or red. That is a good example of using the ng-dirty and ng-invalid CSS classes. We use the same logic in the ng-show directive to only show the error message when the user starts typing for the first time.

You wish to display form validation errors but the form is styled using Twitter Bootstrap.

Ebook angularjs recipes download with

When using the. The group div has the class control-group and the actual controls are further nested in another div element with the CSS class controls. Twitter Bootstrap shows a nice validation status when adding the CSS class error on the div with the control-group class.

Note that we use the ng-class directive on the control-group div. Again we check both the invalid and dirty flags because we only show the error message in case the user has actually changed the form. Note that this ng-class function usage is pretty typical in Angular since expressions do not support ternary checks. The Form Controller attributes form. Note that you have to assign a name attribute to the form element, otherwise form.

The angular-ui project offers a nice custom validation directive which lets you pass in options via expression. Let us have a look at the template first with the usage of the ui-validate Directive:.

First we need to explicitly list our module dependency to the Angular UI directives module. Make sure you actually download the javascript file and load it via script tag. Our blacklist contains the words we do not want to accept as user input and the notBlackListed function checks if the user input matches any of the words defined in the blacklist.

The ui-validate directive is pretty powerful since it lets you define your custom validations easily by just implementing the business logic in a controller function. For this example we will render a list of friends using the ng-repeat directive.

Using the built-in filter and orderBy filters we will filter and sort the friends list client-side. A plain text input field is used to enter the filter query and bound to the filter. Any changes are therefore directly used to filter the list. Chaining filters is a fantastic way of implementing such a use case as long as you have all the data available on the client. The filter Angular. It supports a String, Object or Function parameter. That way we can filter by name and age at the same time.

And lastly you could call a function defined in the controller, which does the filtering for you:. The filterFunction must return either true or false. In this example we use a regular expression on the name starting with Ma to filter the list. Use an HTML table element with the ng-repeat directive to render only the items for the current page. All the pagination logic should be handled in a custom filter and controller implementation. The offset Filter is responsible for selecting the subset of items for the current page.

It uses the slice function on the Array given the start param as the index. The initial idea of this pagination solution can be best explained by looking into the usage of ng-repeat to render the table rows for each item:. This will generate an array from the offset to the end of the array. Then we use the built-in limitTo filter to subset the array to the number of itemsPerPage.

All this is done on the client side with filters only. The controller is responsible for supporting a nextPage and prevPage action and the accompanying functions to check the disabled state of these actions via ng-class directive: The prevPage function first checks if it has not reached the first page yet before decrementing the currentPage and the nextPage does the same for the last page and the same logic is applied for the disabled checks.

This example is already quite involved and I intentionally omitted an explanation of the rendering of links between the previous and next buttons. The full implementation is online though for you to investigate. You cannot use the previous method with a filter since that would require all data to be available on the client. Instead we use an implementation with a controller only instead.

In order to simplify the example we will fake a server-side service by providing an Angular service implementation for the items. The service manages a list of items and has methods for retrieving a subset of items for a given offset and limit and the total number of items.

The controller uses dependency injection to access the Item service and contains almost the same methods as our previous recipe.

It fetches fresh items for the current page and the total number of items. So, on the client side we only have five items available as defined in itemsPerPage and when paginating we throw away the items of the previous page and fetch new items.

If you want to try this with a real backend you only have to swap out the Item service implementation. The solution is actually pretty similar to the previous recipe and uses a controller only again. The new items will be concatenated with the existing items using the Array concat function. The changes to pagedItems will be automatically rendered by the ng-repeat directive. The nextPageDisabledClass checks whether there is more data available by calculating the total number of pages in pageCount and comparing that to the current page.

In a web framework like Ruby on Rails, the form submit will lead to a redirect with the flash confirmation message, relying on the browser session. For our client-side approach we bind to route changes and manage a queue of flash messages.

Angularjs recipes ebook download with

In our example we use a home page with a form and on form submit we navigate to another page and show the flash message. We use the ng-view Directive and define the two pages as script tags here. Note that the flash message just like the navigation is always shown but conditionally hidden depending on whether there is a flash message available.

The interesting part is the flash service, which handles a queue of messages and listens for route changes to provide a message from the queue to the current page. The flash service is dependency-injected into the controller and made available to the scope since we want to use it in our template. When you press the submit button you will be navigated to the other page and see the flash message. The controller uses the setMessage function of the flash service and the service stores the message in an array called queue.

In the template we use ng-show to hide the div element with the flash messaging using flash. Since this is a service it can be used anywhere in your code and it will show a flash message on the next route change. Implement a directive for the contenteditable attribute and use ng-model for data binding.

The directive is especially interesting since it uses ng-model instead of custom attributes. It requires the ngModel controller for data binding in conjunction with the link function. The implementation binds an event listener, which executes the read function with apply. This ensures that even though we call the read function from within a DOM event handler we notify Angular about it.

The directive is surprisingly simple, leaving the ng-model aside. But without the ng-model support we would have to come up with our own model-attribute handling which would not be consistent with other directives. A dialog is called modal when it is blocking the rest of your web application until it is closed.

The controller only handles the button click and the showModal value used by the modal attribute. Do not forget to download and include the angular-ui. The full example is available on Github including the angular-ui module. The modal as defined in the template is straight from the Twitter bootstrap documentation. We can control the visibility with the modal attribute. Additionally, the close attribute defines a close function which is called whenever the dialog is closed.

Note that this could happen if the user presses the escape key or clicking outside the modal. Our own cancel button uses the same function to close the modal manually, whereas the okay button uses the ok function.

This makes it easy for us to distinguish between a user who simply cancelled the modal or actually pressed the okay button. We will use the Twitter search API for our example to render a list of search results. When pressing the button the AJAX request is run and the spinner image should be shown until the request is done. An Angular. Note that we use jQuery to show the spinner in the configuration step and hide the spinner in the interceptor.

The template is the easy part of this recipe since it renders a list of tweets using the ng-repeat directive. Let us jump straight to the interceptor code.

The interceptor is implemented using the factory method and attaches itself to the promise function of the AJAX response to hide the spinner on success or failure. In a similar manner we add the spinnerFunction to the default transformRequest list in order to call it before each AJAX request. We are using JSONP here to allow this code to be executed locally even though it is served by a different domain.

In this chapter we will have a look into solving common problems when combining Angular. The examples used in this chapter are based on an example application to manage a list of contacts.

We can now fetch a list of contacts using Contact. These actions can be directly mapped to the ContactsController actions in your Rails backend. The Rails action controller uses a Contact ActiveRecord model with the usual contact attributes like firstname, lastname, age, etc.

The route definition uses the Rails default resource routing and an api scope to separate the API requests from other requests. If you want to get up to speed with Ruby on Rails, I suggest that you look into the Rails Guides which will help you understand how all the pieces fit together.

If you are using a Rails version prior 3. To disable this behavior you can configure your Rails app accordingly. There are still inconsistencies between the Ruby and Javascript world. It uses transformers and inceptors to rename the attribute fields and handles the root wrapping behavior for you. Every request to the backend should initially render the complete page in order to load our Angular app. Only then will the client-side rendering take over.

Both will be handled by a layout controller with the sole purpose of rendering the initial layout. Let us have a look into the route definition again. First of all the filename ends with erb , since it uses ERB tags in the javascript file, courtesy of the Rails Asset Pipeline. If your Rails app is configured to use an asset host, the path will in fact be absolute. Rails already provides model validation support out of the box for us. Let us start with the Contact ActiveRecord model.

It defines a validation on the age attribute. It must be an integer and less or equal to 50 years. As an example let us look into the create action. Let us have a look at an example JSON response:.