https://github.com/devhelpr/code-flow-canvas

Visual programming system
https://github.com/devhelpr/code-flow-canvas

Last synced: 2 months ago
JSON representation

Visual programming system

• Host: GitHub
• URL: https://github.com/devhelpr/code-flow-canvas
• Owner: devhelpr
• License: other
• Created: 2023-01-21T07:38:04.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2024-09-14T13:12:54.000Z (4 months ago)
• Last Synced: 2024-09-15T09:25:27.663Z (4 months ago)
• Language: TypeScript
• Size: 208 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README-combined-components.md
  • License: license.md

Awesome Lists containing this project

README

        
# "combined components"

(other terms : "composite components", "container components", "compound components" , "composable components")

for example a connection-node with multiple control-points

the control-points are components as well

when the position of a control-point changes, the connection-node should be updated

however... when the connection-node is moved .. the control-points should be moved as well

how to link these?

a node has a position and a list of elements

should it have a separate list of components?

difference between elements and components :

    - element are part of the rendering tree of a node

    - components have their own rendering tree

    - in a DOM context, elements are DOM-elements like a div, a span, a svg, a canvas, a text node etc...

in the case of "control-points" ... the components should be moveable.. but this is not always required

.. in the case of input-output points .. the components should not be moveable but have different properties

    .. they can have constraints depending on the parent node-task-type in a vps environment

.. sometimes the sub-components should be moveable but only within the constraints of the parent

the parent components can have connections with other components without them being child/sub components 

    ... if you move a parent component, the connections should be updated

    ... using "downstream or upstream"-dragging.. whole sets of components can be moved

## implementation

should IElementNode have a list of component-id's or references?

should IElementNode have an x , y and z position? or even a timestamp?

... an IElemntNode is not always placed on a canvas but can be used differently as well.

... implementations can differ depending on whether it is used in a 2d or 3d context...