googlearchive / chromeweblab Goto Github PK

We really need this, there area a lot of dependencies

There are events that are emitted before a handler is set up to catch it. This was noticed when trying to build the LittlePrinter driver.

This was not noticed in other parts as there is a shim which delays calls by X milliseconds.

Have an Arduino attached to the hub via a serial port. Send the orchestra configuration over it.

The Arduino will process the orchestra pattern and activate a series of 4 solenoids that act as the notes on an instrument. Or 8 if it is two player!

The player can then attach the solenoid to any surface to create different sounds.

Inspiration: https://github.com/mcqn/RFIDrum/blob/master/RFIDrum.ino
http://uk.farnell.com/jsp/displayProduct.jsp?sku=9591664&CMP=KNC-GUK-FUK-GEN-LISTINGS&gross_price=true&mckv=8xfSXgBz|pcrid|23407365549|plid|

http://jarkman.co.uk/catalog/robots/sketchy.htm

• Update Sketchbots/README.md and Sketchbots/hw/MindstormsNXT/README.md to include instructions
• add photos/videos for the docs to the repo (probably in Sketchbots/doc/...)

Following the instructions to initialize the submodules fails. Looks like it has not been commited correctly.

http://www.polargraph.co.uk/

Finish what has been started here:
https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Sketchbots/hw/MindstormsTutorial/README.md

See electronics list in https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Orchestra/hw/tutorial/Readme.md

This would allow some really cool demos to be built.

It's a pretty complex subject that needs to be explained more in-depth.

http://makerblock.com/2012/01/wanna-make-a-drawbot/

The hub has a pluggable module system that lets you strip out the OSC/MIDI stuff that is alrady there.

A developer could create an Arduino sketch that reads from the serial port and based on the data toggles output pins that attach to an LED array and will replicate what the user sees on the sequencer board.

For example, even though this is Bluetooth you could build this: http://www.youtube.com/watch?v=4lL3AH8_jH4

Or you could get a couple of these and patch them in to a grid... http://oomlout.co.uk/collections/extra-pieces/products/led-matrix-8x8-bicolour

Also, this machine needs a name!

Docs ought to go in Orchestra/hw/README.md etc.

See electronics list in https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Orchestra/hw/tutorial/Readme.md

It should:

• Check all the dependencies
• launch the UI server --- optional output to a file
• launch the robot controller --- optional output to a file
• open the browser to the page.

The JS is a bit of a mess, it needs to be formatted correctly and consistently.

2 or 4 spaces.

the docs should include these checks/edits:

• Is the correct servo voltage 6v or 7.4v?
• Which type of arm should be attached to the servo spindle?
• Are any adaptors/modifications to the cable used to connect to the arduino?

In https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Sketchbots/sw/robotcontrol/src/draw_machines/MindstormsNXT/Robot3Axis.js

The user should just be able to print to a printer.

Need to write a doc, create a video.

Shall we add a pre-commit hook to make sure the project is adhering to the style guide before it gets committed?

Very trivial to implement but good to keep consistency in the project's codebase

The UI for the Sketchbot and the Orchestra need to be updated significantly to get it working on mobile.

Currently it sends very specific commands, this stops other people from creating drivers to existing hardware that can't be changed.

Are the two different plywood thickness specs correct?
https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Orchestra/hw/tutorial/Readme.md

http://bergcloud.com/littleprinter/
http://remote.bergcloud.com/developers

In the file ./Orchestra/sw/realtimeserver/weblab/orchestra/LiveManager.js there are files being required that no longer exist in the project files.

21 var PlayerLayout = require("./data/PlayerLayout"); 22 var MuseumUser = require("./user/MuseumUser"); 23 var MuseumClient = require("./user/MuseumClient"); 24 var MessageEncoder = require("./utils/MessageEncoder"); 25 var MessageIds = require("./constants/MessageIds");

What shall we do about this, if anything?

The MAX integration is a little abstract and not documented.

Now that I have MAX licence we should be able to at least document what is happening and what the OSC->MIDI software is doing.

Markup and styling

• Add meta viewport definition (see #51).
• Fix CSS as a consequence of above.
• Ensure scripts pulled in #63 (bbab7cf and 59ad9a4) are beautified.

(I'm happy to take this one.)

Add to 12v power supply line in electronics list of https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Orchestra/hw/tutorial/Readme.md

e.g. "12v 1.5A power supply" and update link to correct part.

The Sketchbot produces a series of lines and vectors which in isolation might not be great for a RepRap however it could either just output everything separately or create a simple base, or join every line together.

In the docs, we need a good link to get ahold of the circular base (or instructions for how to make it) - https://github.com/GoogleChrome/ChromeWebLab/blob/hardware-tutorials-dev/Orchestra/hw/tutorial/Readme.md

They have a hosted set of endpoints that let you send drawings to. We should just be able to clone the NoMachine/DrawMachine.js file and just integrate the required web requests to it.

http://cursivedata.co.uk/

TODO we can split these out if needs be:

• Define the viewport
• Define the breakpoints for the media queries
• Check it all works with Touch (you can emulate this on a desktop in Chrome DevTools)
• Create the UI for the appropriate break points.

Currently the Sketchbot looks like this on a desktop:

However, on a mobile screen it is all cut-off

I am not quite sure how it should appear on mobile yet, so comments should include screen shots.

TODO we can split these out if needs be:

• Define the viewport
• Define the breakpoints for the media queries
• Check it all works with Touch (you can emulate this on a desktop in Chrome DevTools)
• Create the UI for the appropriate break points.

Currently Orchestra looks like this on desktop

And like this on mobile

I am not quite sure how it should appear on mobile yet, so comments should include screen shots.