molikto 2021-06-09 05:49:03 a small (silent) demo of my project. it aims to be a productive editor for any typed property graphs, it do this by expanding the graph as a spanning tree, so it appears like an outliner. I am currently using it to keep my notes and references, but the idea is it should be extended to cover other needs. The key is it aims to be an editor of the ultimate data structure: property graph. https://drive.google.com/file/d/18Hdl19iCVbNmrrfVr6zNXECvM6VPrBPW/view
Chris Knott 2021-06-09 09:59:01 This looks great, I agree with lots of what you have written. Just FYI I had assumed there would be sound, and it's quite hard to read on mobile.
This fundamental idea of seeing a spanning tree as a View of graph is very good. This looks like a way to unify tags and folders (taxonomy Vs folksonomy)
How do you specify new Types?
molikto 2021-06-09 10:11:56 Chris Knott the schema of the graph is also a graph, and edited with the same editor (a small caveat is primitive types is handled specially)
molikto 2021-06-09 10:13:13 although the spanning tree for dense graph is not really useful. I can imagine the graph editor has different modes (spanning tree mode or full graph mode)
Konrad Hinsen 2021-06-11 07:51:55 This looks definitely interesting!
What exactly are the types in your graph? Just arbitrarily defined tags, or do they have implications for the structure of the graph?
A practical issue I see with any form of types for data structures meant to be very general is the need for some form of type refactoring. You will certainly end up with near-synonym types (you have "video" and "movie" for example), or data that would fit several types (an e-book presented together with an introductory video on a Web page is... which of the three?), so at some point you may want to redesign and unify your types as the graph grows. I haven't yet seen any system that does this well.
molikto 2021-06-11 07:55:25 the types are not hardcoded in the app, but user-defined by a schema, the schema is a property graph. node schema defines what property it have, edge schema defines what kind of node it connects.
molikto 2021-06-11 07:57:12 yes designing proper types are hard, it is like you need to migrate your database... proper tools can be provided to have an easy migration, but the designing and migrating might not be avoidable...
Konrad Hinsen 2021-06-11 14:41:21 Migrating is fine if its well supported by tools. But I guess the first question is how to define a migration properly.
Kartik Agaram 2021-06-10 05:42:07 I recently added the ability to edit functions in my prototyping environment. It's inspired by Tiddlywiki, with the screen at any moment containing the most recently edited functions. Here's a short live-coding session of everyone's favorite programming problem -- with a small twist.
https://archive.org/details/akkartik-mu-2021-06-09 (video; 6 minutes)
Main project page: https://github.com/akkartik/mu
Ray Imber 2021-06-10 16:54:45 Kartik, you continue to outdo yourself! Your system is becoming exponentially more featureful and useful every time you post a demo.
