Hype Command Pipeline

Extension Project
1

Hype CommandPipeline

Hype-commandPipeline
Hype-commandPipeline1280×905

Usage and inspiration

20181108-0dhxv.jpg1526×400 66.7 KB

As I saw this approach used in simpler ways on the forum. The idea behind it is that one maps different function calls originating by triggering custom behavior onto the same handler function and then uses event.customBehaviorName to run an action.

This allows you to call functions in the hypeDocument scope using the timeline or actions panel without wrapping them in a Hype function first. This is specially useful for commands that trigger stuff from the timeline as you don’t have to create all these hype function wrappers for slight differences in parameters. Triggering the command …

myFunction|"I am a string", 1

… will call the function hypeDocument.myFunction(“I am a string”, 1);. Although for this example to run properly you would need to define that function first like…

hypeDocument.myFunction = function(message, nr){
    console.log("HypeCommandPipeline:", message, nr);
}

You can call built-in functions but mostly that doesn’t make sense as they are already offered in the dropdowns in Hype. Then there are limits in the complexity of arguments as we can’t pass in more than simple objects (so no HTMLDivElement etc.). But at least they can be nested, so the arguments go beyond only strings, as the custom behavior name is actually parsed based on JSON. So, you can do this…

myFunction|"I am a string", 1, { "hello": [1,2,3,4,5,6] }

Code repository on GitHub

Simple Example

HypeCommandPipelineExample.hype.zip

Version history

1.0 (Beta) Initial release under MIT-license
1.1 Fixed error handling and now the errors are detailed
1.2 Fixed pipeline and made parsing more robust
1.3 Converted into a self contained extension

Content Delivery Network (CDN)

Latest version can be linked into your project using the following in the head section of your project:

<script src="https://cdn.jsdelivr.net/gh/worldoptimizer/HypeCommandPipeline/HypeCommandPipeline.min.js"></script>

Optionally you can also link a SRI version or specific releases.
Read more about that on the JsDelivr (CDN) page for this extension at https://www.jsdelivr.com/package/gh/worldoptimizer/HypeCommandPipeline

Learn how to use the latest extension version and how to combine extensions into one file at

5 Likes
2

There’s a way to “abuse” export scripts in a similar fashion that I realized when developing could be used in such a manner for direct javascript calls, but I hadn’t thought of this dynamic method! Clever.

3

↑ look at project
1.3 Converted into a self contained extension

4

Hi Max!

Would You provide a Hype doc of your demo code above?

Thanks.

5

↑ look at project
Added simple example

6

Thank You! :+1:

7

the idea is that the triggering of a custombehaviour is NOT restricted to an existing custombehaviour. any triggering of a custombehaviour thru the API will forward the event. Within a callback for ‘HypeTriggerCustomBehavior’ you’ll then have the opportunity to handle the element and the string that the event carried along …

8

That is precily the idea. You could also use this to build a bridge to some wrapper like electron or a story engine. Here we use it to create function calls to hypeDocument functions (specially to custom onces).

By the way: You could also use an exporter script enviroment to register custom function mappings for the IDE but nobody is really doing it as its Python and bound to the enviroment your exporting to. Hope that plugins transfer that logic to Javascript and out of the specific exporter script enviroment. If your not sure what I am talking about look at:

As long as we are waiting Hype CommandPipeline is a solution.