| ... | ... | @@ -225,3 +225,11 @@ public HelloWorldApplication(String newPropertiesFileUri) throws BuildException |
|
|
|
* Next, we instruct the **contentManager** to build all content defined in the scenario.
|
|
|
|
* As we're going to see when we're looking in detail at the Content class (**lu.list.itis.dkd.tui.content** package), each Content object has an **initialise()** method it may use for its internal houskepping. By calling the **contentManager**'s **initAll()** method, we make sure that the **initialise()** method of each Content object that has been loaded from the scenario will be called.
|
|
|
|
* Last but not least, we call the **TangibleApplications**'s **doneLoading()** method, which will, among other things, make sure the splash-screen is being replaced with the actual content of the application.
|
|
|
|
|
|
|
|
#### HelloWorldContentManager
|
|
|
|
The HelloWorldContentManager class, as its name implies, takes care all of things related to **Content**. Perhaps now is a good time to give a first definition of what **Content** is in the context of a TULIP application. Content in the context of a TULIP application encompasses all entities which are not directly linked to tangible interactions. You may think of content
|
|
|
|
|
|
|
|
|
|
|
|
```java
|
|
|
|
public class HelloWorldContentManager extends TangibleContentManager
|
|
|
|
``` |
|
|
\ No newline at end of file |
