Book Image

Getting Started with NativeScript

By : Nathanael J. Anderson
Book Image

Getting Started with NativeScript

By: Nathanael J. Anderson

Overview of this book

NativeScript allows you to build a fast cross-platform application that has a native UI. NativeScript is a true cross-platform framework that generates native speed applications using the native components of the host platform, all using JavaScript. Although NativeScript allows you to build your application in JavaScript, you have full access to the host OS from your code, allowing you to easily tweak or use new platform features instantly at native code speeds. Whether you have already developed multiple applications or zero applications, this book will help you to develop your next application in a cross-platform framework quickly, saving you a massive amount of time and money. This book concisely shows you NativeScript’s built-in framework that allows you to rapidly develop a fully-working compiled cross-platform application in just a few chapters. It starts by laying the foundation of NativeScript and working through the fundamentals to create a basic shell of the application. Moving on, you’ll see how to build a full-fledged application step by step. We’ll show you how to use plugins, and how to communicate with the native OS libraries easily so that you can customize your application as if your app was created in Java or Objective C. We then deal with the issues that arise from being cross platform and compensate for the different screen sizes, screen resolutions, and device abilities. Finally, we progress to testing and deploying your app.
Table of Contents (15 chapters)
Getting Started with NativeScript
About the Author
About the Reviewer

Understanding the call stack

We will switch tracks. The other side of the equation is debugging your application when it breaks. Nobody is perfect at coding, so understanding the call stack is an important factor in figuring out why your application has just crashed. Both Android and iOS report the call stack slightly differently. So, we shall examine Android first and then finish up with iOS call stack. So, open up your main-page.js file, and on line three, add the bogus code: Stock.blah();.

Android call stack

On Android, you get the call stack in two different places. When the application crashes, it normally creates a log in the actual application that you can view and it looks like this:

As you can see, about half way down on the screen, in the error report, there is the actual error. The error is TypeError: cannot read property 'blah' of undefined. In this case, I put it on line 3, column 6. In this case, the error actually points to the issue directly. Sometimes, you get lucky, and the...