It would be even better if javascript functions could be called as actions. At the moment I solve this with “navigate to Url” and set "javascript:my_function(); as URL, so that I can control my Bric via custom interaction.
While experimenting I noticed that the input field always stays the same width even if the window gets bigger.
@Norm maybe you could define a class that should only be available for functions in the custom interaction. If a Bric has such a class in its HTML definition, the functions become available in the Interaction Manager.
I’m working on this, each entry has different requirements, so I’m still tinkering with a good solution. Mac UI development is not as simple as responsive web design.
I actually built this into the initial release of Blocs 6, but disabled it at the last minute as I thought it had potential to create bugs if errors are manually inputed. Because Custom Interactions are such a new / complex feature, I wanted to be able to patch issues up as fast as possible without any distractions.
However, we have past the 6 month milestone so I will enable the function in the next release of Blocs. You’ll find it under actions.
Very good! The Customs Interactions are already great.
yes the concern is not unjustified, one typo and it goes wrong.
My 2nd comment with the class went in this direction, only offer functions under “call javascript” that are offered or provided by a Bric. Quasi like the export from a module. Then many things could be “remote controlled”, you could also wrap and use external APIs via Custom Interactions.
