Windows-specific code for the GPII realtime framework
C C++ Inno Setup JavaScript Objective-C Shell Batchfile
Pull request Compare This branch is even with GPII:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
gpii/node_modules
listeners
provisioning
tests
.eslintrc.json
.gitignore
.project
Gruntfile.js
LICENSE.txt
README.md
Vagrantfile
gpii.js
index.js
package.json

README.md

GPII for Windows

Contains platform-specific components of the GPII architecture for Windows. See http://gpii.net/ for overall details of the GPII project. After checkout out using git, this project will require node.js and npm to be installed - please consult http://wiki.gpii.net/w/Setting_Up_Your_Development_Environment for installation instructions.

Note that tests and function involving the High Contrast setting will fail on all current versions of Windows (including Windows 7 SP1 and Windows 8 SP2) unless the following hotfix from Microsoft is applied: http://support.microsoft.com/kb/2516889

See http://issues.gpii.net/browse/GPII-49 for more details of this issue.

Building

This package depends on the node 4.x LTS infrastructure - at the time of writing, node 4.4.1 and npm 2.1.14.

To build the GPII for Windows, perform the following:

git clone https://github.com/GPII/windows.git
cd windows
npm install

Test VM

It is possible to provision a Windows VM for testing purposes. Please ensure you have met these VM requirements before proceeding. After that you can use the vagrant up command to create an instance of a Windows 10 Evaluation VM which will boot an instance of the Windows 10 VM, pull in the GPII Framework's npm dependencies, and then build it.

If this is your first time creating this VM an 8 GB download will take place. The downloaded image will be valid for 90 days after which the Windows installation will no longer be useable. To remove an expired image you can use the vagrant box remove "inclusivedesign/windows10-eval" command.

Once the VM has finished booting up you will need to type the vagrant reload command to cause it to restart. This is required so changes made to the Windows VM's PATH environment variable as part of the provisioning process are available in terminal sessions. This step is a temporary workaround and will be removed in the near future.

Now you can open a command prompt window and use the following commands to test the framework:

cd c:\vagrant
node tests\UnitTests.js
node tests\AcceptanceTests.js builtIn