Showing posts from January, 2012

Ray Platform: a message-passing-interface programming framework

The first pieces of Ray were put together in a git repository on 21 January 2010. Since that, Ray has undergo numerous major refactoring events. The biggest changes to date are those of a few days ago. The source code of Ray is now divided in Ray Platform (around 13000 source lines of code including comments and blank lines) and Ray Application (around 29 000 source lines of code including comments and blank lines). Ray Platform compiles independently of Ray Application -- it can be reused over and over again. I changed the license too. While Ray Application is still licensed under the GNU General Public License, version 3, Ray Platform is licensed under the GNU Lesser General Public License, version 3. This means that Ray Platform can be incorporated in proprietary software (for free, if that matters). If changes are made to Ray Platform, however, these have to be shared. How it works ? The main class of the Ray Platform is ComputeCore. It represents a process mapped to a si

Making a github project readable as a web page

It is no secret, I love github (and git). Today I updated my knowledge on javascript. I started to wrote a game, the slim volleyball game to be exact (see reddit ). So I pushed the thing on github . However, the files were not served as being part of a web page. Fortunately, github implements a service called github pages which allows any github user to share a web page about something using the user's username. This service also allows one to add a branch called 'gh-pages' (refs/heads/gh-pages to be exact I believe) to git repository to serve its content on the web. The content of the branch 'gh-pages' for projectX of userA is served as a web page at Initially, the only reference is usually 'master' (along with its remote twin). seb@godzilla$ git branch -a * master remotes/origin/master To serve all the content of the branch 'refs/heads/master' on github pages, a symbolic reference called 'r