FAQ

What is Ubigraph?

Ubigraph is a 3D graph visualisation environment that splits the work between a viewer and a client program. The viewer renders nodes and edges. The client tells the viewer what to draw, using a remote call protocol. The two run as separate processes. There is a longer write-up on the Ubigraph pillar, and a compact one on the overview page.

Where should I start on this site?

If you want the conceptual picture, the Ubigraph pillar is the right entry point. If you want to look at the demos, start at the demo index. If you want to understand the client side, start at the docs index. If you want to set expectations before chasing original binaries, read the downloads page.

Are the demos still useful if I cannot run the original viewer?

Yes. Each demo is built around one idea about how a graph viewer should behave under specific conditions. The write-ups on this site explain the idea and what to look for, and that explanation is the part that survives regardless of which viewer you are running. The demos section and the demo index cover the set.

What about the documentation - does it still apply?

The general shape of the call surface still applies. The protocol is XML-RPC style, the call set is small, and the patterns translate cleanly to current language tooling. The harder part is environment, not the API. The docs index is the best starting point.

Can I download original Ubigraph binaries here?

No. This site does not host binaries from the original distribution. The downloads page is direct about that. If you obtain Ubigraph-era material from a third party, the downloads page covers safer ways to think about setup and what to verify before running anything.

What about the PDFs - are those originals?

Where a paper PDF has been verified, it is served at its original path. Where a paper PDF has not been verified, the path is held by a careful placeholder PDF that explains what it is. The papers section covers each one through its companion HTML note.

I came in from an old index.html or .php link. Did the site move?

No. The historical paths still resolve. /ubigraph/index.html, /ubigraph/content/Demos/index.html, /ubigraph/content/Demos/RandomGraph.html, /ubigraph/content/Demos/random_binary_tree.html, /ubigraph/content/Demos/Animation.html, /ubigraph/content/Docs/index.html, and /ubigraph/content/Downloads/index.php all return real pages. Bookmarks should keep working.

How do I drive a Ubigraph-style viewer from modern Python?

Use the standard library XML-RPC client. The docs index covers the basic shape, including the small set of calls you will use most often. The harder questions tend to be about old example code that was written against Python 2, and the docs and XML-RPC graph control lab note walk through that transition.

What are reasonable substitutes today?

For most use cases, a modern graph drawing library or a browser-based renderer is simpler than chasing the original viewer. The graph visualisation alternatives lab note covers the categories worth knowing about and where each one is a sensible fit. There is no single best replacement. There are several different trade-offs.

Why are the demo pages written without screenshots?

Each demo is about behaviour over time. A still image of any one moment hides the point of the demo. The pages are written so the behaviour is described clearly enough that you do not need a screenshot to understand what the demo is teaching.

Can I cite a page from this site in a paper or a write-up?

You can link to any page here. Treat the prose on each page as a working note rather than a final reference, and verify any factual claim about original Ubigraph material against the historical sources that exist elsewhere.

What about the /blog/ URL I have seen referenced before?

/blog/ is preserved as a compact index that points at current lab notes. It is not a general programming blog. Notes here are about graph visualisation, Ubigraph workflows, related papers, and modern substitutes.

Why does this site keep talking about modern alternatives?

Because being honest about substitutes is more useful than pretending the old toolchain is the only good answer. The site exists to keep useful pages alive. Useful in 2026 means including the path that takes you forward, not only the path that takes you back. The Ubigraph pillar covers the trade-offs.

Is there a forum, an issue tracker, or a community channel?

No. This site does not run a live community space. The support page and the contact page are the right places to set expectations.

How do I get hold of the maintainer for a substantive question?

See the contact page. Responses are not on a fixed schedule.

Is the site safe to share with students?

Yes. The content is written to be useful for self-study. There are no third-party scripts beyond local search, no aggressive tracking, and no advertising. The privacy page sets out what the site does and does not collect.

Is anything dated wrong on this site?

Sometimes. Where date confidence is weak, the site uses undated maintenance notes rather than inventing a calendar. If you notice an actual error, the contact page is the right route.

Where can I read about the paper shelf?

The papers section and the three companion notes - Blitz arrays, C++ templates as a Turing-complete language, and the Veldhuizen thesis - cover the shelf.

Anything else I should know?

The changelog tracks visible changes. The license, privacy, and terms pages cover the small print. Nothing on the site is intended to be presented in a misleading way, and where this page is uncertain it tries to say so.