The back end elements of the page consist of some Javascript for validation, some AJAX and PHP to write to the PostgreSQL.

The validation is used for verifying valid e-mails and to make sure necessary information is included before the data is submitted. The AJAX will be called when the information is submitted, parse the data to a PHP function to add the the data into the database tables via a PostgreSQL function, then get confirmation that the function was successful and callback to the javascript. The callbacks are functions called by AJAX after it has carried out its function. The reason we use AJAX in this way throughout our project is that it is an efficient way of handling data, error messages and user interaction between the front end and the database without disrupting the users page.

Firstly we built our form elements depending on what type of data we would eb sending to the database; eg Checkbox for values of boolean type on the back end. Then we started writing the functions that would send the inputted data to the back end. We planned to do this using AJAX, which would let us move around data without having to navigate away from the page, this task was broken down into a few steps.

Firstly, our form would send the data supplied through a Javascript function. This data is then formatted within the function and sent using Ajax into a PHP script. The PHP script will then pass the data to the database where a function there will designate which fields the data is to be stored in. Fairly simple laid out like that, but rather complicated when I came to the coding (althought made a lot easier with some examples supplied by steve!).

With the database and the page talking to eachother we decided to add some validation to the page. Some examples of these being; checking if the e-mail address is valid, making sure dates had the correct number of digits, forcing numbers only in to some fields and last but not least checking wether there is data in the required fields.

Our most complex validation function was the e-mail as we wanted to display some visual indication along the way as to wether the text being inputted was valid. It started off as being able to determin wether there was any text in place but grew to check wether it was formatted properly.

The stages of the form field are (We realise address is spelt wrong):

Valid Email

Obviously we’ll wont use some ghastly colors in the final design, but the framework for changing how the error is displayed is in place.

We have come up with a set of three schemas (folders), containing 9 tables. We have split up some of the tables so parts of the data that doesnt always have to be recalled can be stored elsewhere and will help reduce load times. We have an audit table which will contain an archive of all the booking request history. In this table we will include all the data possible that was previously spread out on the system. In this case, having all the information in one place will eliminate the need to skim over all of the tables to retrieve data when reviewing a archived booking.

We have had a brief plan out of how this will be managed. The back end will be built using postgreSQL and php; enabling us to store and manage user information,bookings, calendars and audit. For the front end we plan on using HTML5, javascript and css to create a simple user friendly interface and experience.

For our schedule we will be spending 3 days per week with SiSo to work on the project as they have the necessary tools to work with databases set up ready for use.

Do this with CCV

Video is a bit laggy.

I had set up Max to track the co-ordinates of a color range in the webcam video, then from here I wrote a short expression that asked if the color range was in a certain area of the video to trigger a bang that would set off the audio trigger. In theory it would work fine, and it did, but instead of sending just one bang for one beat Max would send a continuous string of beats.

Having racked my brain with Liam for a bit, I assumed the problem could be solved using a couple more expressions that would try and detect if a bang had already been sent before another one could. This did work, but metros from elsewhere in the patch interfered causing intermittent bangs.

Finally this afternoon with some much much needed help from Luke and Kavi, I was enlightened with two pieces of code called ‘change’ and ‘gate’. With my expression changed to output a number instead of a bang I could route the number through change. Change basically looks for a change in the value that it recieves through its inlet, and sends a single bang along with it. Perfect for what I needed, but as it would send a bang each time it changed, it would also send one when the color was moved out of the trigger area.

To solve this I used gate. This object can have many outlets and can send data out to different paths depending on what comes in. This is as simple as send a number in, then send a bang to the outlet of the same value as the number in. As the values currently coming from change are 0 and 1, of which you cant have an outlet 0, I inluded a math function which adds 1 to the value before the gate accepts the data. So we have a 1 and 2 value being input. With this it was a simple case of adding a Bang to the relative value and output to create the trigger.

My initial idea is to use a webcam to track the hand movement of the user(s), in the form or gestures, area defined hotspots or x/y
co-ordinates to trigger sounds. The software side of this will be controlled by Max MSP and Ableton Live. I originally chose these two pieces of software because I had previous experience with Ableton and quite a few previous projects on the course have used Max MSP and could see it was capable of what was needed, but since then I have discovered Max For Live which simply integrates some Ableton interface elements in Max for easy programming.

One of my inspirations for this idea came from Reactables. Simply it is a module-based tabletop synthesizer. Each object will either create or effect a synthesized sound based and can be altered depending on its orientation, touch adjustable paramaters and relative position to other objects. I have played around with a mobile app version for the iPhone and it has a lot of technical ability but is quite hard to perform on a small screen. Hopefully I will be able to bring in some similar aspects of this onto a virtual interface.