As I am writing extensions for Hype am really wishing for Live-Previews and JS running in the Hype GUI. I guess it’s also a matter of security that this still isn’t possible. In one of my recent newsletters I came across this interesting Blog-Post from Figma and their Plugin-Approaches. Maybe an int…

I am not sure what your plans are for the long run, but for the immediate future I’d appreciate some Hype tags like IE had back in the days (and a fixed parser!). This might just be really great…  …

Yeah, the reality is that there are definitely times when one would want and wouldn’t want effects to be previewed live. Right now it is both a feature and bug (depending on the effect) that these occur in the scene editor. I can see that a plugin should be able to be notified when it is okay or n…

Also it might have it’s preview code be removed on exports.

Yup, any plugin system would need to be able to identify and export differently based on the editor vs. export environment.

[image] jonathan: In fact, the scene editor will run javascript now if you include it in the head html (or as part of a .js file set to be included in the head). Here is a quick example but I am not getting all green Div's in the GUI? ActiveScriptInHeadTest.hype.zip (12,7 KB) [image] jon…

BTW I loved the times when we could enable the JSContexts. It would fire up the safari inspect allowing to peak into the WebKit stage used in the Hype GUI. https://forums.tumult.com/t/when-launching-the-beta-js-screen-appears-jscontext-window/11477?u=maxzieb

Interesting, this is a bug. For the scene editor, we run the head html through a tidy process to ensure that mangled head html code won't interfere with editing. (Of course valid head html still can in many other ways!). The tidy method we use isn't smart enough to know about the <script> tag, and…

[image] jonathan: defaults write com.tumult.Hype4 WebKitDeveloperExtras -bool YES HURRAY! It's back… :heart: This works :slight_smile: until it get's fixed… avoiding the symbol "<". <script> setInterval(function(){ var divs = document.querySelectorAll('div'); for (i = 0; i != divs.leng…

That may be the best way to do it… I was also looking into media queries with environment variables for CSS-specific cases but it doesn’t look like those are yet supported. For plugins specifically though I think it is fine if things are well defined – these are more of a case for standard CSS/JS t…

So I had a good nights sleep on the topic and what do you think about structuring the plugins around callbacks / events like the current event system (Hype‘s Observer Pattern). So many of the same events would be triggered on an dedicated listener array specific to the IDE (like HypeSceneLoad and m…

By the way. The conditional tags could potentially also solve 3rd party issues by removing these bits when rendering the head HTML to the IDE WebKit-Instance. Note the negation with the not (!) exclamation !HYPE. <!--[if !HYPE]> <script src="https://someserver.tld/1.2.3/weirdLibrary.min.js"></scrip…

The future of plugins and extensions with Hype

Extension Project

MaxZieb (Loves Hype) August 28, 2019, 10:28pm 15

First attempt at a "full" IDE plugin…