User Tools

Site Tools


composingintroduction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
composingintroduction [2015/06/23 15:09]
richard
composingintroduction [2015/06/23 17:31] (current)
Line 39: Line 39:
  
 <​code>​ <​code>​
-new Role("​Lead"​);​ new Role("​Rhythm",​ {maxPerformers:​ 3});+new Role("​Lead"​); ​ 
 +new Role("​Rhythm",​ {maxPerformers:​ 3});
 </​code>​ </​code>​
  
Line 46: Line 47:
 ===== Events and performance ===== ===== Events and performance =====
  
-In dfscore an Event can be thought of as a page or view. The composer can include text instructions with TextEvent, formatted or arbitrary HTML with HtmlEvent, Vextab markup notation displays with ScoreEvent, static images/​graphics with ImageEvent and client-side scripted events with arbitrary functionality using ScriptEvent. These different types are detailed in the API reference.+In dfscore an Event can be thought of as a page/pane or view. The composer can include text instructions with TextEvent, formatted or arbitrary HTML with HtmlEvent, Vextab markup notation displays with ScoreEvent, static images/​graphics with ImageEvent and client-side scripted events with arbitrary functionality using ScriptEvent. These different types are detailed in the API reference.
  
 Events are performed by using the **perform****()** ​ directive, referencing the role, event and duration (in milliseconds) to display the event for. The event referenced can be created before the perform directive or within it. Events are performed by using the **perform****()** ​ directive, referencing the role, event and duration (in milliseconds) to display the event for. The event referenced can be created before the perform directive or within it.
Line 77: Line 78:
 This will result in all roles displaying "Hello everyone"​ for six seconds. Depending on the durations that have led to the current point, this may not necessarily mean that the event will be synchronised between roles. However in this case, as both of the roles, //​Lead// ​ and //​Rhythm// ​ have performed synchronised events (ie, 10s then 7s), the "Hello everyone"​ message will be synchronised. This will result in all roles displaying "Hello everyone"​ for six seconds. Depending on the durations that have led to the current point, this may not necessarily mean that the event will be synchronised between roles. However in this case, as both of the roles, //​Lead// ​ and //​Rhythm// ​ have performed synchronised events (ie, 10s then 7s), the "Hello everyone"​ message will be synchronised.
  
-Now another two events will be predefined (created before a perform() instruction,​ with a name). For this oneit won't show the progress bar along the bottom of the screen, nor the preview of the next event (by default these are turned on). These parameters can be set using {curly bracket} parameters which you can find out more about in the Events section of the API reference.+Now another two events will be predefined (created before a perform() instruction,​ with a name). For these twodfscore ​won't show the progress bar along the bottom of the screen, nor the preview of the next event (by default these are turned on). These parameters can be set using {curly bracket} parameters which you can find out more about in the Events section of the API reference.
  
 <​code>​ <​code>​
Line 105: Line 106:
 ===== Putting it together ===== ===== Putting it together =====
  
-<​code>​ 
 That's a basic introduction to creating a simple dfscore composition just using text cues. Here's what it looks like with each of the bits detailed in the tutorial. In javascript, one way of using comments is by prepending text with // (two slashes) which you can see in the assembly below. ​ // That's a basic introduction to creating a simple dfscore composition just using text cues. Here's what it looks like with each of the bits detailed in the tutorial. In javascript, one way of using comments is by prepending text with // (two slashes) which you can see in the assembly below. ​ //
-</​code>​ 
  
 <​code>​ <​code>​
Line 134: Line 133:
  
   // pre-define two events with the progress bar and event preview turned off   // pre-define two events with the progress bar and event preview turned off
-  new TextEvent("​Hello brave new worsld", "​brave1",​ { progressBar:​ false, showNextEvent:​ false});+  new TextEvent("​Hello brave new world", "​brave1",​ { progressBar:​ false, showNextEvent:​ false});
   new TextEvent("​Hello brave old world",​ "​brave2",​ { progressBar:​ false, showNextEvent:​ false});   new TextEvent("​Hello brave old world",​ "​brave2",​ { progressBar:​ false, showNextEvent:​ false});
  
composingintroduction.txt · Last modified: 2015/06/23 17:31 (external edit)