-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically generate default scripts (templates) from connected inputs #83
Comments
How about something similar to the Java and R Snippet nodes, where you have a sidebar with all available columns and flow variables, and the necessary variables/parameters are added to the script automatically upon double-clicking any of them? |
@imagejan That's how it is implemented at the moment which works really nice. It was just a thought experiment to maybe add the already connected inputs and outputs to the default templates when opening the node's configuration dialog. |
@stelfrich oh, I see, sorry. Then I'll shut up ;) |
I agree that the templates need improvement. I don't think it would be feasible though to add all inputs and outputs, this. |
I agree. I think we could do some auto-guessing, like adding the first image column or so, but I'd not try to be too smart here. Rather I'd provide nice examples on the website (or a video) explaining the concept. Adding inputs as default only helps new users. |
I vote +1 for adding the first image column as parameter, @dietzc.
Exactly, that's why I think it is a good idea to add a parameter (in a future release) as an example. It might lower the frustration for new users on their first try, maybe making them stick with scripting. |
This might be hard to achieve / to find a sensible default case: for a beginner it would be useful to have a template with input
@Paramter
s according to the inputs connected to the node.For tables with a few columns it might be sensible to add those as inputs and have the user remove them instead of having him/her add them one after the other.
The text was updated successfully, but these errors were encountered: