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
NodeEditor is one of the few open source flow graph QT libraries. I can understand the intent of QT's MVD pattern from simplegraph example.But the NodeDelegateModel concept confused me. I think it is not a "Delegate" or "Model" in "MVD". It is more like Data containing In/Out member and a compute function because nodedelegatemodel is stored directly in DataflowGraphModel. Maybe existing pattern and "NodeDelegateModel" obj can be given other names.
I've been thinking about it lately. If the nodeeditor is strictly designed as MVD in the future, how should it be desigened? A generic flow graph pattern is more valuable than more and more functional details.
The text was updated successfully, but these errors were encountered:
NodeEditor is one of the few open source flow graph QT libraries. I can understand the intent of QT's MVD pattern from simplegraph example.But the NodeDelegateModel concept confused me. I think it is not a "Delegate" or "Model" in "MVD". It is more like Data containing In/Out member and a compute function because nodedelegatemodel is stored directly in DataflowGraphModel. Maybe existing pattern and "NodeDelegateModel" obj can be given other names.
I've been thinking about it lately. If the nodeeditor is strictly designed as MVD in the future, how should it be desigened? A generic flow graph pattern is more valuable than more and more functional details.
The text was updated successfully, but these errors were encountered: