|
@@ -4,14 +4,7 @@ General purpose graph package for Go
|
|
|
|
|
|
|
|
## Initial Idea
|
|
## Initial Idea
|
|
|
|
|
|
|
|
-`todo`
|
|
|
|
|
-
|
|
|
|
|
-> Explain the initial Idea came from machine learning Tensorflow etc...
|
|
|
|
|
-
|
|
|
|
|
-> And by watching drone CI stages, I saw I could implement timing and triggers
|
|
|
|
|
-> on nodes creating the possibility to add Go functions that handle
|
|
|
|
|
-> docker containers to execute our steps and triggers would execute nodes that
|
|
|
|
|
-> handle notifications (as plugin/slack, plugin/email)
|
|
|
|
|
|
|
+`possibilities`
|
|
|
|
|
|
|
|
* Machine learning
|
|
* Machine learning
|
|
|
* Graphical CI pipeline
|
|
* Graphical CI pipeline
|
|
@@ -136,6 +129,7 @@ registry.Describer(
|
|
|
|
|
|
|
|
* FlowPkg: Create training mechanism
|
|
* FlowPkg: Create training mechanism
|
|
|
* FlowPkg: Machine learning examples
|
|
* FlowPkg: Machine learning examples
|
|
|
|
|
+* FlowPkg: Generate go code to maximize call performance
|
|
|
|
|
|
|
|
### Backend
|
|
### Backend
|
|
|
|
|
|
|
@@ -157,3 +151,7 @@ in Server side we can do an analysis on each type to see if it can be
|
|
|
implemented by another type and send this as part of the registry with all
|
|
implemented by another type and send this as part of the registry with all
|
|
|
descriptions, this way we can highlight sockets that can implement the dragging
|
|
descriptions, this way we can highlight sockets that can implement the dragging
|
|
|
type
|
|
type
|
|
|
|
|
+
|
|
|
|
|
+### Generating code
|
|
|
|
|
+
|
|
|
|
|
+generate code based on a flow should be simple as we have the function signatures
|
luis