Skip to content

Version 1.4.0

Latest
Latest
Compare
Choose a tag to compare
@benloh benloh released this 16 Apr 21:02
· 82 commits to dev since this release
v1.4.0
5d2359d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Date Released: 4/18/2022

Version 1.4.0 release focuses on improvements in filtering, data import and export.

The Net.Create database/file data format has changed significantly with 1.4.0 so pre-1.4.0 data (*.loki) and template (*.json) files are no longer compatible.

Key Features

See the wiki and pull requests for details:

  • #169 Filters
  • #179 Export Data
  • #217 Import Data
  • #198 Flattened Data Format
  • #194 TOML Template Editor
  • Misc Changes

Filters

A new "Filters" panel allows you to:

  • "Highlight" nodes and edges -- will show nodes and edges that match the criteria and "fade" nodes and edges that do not match the criteria, retaining the original shape of the graph.
  • "Filter" niodes and edges -- will show nodes and edges that match the criteria and "hide" nodes and edges that do not match the criteria, redrawing the graph so that hidden nodes and edges do not change the shape of the graph.

Export Data

Currently visible nodes and edges can be exported to a comma-delimited .csv file. Nodes and edges are exported to separate files.

See Export Data for more information.

Import Data

Nodes and edges can be imported into the currently open graph via comma-delimited .csv files.

See Import Data for more information.

Flattened Data Format

The original Net.Create data format was based on the Google Fusion export format that encapsulated arbitrary fields in an attributes object. When reading and writing data, we converted back and forth between an internal representation which used a flat set of variables (e.g. node.type) to the encapsulated format (e.g. node.attributes.NodeType). This added unnecessary complexity to data handling, especially with regards to exporting, importing data and template streamlining.

With the implementation of exporting, importing, and template improvements, this seemed a natural time to also update the data format. It would simplify the implementation of those features.

Opening a pre-1.4.0 project should automatically convert it to the 1.4.0 format.

See Database Versions for more information.

TOML Template Editor

Prior to Version 1.4.0, project templates were stored as *.json files. While json files are convenient for early prototyping, they are difficult for novices to edit. With 1.4.0, we have converted the template files to a TOML format, which is easier to read and edit, AND, we have added a JSON editor.

Opening a pre-1.4.0 project and project template should automatically convert them to the 1.4.0 format.

See Using Templates for more information.

Misc Changes

See also commits by JDanish dated between Oct and Dec 2020 for miscellaneous changes.

Assets 2