Book Image

Angular Services

Book Image

Angular Services

Overview of this book

A primary concern with modern day applications is that they need to be dynamic, and for that, data access from the server side, data authentication, and security are very important. Angular leverages its services to create such state-of-the-art dynamic applications. This book will help you create and design customized services, integrate them into your applications, import third-party plugins, and make your apps perform better and faster. This book starts with a basic rundown on how you can create your own Angular development environment compatible with v2 and v4. You will then use Bootstrap and Angular UI components to create pages. You will also understand how to use controllers to collect data and populate them into NG UIs. Later, you will then create a rating service to evaluate entries and assign a score to them. Next, you will create "cron jobs" in NG. We will then create a crawler service to find all relevant resources regarding a selected headline and generate reports on it. Finally, you will create a service to manage accuracy and provide feedback about troubled areas in the app created. This book is up to date for the 2.4 release and is compatible with the 4.0 release as well, and it does not have any code based on the beta or release candidates.
Table of Contents (15 chapters)
Angular Services
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Chapter 7.  The Report Generator Service - Creating Controllers to Set Report Template

In this chapter, we are going to create a service to read the network graph data (generated from the previous chapter), mix it with summary details created from the corpus, and generate various reports. The report will solely rely on the data that we feed it. So the first two requirements are:

  • Corpus summary (corpus size, vocabulary size, average article size, and so on)

  • Network graph data

When these information sources are in place, we can feed them (as raw data) to the Report Generator and make it generate different types of reports (with different levels of details).

That means the report generator should have controllers to set the template for the report (child views) and those templates should get their setup from a configuration mechanism saved permanently somewhere. It is nice to have a mechanism that creates and saves various configurations for different themes as well. At the end we need to have...