Book Image

Mastering Ext JS

By : Loiane Groner
Book Image

Mastering Ext JS

By: Loiane Groner

Overview of this book

<p>Ext JS 4 is a JavaScript framework that provides you with the resources to build multi-browser, high-performance, and rich Internet applications.<br /><br />Mastering Ext JS is a practical, hands-on guide that will teach you how to develop a complete application with Ext JS. You’ll begin by learning how to create the project’s structure and login screen before mastering advanced level features such as dynamic menus and master-detail grids, before finally preparing the application for production.<br /><br />Mastering Ext JS will help you to utilize Ext JS to its full potential and will show you how to create a complete Ext JS application from the scratch, as well as explaining how to create a Wordpress theme.</p> <p><br />You will learn how to create user and group security, master-detail grids and forms, charts, trees, and how to export data to excel including PDF and images, always focusing on best practices.</p> <p><br />You will also learn how to customize themes and how to prepare the application to be ready for deployment upon completion. Each chapter of the book is focused on one task and helps you understand and master an individual aspect of the application.</p> <p><br />By the end of the book, you will have learned everything you need to know to truly master Ext JS and to start building advanced applications.</p>
Table of Contents (20 chapters)
Mastering Ext JS
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Presenting the tables


If we open and analyze the ER (Entity Relationship) diagram that comes with the Sakila installation, we will notice the following tables:

These tables can exist independently of the other tables, and we are going to work with them in this chapter.

When we open the SQL Editor in MySQL Workbench, we can select a table; right-click on it and select Edit Table Data. When we choose this option, a new tab will be opened and it looks like the following:

The preceding table is the actor table. The idea is to implement screens that look like the preceding screenshot for each of the tables that we selected: Actors, Categories, Languages, Cities, and Countries as displayed in the following screenshot (which is the final result of the code that we will be implementing in this chapter):

Our goal in this chapter is to minimize the amount of code to implement these five screens. This means that we want to create the most generic code possible, which will facilitate future code fixes,...