Skip to content

Instantly share code, notes, and snippets.

@stepheneb
Created November 24, 2008 00:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save stepheneb/28329 to your computer and use it in GitHub Desktop.
Save stepheneb/28329 to your computer and use it in GitHub Desktop.
-Dotrunk.view.export_image=true
otrunk.view.frame_title
Set's the title of the OTViewer window frame.
otrunk.view.hide_tree
Hides a JTree navigation component that appears on theleft.
otrunk.view.hide_tree
Shows the Java console.
Description of the difference between running an activity in learner mode and author mode
Running an OTrunk example in learner mode uses the default view mode which assumes a learner. In addition if you use the File menu to save the otml only the differences between the activity otml and the changes will be saved. The otml saved is the learner difference otml and is often much smaller than activty otml.
Running an OTrunk example in author mode sets the following jnlp properties:
* otrunk.view.author=true
* otrunk.view.mode=authoring
Setting otrunk.view.author to true causes the entire OTrunk state to be saved as otml when a File save is performed. Setting otrunk.view.mode to authoring is used in the view system to enable authoring affordances in the views. Many examples do not have special authoring views. The Basic Example: document-edit.otml does have both authoring and student view modes.
-Dotrunk.view.author=true
-Dotrunk.view.debug=true
-Dotrunk.view.mode=student
Turns on display of the memory status indicator status
-Dotrunk.view.status=true
-Djava.library.path="${workspace_loc:sensor-native}/bin"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment