Skip to content

Commit

Permalink
Merge pull request rage#316 from gardalic/patch-2
Browse files Browse the repository at this point in the history
Fix a few typos
  • Loading branch information
ConcernedHobbit authored Mar 1, 2022
2 parents 5426563 + 2f1b633 commit 9dcf387
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions data/part-13/5-multiple-views.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ hidden: false

<text-box variant='learningObjectives' name='Learning Objectives'>

- You proctice adding multiple views to a graphical interface.
- You practice adding multiple views to a graphical interface.
- You know methods for changing the view.
- You know methods for separating the application logic and the user interface logic

Expand All @@ -26,7 +26,7 @@ Thus far our graphical interfaces have always included only one view. Next, we'l

<!-- Yleisesti ottaen näkymät luodaan Scene-olion avulla, joiden välillä siirtyminen tapahtuu sovellukseen kytkettyjen tapahtumien avulla. Alla olevassa esimerkissä on luotu kaksi erillistä Scene-oliota, joista kummallakin on oma sisältö sekä sisältöön liittyvä tapahtuma. Alla Scene-olioihin ei ole erikseen liitetty käyttöliittymän asetteluun käytettyä komponenttia (esim. BorderPane), vaan kummassakin Scene-oliossa on täsmälleen yksi käyttöliittymäkomponentti. -->

Generally the views are created as Scene-objects and the transitioning between them happens with events bound to the application. The example below has two Scene objects which both have their own content and an event related to the content. Instead of having an object for laying out components (such as BorderPane) in the example Scene objects, both objects have just one user interface component.
Generally the views are created as Scene-objects and the transitioning between them happens with events bound to the application. The example below has two Scene objects which both have their own content and an event related to the content. Instead of having an object for laying out components (such as BorderPane) in the example Scene objects, both objects have just one user interface component.


```java
Expand Down Expand Up @@ -203,7 +203,7 @@ The example takes advantage of GridPane's and StackPane's built in setPrefSize a

<!-- Luo tehtäväpohjassa olevaan luokkaan TervehtijaSovellus sovellus, jossa on kaksi näkymää. Ensimmäisessä näkymässä on tekstikenttä, jolla kysytään käyttäjän nimeä. Toisessa näkymässä käyttäjälle näytetään tervehdysteksti. Tervehdystekstin tulee olla muotoa "Tervetuloa nimi!", missä nimen paikalle tulee käyttäjän kirjoittama nimi. -->

In the exercise templare there is a class called GreeterApplication. Create in it an application with two views. The first view should have a text field that's used to ask for the user's name. The second view then shows the user a greeting text. The greeting should be of the form "Welcome name!" where the user's name is inserted in place of 'name'.
In the exercise template there is a class called GreeterApplication. Create in it an application with two views. The first view should have a text field that's used to ask for the user's name. The second view then shows the user a greeting text. The greeting should be of the form "Welcome name!" where the user's name is inserted in place of 'name'.

<!-- Esimerkki sovelluksen toiminnasta: -->

Expand Down

0 comments on commit 9dcf387

Please sign in to comment.