My name is Vojtech Bardiovsky and I am working on the new Visualization API. This is done together with the new visualization engine based on shaders.

API design

The aim of the project was to design a clean and usable API for the new engine. It exposes only as much as necessary, but enough to make customization of visualization possible. The following four API classes are all services and can be retrieved through ‘Lookup’.

Visualization controller

This is the most important class in the API and can be used to retrieve the ‘Camera’, ‘Canvas’ used for visualization display, and very importantly the instance of active ‘VizModel’ and ‘VizConfig’ classes that both contain many settings that help controlling the visualization. It will also allow making direct changes to visualization like setting the frame rate or centering camera according to different parameters. The ‘Camera’ class can be used to get data about its position or to make actions such as translation or zooming.

Event and Selection managers

The Event manager can be used to register listeners to user events exactly as in the old engine. This is very important for the tools. The selection manager provides methods to retrieve all currently selected nodes or edges, to select nodes or edges and to control the selection state of the UI (dragging, rectangle selection, etc).

Motion manager

Apart from listening to all user induced events and their most basic handling (selection, translation, zoom), this class provides information about current mouse position in both screen and world coordinates.

New features

There are many changes the new engine will bring and although it is not finished yet, there already are some new user-side features.

Complex selection

In the old visualization engine, only rectangular and direct (one node) selection were possible. New API will allow to implement any reasonable shape. At the moment it supports rectangles, ellipses and polygons.

Thanks to the selection shape variability and changes in the mouse event system, it is possible to make incremental/decremental selections using Shift and Ctrl keys. Opposed to only one node at the time, the whole selection can be dragged and moved now.

Background image

It is now possible to change and configure the background image. Settings are similar to the CSS properties such as ‘background position’ or ‘background repeat’.

Node shapes

It is possible to have different shapes for every node in graph. Basic shapes include ‘circle’, ‘triangle’, ’square’, etc., but also up to 8 custom images that can be imported by user. Nodes can have their shapes defined in the import file or set them directly through the context menu.

Better 3D

Work has been done on a better way to control the scene in the 3D. Graphs are not naturally suited for 3D, for example adding new nodes or moving them will never be perfectly intuitive. But for displaying the graph, some enhancements can be done.

Current status

The engine is still under development, but the API is slowly closing to its final state. Next step for the API will be to include as many configuration possibilities as the engine will allow. The underlying data structures will be optimized for performance.
As the project consists of two parts, API and engine, Antonio Patriarca, the mentor for this GSoC project and implementor of the engine will write an article about rendering details in the near future.

(The rendering pipeline for edges is not fully finished, so the images shown are not the actual new look of gephi.)

Post to Twitter Post to Plurk Post to Yahoo Buzz Post to Delicious Post to Digg Post to Facebook Post to Ping.fm Post to Reddit Post to StumbleUpon

Related Posts:


Design Functionality ~

Trackback

11 comments feed

  1. 1
    Jedix

    This’s great, i’m looking forward to testing!

  2. 2
    Andrew

    Thanks for the great work- I’m looking forward to shaped nodes! It would be nice to have more than 8 image options so I could use flags. ( http://www.famfamfam.com/lab/icons/flags/ )

  3. 3
    Sebastien Heymann

    I guess the nodes could use any images possible if the image location is set at import?

  4. 4
    Antonio Patriarca

    The image shapes aren’t currently implemented, so we can still change it. The limit of eight images was chosen to have a simpler interface, but we can support more images, probably also an “unlimited” number of them. How do you want to set the shape of a node? How do you want to load them?

  5. 5
    Sebastien Heymann

    In a case of a social network, I’d like to see the faces of everyone instead of a geometrical shape.

    The GEXF file format (http://gexf.net/1.2draft/gexf-12draft-primer.pdf) allows to define an “image” as a shape type for each node, and specify an URI location to load the images.

  6. 6
    dominic

    In case of social networks, and especially in case of bibartite networks showing users AND user’s pictures/activities in one whole system, it would be great to have implemented this function Sébastien (and Antonio) described. I’m looking forward to it, because I already specified an URI location in my GEXF-files, but—of course—loading the images doesn’t work yet (and so I have not been able to test this nice feature). anyway: thanks, you guys, go for it!

  7. 7
    Antonio Patriarca

    We will then change the API to support this feature. :)

  8. 8
    will

    Is there any update on this API? Is it available in 0.8?

  9. 9
    Erwan Demairy

    Do you have any plan to merge this new visualization API with the trunk?

  10. 10
    Emma Johansson

    These functions are exactly what I’m looking for. I have installed the plugin Visualization API but it is light grey in the list and says “It is in read-only mode and cannot be checked”, is it still installed?
    I cannot chose background picture or have images as nodes so I suppose I need to do something more.
    How do I activate this plugin?

  11. 11
    Miro Marchi

    How’s your job going on? We are all looking forward to it! :-)

Add comment