The last week or so has been spent focusing on putting together the programming for pulling and displaying our content as well as the logistics of getting permission for use of said content as well as the use of the location and screens. Last week we visited electronics stores and spoke to the managers and passed on a hard copy of our project proposal. At James advice, we have been attempting to follow these up with phone calls, emails and visits in person and finally this morning we have gotten the go ahead from the area manager.
We have also been soldiering on with out programming so once our content is ready, it will be easy to adapt it to the premises and their setup. It has been interesting to see our concept develop seemingly naturally as we have begun programming. After our experiences learning Java (i.e. which we all found extremely challenging), it was to be feared as possibly the most complicated part. I have however found that I have gotten to the point in my understanding where I can pull at my knowledge from both programming papers (Processing and Java) and combined with common sense and helpful resources (and the indispensable aid of Kim) has been sufficient to work out and achieve the outcomes we set out to create.
My absolute moment of joy came at about 11pm on Monday night where, after about a week of searching, experimenting, trial and error, I finally managed to work the Flickr API to display and image on the screen. This was configured to search by tag and creative commons so it will relate to the content pulled from news headline feeds and Twitter, while ensure also that we do not breach copyright restrictions.( Images are licensed under 'BY' which require attribution only so from here it is a matter of displating also the username of the creator of the image.) It was the point where I realised that I have begun to enjoy programming the same way I enjoyed maths in that is it something really quite challenging and requires careful and precise calculations, but when that successful outcome is achieved, it is absolutely rewarding.
We have at this point about four seperate programs to perform all the functions which generate the various aspects of our content, including:
- Generating and placing in pre-recorded content,
- Reading, displaying and saving footage from a live webcam feed
- Pulling a keyword from the news headline to feed into the twitter feed and Flickr search.
Now, this is where we are starting to have problems with integrating the different parts of the code so they don't interfere with each other. My concern also is with the demands of the program on the computer once all the elements are integrated as already with two videos, the live webcam feed and the rss feeds has caused it to crash.
As it is visually coming together, it is exciting to see how the elements are begin visually integrated and imagining how it will look and the effect it will have when in context. As outlined above, we are beginning to have an idea of the meaning it will convey. At this point, our intended effect on the viewer is to make them stop and engage with the screens and the content. It could be interesting also to observe how viewers interact with the screens when the usual content is on and compare the effect as ultimately, with this project we are trying to create a conversation between the space, the screen, the content, the passive contributor and the viewer.
We have also been soldiering on with out programming so once our content is ready, it will be easy to adapt it to the premises and their setup. It has been interesting to see our concept develop seemingly naturally as we have begun programming. After our experiences learning Java (i.e. which we all found extremely challenging), it was to be feared as possibly the most complicated part. I have however found that I have gotten to the point in my understanding where I can pull at my knowledge from both programming papers (Processing and Java) and combined with common sense and helpful resources (and the indispensable aid of Kim) has been sufficient to work out and achieve the outcomes we set out to create.
My absolute moment of joy came at about 11pm on Monday night where, after about a week of searching, experimenting, trial and error, I finally managed to work the Flickr API to display and image on the screen. This was configured to search by tag and creative commons so it will relate to the content pulled from news headline feeds and Twitter, while ensure also that we do not breach copyright restrictions.( Images are licensed under 'BY' which require attribution only so from here it is a matter of displating also the username of the creator of the image.) It was the point where I realised that I have begun to enjoy programming the same way I enjoyed maths in that is it something really quite challenging and requires careful and precise calculations, but when that successful outcome is achieved, it is absolutely rewarding.
We have at this point about four seperate programs to perform all the functions which generate the various aspects of our content, including:
- Generating and placing in pre-recorded content,
- Reading, displaying and saving footage from a live webcam feed
- Pulling a keyword from the news headline to feed into the twitter feed and Flickr search.
Now, this is where we are starting to have problems with integrating the different parts of the code so they don't interfere with each other. My concern also is with the demands of the program on the computer once all the elements are integrated as already with two videos, the live webcam feed and the rss feeds has caused it to crash.
As it is visually coming together, it is exciting to see how the elements are begin visually integrated and imagining how it will look and the effect it will have when in context. As outlined above, we are beginning to have an idea of the meaning it will convey. At this point, our intended effect on the viewer is to make them stop and engage with the screens and the content. It could be interesting also to observe how viewers interact with the screens when the usual content is on and compare the effect as ultimately, with this project we are trying to create a conversation between the space, the screen, the content, the passive contributor and the viewer.
No comments:
Post a Comment