You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/chapters/chapter3.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,7 @@ TODO: Transition
145
145
146
146
### Structuring your app
147
147
148
-
There are many reasons to segment any application into modular units, and you can [read about the various benefits on Wikipedia](https://en.wikipedia.org/wiki/Modular_programming). However, keeping NativeScript apps modular has one unique benefit: the ability to share the code you write between Angular-2-built web apps, and Angular-2-built native apps.
148
+
There are many reasons to segment any application into modular units, and you can [read about the various benefits on Wikipedia](https://en.wikipedia.org/wiki/Modular_programming). Modularizing NativeScript apps, in addition, has one unique benefit: the ability to share the code you write between Angular-2-built web apps, and Angular-2-built native apps.
149
149
150
150
Even if you have no plans to create an Angular 2 web app, separating out your code is still advantageous for a number of other reasons—testability, ease of maintenance, and so forth—but if you _do_ have plans to build an Angular 2 web app, having a chunk of functionality that you can reuse in your native and web apps can be an invaluable time saver.
151
151
@@ -176,6 +176,7 @@ Here you import the `User` class that you just defined. Note the parallel betwee
176
176
177
177
Next, replace the existing `AppComponent` definition with the one below, which uses the `User` class you just imported.
178
178
179
+
<!-- Todo, explain the isLoggingIn piece - from the exercise above I think. The button XML needs to be edited -->
179
180
```JavaScript
180
181
exportclassAppComponent {
181
182
user: User;
@@ -243,7 +244,7 @@ A login screen isn’t all that useful if it doesn’t actually log users into a
243
244
244
245
For the purposes of this tutorial we prebuilt a handful of backend endpoints using [Telerik Backend Services](http://www.telerik.com/platform/backend-services), and we’ll be using those endpoints to make this app functional. Let’s see how they work.
245
246
246
-
> **NOTE**: You don't have to use Telerik Backend Services to hit your app’s backend; you can use any HTTP API in a NativeScript app. Telerik Backend Services is convenient for us to use for this tutorial because it lets us spin up HTTP endpoints quickly.
247
+
> **NOTE**: You don't have to use Telerik Backend Services to power your app’s backend; you can use any HTTP API in a NativeScript app. Telerik Backend Services is convenient for us to use for this tutorial because it lets us spin up HTTP endpoints quickly.
247
248
248
249
<h4class="exercise-start">
249
250
<b>Exercise</b>: Add an Angular 2 service
@@ -289,7 +290,7 @@ export class UserService {
289
290
290
291
TODO: Explain that mess above, and probably break it into a lot of steps.
291
292
292
-
In app.component.ts. Add the lines below to the top:
293
+
In `app.component.ts`, add the lines below to the top:
0 commit comments