Free Reconfigure by Epredator, Ian Hughes Page A

anywhere, such as her breakfast Marmite, she figured that line of sight was going to be easier to deal with. She could easily cause unintended harm, working at distances not being able to observe the full impact. She didn’t want any of that to worry about. Her preference was to use the game development engine Unity3D. Roisin liked its workflow and approach. Also its model of 3D environments seemed to fit pretty well her RC interactions so far. Translation and Transformations were all the same principles. She hoped that she could use the engine to represent the objects in space and also make streaming connection requests to RC from it. Another bolt of inspiration almost set light to her hair with the buzz of electric excitement it caused. If she could do that she could also make it a full blended reality application. Mixing a camera feed of the visible world and the deeper instrumentation of everything on the planet? Step aside gaming headsets she thought. Your demos may have seemed like the killer app for blended reality, or mixed reality, or augmented reality, or whatever the flavour of the day was, but this?
    “Now this Death Star is the ultimate power in the Universe! Aaaaand breathe!” She said. Roisin had got a little carried away with herself, again! She had not written any code. Fancy extra requirements were not getting her anywhere near to solving the basic problem. That’s decided! Unity3D it is, she mentally confirmed. She sparked up the environment with a click on the cartoon cube logo. Did she want to start a new project or load an existing one? New project of course. She typed ‘Full Metal Marmite’. Project names were never a problem for Roisin. She simply picked some recent events and mixed them with some other media like a film or a book. She thought of a bootcamp and how, now, she was going to make the transition into the field. She considered starting a hashtag on Twitter #filmswithyeast, she could then choose another project name from the comedy gold that would come in. This project was on the down-low so FMM it was.
    Twitter didn’t have a mainstream C# client example. Java, C++, Javascript for Node.JS, Go and more all were supported. She had actually found a proper, apparently complete, implementation of C# for Twitter for a previous project. Her project hadn’t gone anywhere but she had started to look at it. She found the module she had written when exploring the C# version. It was great to have already written the OAuth authentication connection, the read a timeline and then disconnect, pieces of code. Those had been for a traditional RESTful connection but it was very easy to swap out for the User Stream constant connection. In the code she kept the connection alive and didn’t destroy the class instance variables straight away. Rather than the ‘Update()’ being used to look for changes, the underlying connection was keeping a constant flow of information to and fro with the Twitter DM. She had to code the responses to the events that occurred with the correct message handling routines. The messages that indicated data responses were the most important. The connect, disconnect, error, stall etc. were less important to her right at this moment. A JSON message, encoded and delivered to a string array was what she was after. She started just dumping that to the console log. She made a mental note to think about the parsing structure, and how to relate that to a 3D world, next. The whole design ethic was ‘NO CLI!’ For now text was going to have to be the vehicle to test with. There was something different about a nice shiny user interface entry field with delicate round corners and drop shadow, to the blinking terminal cursor of an emulator. She knew she was kidding herself, but it felt like progress. She wrote a function to accept a string, and send the message to the Twitter stream, that she would be connected to when all this wiring and configuration was complete.
    After about