• Features
  • Community
  • Documentation

  • Maestro Moved to Google Code

    January 2, 2010

    The Maestro project has finally been able to move to Google Code. The SVN repository and wiki have been migrated to Google Code. See the main project page for newly created Google discussion groups for Maestro.

    VR Juggler 3.0.0 Released

    November 27, 2010

    VR Juggler 3.0 represents the culmination of three years of development and testing, and as a result, this is probably the most well tested VR Juggler version yet. A great deal of care was taken to ensure that this would be a solid release because of its significance. Specifically, VR Juggler 3.0 has a totally redesigned cluster infrastructure.

    The new cluster infrastructure is based on a formal client/server model rather than the peer-to-peer approach with an ad hoc server used by VR Juggler 2.x. The new architecture is vastly more scalable and more performant. It should also prove easier to configure in at least two ways. First, the server node distributes configuration information to clients rather than requiring users to maintain per-machine configuration arrangements. Second, it is no longer necessary to identify which cluster node is hosting a device because all devices have to be hosted by the server.

    In general, most applications should migrate from VR Juggler 2.2 to 3.0 fairly easily, but there are bound to be exceptions. All users and application developers are strongly encouraged to read the VR Juggler 3.0 Migration Guide carefully. Note especially that configuration files need to be updated for proper migration.

    The Move to Google Code

    November 2009

    The VR Juggler mailing lists, Subversion repository and wiki have been moved to Google Code. The SourceForge project page is defunct at this point, but it has been retained to preserve the old mailing list archives.