you have a box, its height depends on some other data + the porcentage of other data + a multiplayer for some reason. you end up with a lot wiring jumping from one node to another, trying to understand long ass string/funtions on parameters, etc.
maybe if we got one more context for this kind of stuff like: you go to DAOPs, some sort of VOPS(with things like reading txt files on disk or whatever (kind of PDG stuff)) well, you open this context and you have a "string" node, to create a variable name for the "height" attribute we need,then we just hook up a couple of "import parameter" node, with some math nodes like in vops to make the logic, then we just export this variable "height" and we just put something like "@var_height" in the box's size parameter. super clean and easy to read/understand all the logic behind the "height" of the box.
Could be a good context for Strings manipulation(the pain of paths writing ffs) easily solved by string nodes with things like "add", "substract", "find string", "divide by caracter", idk... endless posibilities.
then we just export something like a global variable to use it in any part of the software. like @var_variablename
hope it makes sense, sorry for my poor english.
i know its possible to do it by saving that data on attributes or whatever, but its not clean and for some things like reading data from disk it could be easier than using python or spaguetti wiring/referencing.
stop this madness of long ass funtions/parameters text in tiny windows and make it more houdini's way of doing things, a couple of nodes and wires.
EDIT: this could be a replace for those $F%4==0 kind of (function?). imagine just entering this new context and dropping a "loop count" that give you a value in a range, with some other node like "skipping every x frame", or things like that. maybe this could open a door for more procedural animation and making handling instances with custom animation offsets more easy.
EDIT: other situation where this could be usefull, RigPose, god, the amount of time you spend locking parameters, referencing etc etc.
imagine just going to DAOPs droping a "import parameters node", it brings all the parameters in the rigpose node (in a string-list type of data) then we just find every parameter with "scale" in its name, group them, and with the "lock parameters" node, we specify the parameter group name, lock all selected. easy. clean.
Limit, clamp, remap, values. for animation could be amazing, like, putting just 2 keyframes, linear, and importing that parameter into DAOPs, then remapping, adding fxs. like chops but in a VOPs style and working directly with parameters strings. no attributes, no geo.
idk, i think it could be awesome.
Other cool things:
-AI for node recomendation, vex code, etc.
-better animation-wise features. Maybe more procedural animation?
-Node bubbles and groups ("allways on top" kind of thing) yes, like social app's chats (whatsupp, messenger, etc). for big proyects is a must. you easily spend 30% of your time just trying to find specifics nodes back and fourth, i know there is the CTRL+Number thing, not the same.