Copy link to clipboard
Copied
Working in Automation Blocks has been a blast. It's the first time I've actually been able to script anything of value. The tutorial videos are an absolute godsend to getting into it. I do have a couple of notes/requests for versions down the line. They range from the mundane to big requests, so take this as just a rambling.
I'm sure that more will come up, but this is what's come up over the past two weeks or so. Totally digging it all! Also, if any of this is me just being ignorant, please feel free to say so. I'd rather learn something new.
Thanks for the great set of tools!
Copy link to clipboard
Copied
Thank you for these detailed thoughts! These are some very good feature requests.
Here my thoughts in detail:
1. Inputs panel
yes, it is an upcoming feature, which is not documented yet. It slipped into the last update by accident, but should already be working fine. Tip: In the category "User Interface & Comments" at the very top you find a new block "Input" and a dropdown in that block allows you choose one of many UI element types. As soon as you add this block to your code, in the inputs panel a corresponding input will show up. When you execute the script, the block will be replaced by the value, that the user entered in the inputs panel. This allows you to create scripts with user interfaces which are no popup dialogs, but instead are shown directly in the Automation Blocks UI as soon as you open a script.
Here is an overview of all supported UI elements and what the blocks and their UI look like:
2. Multiple Selections
I see the benefit of this. However, the AB user interface is based on a project by google which is called "Blockly". Blockly does not support multiple selections and hence, it is nearly impossible for me to add this, as long as Blockly itself does not support this.
3. keep library tree state :This is a very good feature request. I will keep it in mind for future updates.
4/5 better visualize were the error happened: very good ideas and on my feature request list now. Centering the block where the error happened and maybe even expanding a collapsed function if it happend inside that function would be very helpful. Automation Blocks already highlights each block when it is executed (usually this is so fast that you only notice some flickering), but this can definitely be improved.
6. maybe I fould add some keyboard shortcuts for that, on my feature request list now
7. I don't really understand this point. Could you explain in more detail what NUKE's corner map is working.
8. Interesting idea! Changing the BG color should be not too much work to add. I just wonder if the contrast to the blocks themselves is then still good enough or if this would mean we need to change the entire color theme.
9. this is again something that should be added to the Blockly system and that would be very hard for me to add on top of it.
10. I guess lines connecting the blocks to their function declaration blocks would become very messy soon. If you use a function on multiple places, you quickly have lines everywhere. What you can do already now is to right click on the block which executes the function and choose "highlight function definition". That will select and center the block which defines this function.
Again thank you for all the feedback! Great to see that you use Automation Blocks so extensively that all these little improvement ideas show up 🙂
Copy link to clipboard
Copied
1. This system might be interesting to have "Custom Input Dialog with Close Options" Inputs show up in Inputs so they can be used interchangeably, akin to how Essential Graphics.
4/5. "Automation Blocks already highlights each block when it is executed (usually this is so fast that you only notice some flickering), but this can definitely be improved."
I guess what I'm looking for is an ability to manually step thru each block as it's working. This might get tedious after a bit, but as a mode that can be turned on/off, this might be helpful.
7. This video shows what I was talking about, but since this is not a function of the Blockly system, it's probably not possible. I'm sure the Foundry spent a lot of time on this.
https://youtu.be/_PT-AwmgYCk?t=57
10. As an Nuke user will experience from time to time, node based systems turn into rat nests if they're not vigilant with comp management. I do get what you're saying though.
Copy link to clipboard
Copied
Oh, these corner maps look very handy in deed! Sounds like a great feature request for Blockly 🙂
concerning 4/5 what you effectively are looking for is a debugger, which allows to
- execute a code step by step or stop at certain blocks
- alllows to see the values of all variables while stepping though the code
I think there exists some debugger project for Blockly, so this might be something to consider for future versions. But the would definitely be a big project, so it won't happen soon.
Copy link to clipboard
Copied
Update for question 1:
the docs for the inputs panel (input block) are not online.