A couple of days ago, my developer version of the Oculus Rift Virtual Reality (VR) headset arrived. It came in a very slick plastic case and hooked up to my computer in minutes. I installed the software and ran the demonstration "world" and stuck my head into the Oculus Rift - Amazing!
I have released the beta 1 version of my RDF PipeLogger on GitHub https://github.com/ebremer/PipeLogger under the BSD 3-Clause License. The program is still being tested but appears to be stable enough for a beta release. The project was developed in NetBean 7.3 using JDK 1.7.0_17.
My test server currently uses the following LogFormat config with potential simplifications indicated with individual line comments:
Each time I get a complaint that one of my web servers is running slow, the first thing I do is look at the Apache httpd logs. For anyone familiar with Apache HTTP Server logs, they are not particularly useful when trying to analyze huge amounts logging information. Trying to figure out what client(s) may or may not be misbehaving usually requires some log analysis tool whether commercial or open-source. As it is, the http server logs alone do not tell a complete story of what is going on.
Nexus has been upgraded from Jetty 7 to the latest Jetty 8 which supports the RFC 6455 version of the WebSocket protocol. This allows the use of the latest FireFox 13 and Google Chrome browsers and, of course, all of the improvements to both browsers, especially the HTML5 and WebGL support. I've been holding back on updating because of the number of revisions the WebSocket protocol has been going through. I wanted to spend my time on core Nexus development rather than just bumping the WebSocket revis
Alright, it doesn't look like much, but there is something special about the web dialog that is being displayed over the 3D graph - it was built triple by triple. I had reached the point in developing Nexus where I needed to have interactive dialogs for display control and user-input. Up until this point, I had been working with 3D objects and taki
From the beginning, I wanted Nexus to be a collaborative visualization system allowing multiple clients in multiple locations to see the same visualizations in real-time. The issue that arises here is knowing "where" in the 3D semantic web visualization the other clients (people/avatars) are and what direction they are looking at. In the 3D digital world, you have the concept of a "camera". This is essentially your point-of-view in a particular 3D simulation. As the camera moves, your view of the model changes as well. In order to know where the other clients are in the simulation
It took less time than I thought it would, but here is an updated version of the 3D FOAF graph from my last posting with node sizes determined by the log base 10 of the number of links into a particular node. The coulombs law for the larger nodes is adjusted so that larger nodes "push" out harder to accomodate the larg