Downloads

What you will find here

This is the modern downloads landing page. The original page lives at its historical path, /ubigraph/content/Downloads/index.php, and is preserved so that older bookmarks still resolve.

The honest position on downloads is that the original Ubigraph distribution material is not always easy to confirm at source. This site does not present unverified binaries or source archives as if they were official originals. Where reference PDFs can be served at their historical paths, they are served there. Where they cannot be verified, the path is held open by a careful placeholder, with a companion HTML note that explains what the page is.

That position is unglamorous on purpose. The cost of misrepresenting a download is higher than the cost of being plain about what is here.

What is available on this site today

• The three reference PDFs from the historical papers section: BlitzArrays.pdf, CppTuring.pdf, VeldhuizenThesis.pdf, each with a companion note on the papers page.
• The exact historical page paths under /ubigraph/, including the demo pages, the docs index, and this downloads page.
• The full docs section covering the XML-RPC style call surface and what to expect when running old example code with current tooling.

No binaries are served from this site. If a future verified binary release becomes available and can be hosted appropriately, the changelog will say so.

How to think about setup on a modern system

If you are sitting down today with the intent of running an older graph viewer alongside a current operating system, a small amount of planning saves a lot of frustration.

A few honest expectations:

• The viewer side will be the harder side. Binaries from that era often depend on specific runtime libraries, and reconstructing the right environment can be more involved than the client code that talks to them.
• The client side translates more cleanly. XML-RPC style calls in Python translate to the standard library with modest effort.
• Display behaviour can be surprising. Older 3D applications sometimes rely on graphics features that have moved or been retired.
• Networking is mostly straightforward. XML-RPC over local loopback is forgiving and well-supported.

The realistic plan is: get a client connected to something - even a stub server that records calls - then worry about the real viewer afterwards.

Safer ways to try the idea

If your goal is to learn the workflow rather than to revive a specific binary, three softer paths are worth considering:

1. Use the documentation as a specification. Build a tiny stub server in any language that records the calls you send. The shape of the protocol is enough to teach you the client-side patterns.
2. Use a modern graph drawing library. Many of the workflow ideas - long-running viewer, streaming updates, attribute changes - can be approximated in current libraries.
3. Read the demo write-ups carefully. The demos section and the demo index explain what each example is supposed to do. You do not need the original viewer to learn from the examples.

That third path is often the most productive. The demos teach concepts. The concepts outlast the binaries.

Verifying anything you do download

If you obtain Ubigraph-era material from a third party, treat it with normal caution:

• Check the file size and type against any description you have.
• Run the file through a malware scanner before opening it.
• Do not give the executable any unnecessary privileges on first run.
• Do not assume an archive is the official original unless you can confirm the source.
• Keep the file isolated until you are confident it behaves.

There is nothing unique to Ubigraph here. These are standard precautions for any old binary from an uncertain source.

What to do if your environment will not co-operate

A few things to try before giving up:

• Run the viewer in a virtual machine with a known-good older operating system image. This isolates dependency problems from your current setup.
• Run the viewer in a container if it is available in a portable form. The same isolation, less overhead.
• Replace the viewer entirely with a modern alternative for the parts of the workflow that are most valuable to you. The graph visualisation alternatives lab note covers what to look at.

These are not workarounds in the embarrassed sense. They are common engineering responses to older software meeting newer environments.

Where the original docs live on this site

The most useful starting points if you want to keep digging:

• The original docs index.
• The original demos index.
• The original downloads page.
• The Ubigraph pillar for the wider picture.

If you came here expecting a one-click install button, this is not that kind of page. The point is to leave you better informed than you arrived, not better marketed to.

A note for people maintaining old workflows

If you are responsible for a workflow that still depends on Ubigraph-era tooling, the FAQ and the support page cover the questions that come up most often. Neither pretends to be a hotline. They are notes written for people who already know what they are dealing with and want a small, calm place to think.