I’ve been using KNIME for a few weeks, and enjoying that it is a local app, has so much thought invested and works for a good number of my use cases. Two requests:
1_ The graphical node UI is a great step towards easier usability.It breaks down one level beneath when the user double clicks or needs to change the behavior or do setup. The dialogues that are beneath the visual node interface contain most of the complexity and functionality. They need renaming, floating help, better layout and inline documentation. Additionally, it would be amazing if one could edit a node’s code without needing to descend into the /src/plugins directory. Big asks all, I am aware! Thank you for creating and maintaining this fantastic resource.
thanks for the lovely feedback. It is always nice to hear that one’s work is well appreciated.
In fact, we are putting a lot of effort into migrating node dialogs to the new user interface. With the release planned for July, there will be a bunch more. Additionally, the integration of node dialogs is going to improve. Did you spot the little help icons that appears above each input field when you are hovering?
May I ask why you need to change the code of nodes? What is your use case for that? From what I know people usually to not change the behavior of existing nodes, but build their own extension, e.g., using Python.
>Did you spot the little help icons that appears above each input field when you are hovering?
You are all working so hard on the app, thank you. The help interface is going even deeper into the settings dialog, great news Yes the little help hovers make finding information super fast and contextual. The settings and inputs dialogues of the app can be complex and rather daunting.
May I ask why you need to change the code of nodes?
One example is the OpenAI Authenticator Node, or nodes associated with GPT4ALL. I have found the need to make changes to them, to work with our internal (non-SSL) servers, or to tweak them slightly to handle the fast moving world of local LLM’s to keep them working. In another case, the name of certain models is hard coded into the node plugin and I was able to resolve the issue by modifying the source. The process to modify in this way would be much easier if the development were exposed in some way. For instance, right clicking on the node and having a “Edit Script” option to edit the code in situ. Since these nodes are rather complicated, it’s easier to duplicate and modify than write a new one from scratch.