Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
We are proud to announce that we have teamed up with Chainlink to launch a new bug bounty program to secure the Chainlink protocol. Chainlink is the …
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
Gitcoin is GDPR compliant. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
This gets relevant when the ports (dots next to parameters) are introduced to the nodes (#37). The plan is to draw connections from output ports to input ports on other nodes. For this, the fabrik application uses some jplumb code. A large part of this can be copied, but I do believe it's a somewhat older version. I much prefer staying up-to-date.
* [x] Make connections possible. The connections should look ok-ish, but not necessarily great.
* [x] Make sure that output can only be connected to input, no output-output or input-input
* [ ] Store the connections in a reasonable place
* [ ] Make sure that when a connection is made, the parent (output) does not have the child (input) as own X-generation parent, i.e., no circular graphs allows. I realise that this is what's making this issue difficult, as it requires some (probably recursive) call to all parents. Please discuss issues or implementation strategies.