You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An enterprise application that uses logic graphs for decision support and business intelligence.
Describe the problem or limitation you are having in your project
Once a graph is constructed in GraphEdit, the contents need to be POSTed to our intelligence engine for analysis. It appears none of the Graph* nodes are JSON serializable so we are having to write our own serialization every time.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
JSON serialization is a key feature in modern applications and interoperability. WIth this feature could easily tie our logic graphs (and other visual-coding derived knowledge) to our cloud applications for bi-directional communication.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
A new method such as .to_json() for classes child to GraphElement
Consider a custom class with three fields, Name, Age, Zip Code and instance x.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Perhaps, but not a few. Many languages support serialization routines for all objects. It's like this could be written into the "Control" node or such like.
Is there a reason why this should be core and not an add-on in the asset library?
Requires changes in the GraphNode source.
The text was updated successfully, but these errors were encountered:
Describe the project you are working on
An enterprise application that uses logic graphs for decision support and business intelligence.
Describe the problem or limitation you are having in your project
Once a graph is constructed in GraphEdit, the contents need to be POSTed to our intelligence engine for analysis. It appears none of the Graph* nodes are JSON serializable so we are having to write our own serialization every time.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
JSON serialization is a key feature in modern applications and interoperability. WIth this feature could easily tie our logic graphs (and other visual-coding derived knowledge) to our cloud applications for bi-directional communication.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
A new method such as
.to_json()
for classes child to GraphElementConsider a custom class with three fields, Name, Age, Zip Code and instance x.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Perhaps, but not a few. Many languages support serialization routines for all objects. It's like this could be written into the "Control" node or such like.
Is there a reason why this should be core and not an add-on in the asset library?
Requires changes in the GraphNode source.
The text was updated successfully, but these errors were encountered: