Mercurial > hg > nodescore
comparison www/old/index.html~ @ 42:49c94f63b8b0
css for nexus 7 and associated files- archive m.a added - remove later
| author | tzara <rc-web@kiben.net> |
|---|---|
| date | Tue, 04 Sep 2012 07:25:49 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 41:56767c69b7c4 | 42:49c94f63b8b0 |
|---|---|
| 1 <!DOCTYPE html> | |
| 2 <html> | |
| 3 <head> | |
| 4 <script src="/js/stopwatch.js" type="text/javascript" charset="utf-8"></script> | |
| 5 <link href="/stylesheets/style.css" rel="stylesheet"> | |
| 6 <script src="/socket.io/socket.io.js"></script> | |
| 7 <script src="http://code.jquery.com/jquery-1.6.1.min.js"></script> | |
| 8 <script src="/js/socket-ctrl.js"></script> | |
| 9 </head> | |
| 10 | |
| 11 <body> | |
| 12 <style type="text/css">body{ background-color: white; }</style> | |
| 13 | |
| 14 <div id="title"> | |
| 15 <h1>NodeScore</h1> | |
| 16 </div> | |
| 17 | |
| 18 <br/> | |
| 19 <img src="img/chromiumlogo.png" width="30" height="30"/> | |
| 20 <img src="img/nodejs-dark.png" height="30"/> | |
| 21 <img src="img/ECMAScript.png" height="30"/> | |
| 22 | |
| 23 <br/><br/> | |
| 24 | |
| 25 <div class="readme"> | |
| 26 | |
| 27 <h2>What is NodeScore?</h2> NodeScore is a framework to facilitate | |
| 28 networked telematic ensemble performance. As a framework it uses the | |
| 29 "screen score" as its paradigm. While it could be used to syncronise | |
| 30 any type of telematic event/performance in this context it is aimed at | |
| 31 the musical performance. | |
| 32 | |
| 33 <p> The goal of the NodeScore framework is to allow performers | |
| 34 who are connected to a network via a computer/tablet/mobile device to | |
| 35 syncronise to a master clock and recieve instructions, in | |
| 36 realtime,from a central "conductor/director" as well as being able to | |
| 37 communicate with one another. | |
| 38 </p> | |
| 39 <p>As performers may be geographically dispersed the technical setup | |
| 40 needs to be trivial, this is why NodeScore uses the Internet browser | |
| 41 as it is a cross-platform, standards compliant | |
| 42 environment that will run on anycomputer without complex setup and | |
| 43 installation process. All that the performers involved in a NodeScore | |
| 44 performance need to do is open a browser such as Google's Chrome and | |
| 45 point it to the address of the NodeScore server, login and await | |
| 46 instructions that shall be displayed in the browsers window. | |
| 47 </p> | |
| 48 <p>The nature of these instuctions is the left to the composer, the | |
| 49 only prerequisite when composing for the NodeScore framework is that | |
| 50 the instructions are formatted in HTML5. This allows for the | |
| 51 incorporation of a wide range of rich media content such as images, | |
| 52 video, sound and animated SVG as well as simple plain text | |
| 53 instructions. Any medium that can be displayed in an internet web | |
| 54 browser maybe used in a NodeScore composition. | |
| 55 | |
| 56 Other features include a shared, embedded network stopwatch and a | |
| 57 live-chat window to facilitate syncronisation and communication | |
| 58 between partisipants in the performance.</p> | |
| 59 <h2>How does NodeScore work?</h2> The control interface for | |
| 60 NodeScore is a webpage displayed in an internet web browser, from this | |
| 61 control page the "conductor/director" can issue the precomposed, HTML5 | |
| 62 formated, compositional instructions. These instrutions can be | |
| 63 deployed to the ensemble as a whole or targeted at specific | |
| 64 perfomers. Once the instruction is deployed by the director it is | |
| 65 instantly presented in the web browser of the performer/s. | |
| 66 | |
| 67 <p>In a NodeScore performance the conductor/director also becomes | |
| 68 active in the compositional process as he she decides who plays what | |
| 69 material when. In this way NodeScore can be seen as an evolution of | |
| 70 methods used by composers from Lutoslawski (Jeux vénitiens to Zorn | |
| 71 ("Cobra") amongst others, where musicians are given cues chosen by the | |
| 72 director indicating certian prearranged stratagies. NodeScore however | |
| 73 alows much more complex media to be incorporated in the instructions | |
| 74 as well as facilitating networked telematic performances in this | |
| 75 style. | |
| 76 </p> | |
| 77 | |
| 78 <h2>How is this achived technically?</h2> NodeScore uses realtime web | |
| 79 technologies including the node.js server software allowing serverside | |
| 80 javascript as well as websockets. "Websockets" allows the server to | |
| 81 push content to the clients without them requesting it first as is | |
| 82 traditionally the case. <p>This has been possible in the past through a | |
| 83 technique called "longpolling", though this was quite inefficient | |
| 84 compatered to websockets which allow a persistant live connection | |
| 85 between server and client. Through this connection the server can push | |
| 86 content to the client in realtime for instant displayed in their | |
| 87 browser.</p> | |
| 88 | |
| 89 <h2>Browser Compatability:</h2> This project uses some bleeding | |
| 90 edge network technologies his means it will not currently work in all | |
| 91 browsers, some versions of Firefox have disabled websockets for | |
| 92 security reasons, also different browsers deal with CSS scaling in | |
| 93 different ways for example. Recent versions of Chromium, Google Chrome or | |
| 94 Firefox are recomended. | |
| 95 | |
| 96 </div> | |
| 97 | |
| 98 <br/> | |
| 99 | |
| 100 | |
| 101 <br/> | |
| 102 <script type="text/javascript" src="/js/footer.js"> </script> | |
| 103 | |
| 104 </body> | |
| 105 | |
| 106 </html> |