Opening a multiple select field as its own isolated “block” on the canvas

Complete index:

A list of all workspaces, classes, and freestanding objects. Classes would be accordions (possibly using <summary>/<details>), so upon clicking on them you would be able to see their constituent objects.

I’m imagining this to be accessible from the home tab once a project is open, and possibly also as some kind of drawer nav in all workspaces.

Single table workspaces/windows

I’m thinking of my fondness of the Stickies app on MacOS (where I’m currently drafting this), and the way it isolates notes in different window contexts. I think it would be nice if Goby had a similar functionality, possibly with a responsive column width (while still keeping the widths in grid square units). I’m also realizing that developers have access to the “float on top” window type on MacOS, so I could add that as an option.

Visual joins:

In the same way that you can join tables in SQLite on a shared column, I think it would be cool if you could visually link up two or more classes using their relation properties, possibly separating multiple choice selections into multiple rows and only showing repeated information once. I could imagine how the header for a table could be augmented to represent that:

● Typefaces + ● Foundries on ⬩Foundry/⬩Created

Matrix view:

Ability to create a matrix table representation of two classes intersected in their relations with a third, e.g. in a table displaying political candidate positions by issue, made using the intersection of a candidates table and issues table on a position table

Data conflict resolution panel:

When you change an object’s class or change the properties in a class, such that columns of data are left stranded or new values have to be filled in, Goby should prompt you about what to do with this data. It should let you:

• cancel the change you were about to make
• direct Goby to discard the old data
• potentially offer some other way of preserving the old data

Space view - toggle between static and animated:

My original plan for the space view was to have the nodes initially positioned with a force graph, and then become static and draggable without influencing the position of the other nodes (Kinopio style).

However, it’s very entertaining to drag stuff around in the force diagram. so I think I may keep it and make it a switch back and forth thing.

Show/hide property columns:

The use case I'm thinking of is using an expression to evaluate a column from its neighbors, and not want/needing to see the input columns.

Cell wrapping:

This is a minor thing but came up in a conversation with someone about the table view. The idea is you'll be able to toggle wrapping on each property among other styling, so text and taglists will either run in one line/hide beyond the column edge, or break to a new line at the column edge.