Hey there!

I tried Houdini 2 years ago, and my biggest progress blocker was to define stuffs with the "traditional" typing in kind of expression creation.

My question is, is there a way to "replace" Vexpression with VEXBuilder?

Like an example in this video at 11:06
https://www.youtube.com/watch?v=dRidiaXGYrk&ab_channel=RenderEverything [www.youtube.com]

He create some fancy expressions with vexpression in the Attribute Wrangle node. Question: is there a way to put down a VEXBuilder node (can't find the name of that node) and create the same expression with (and only with)the nodes of the vex builder.

For example Substance designer functions are very similar to define an expression/function and it can uses nodes.
To somebody who has no scripting coding skills, this kind of node based expression creation would be very effective.

But for the same for example to any parameters in Houdini.

Is that very nonsense and goes against the whole theory of Houdini or is there a way to work like this?

Many thanks for the answers in advance!
Like i want to modify a parameter of a cube (let's say, its length) and i would modify it via VEXBuilder, instead of typing in the parameter field of that cube "item".
I would imagine it like i put down a VEXBuilder node under the cube item/node, and i get the parameter of the cube in the VEXBuilder, and modify it there, and then i (somehow) put that modified parameter back to the parameter of the cube

for that specific example you can put down Point VOP instead of Point Wrangle to manipulate attributes
dive inside and use nodes
like Bind VOP to read from border attribute
Clamp VOP to clamp that value
and Bind Export VOP to write the value back to the border attribute

but there is no VEX context for modifying the node parameters and writing back, even VEXpressions dont do that
the only ways to procedrally control parameters is using Expressions or CHOPs, I don't count Takes, but technically yes, Takes also

I see.
And is there any way to address a node parameter, like the length of my cube, and then drive that "address" with VEXBuilder.
Like a kind of "expose" parameter, but for not manual setting, but to able to get (drive) that parameter in VEXBuilder.

The point of this whole addressing, editing would be the node connection editing instead of typewriting (sorry can't express it better haha) the code.

I would even "typewrite" that kind of address definition, if after that addressing i can use that address in VEXBuilder.

Thanks for the quick reply!