I know I'm about a year late to the request for new 5.0 features. But I would like to encourage integrating the excellent HypeBlendModes by @MaxZieb into the Hype u.i. I'd love to have a pull-down menu of ink effects that I can apply to any object and have Hype add the needed code into the Head HTML and apply the additional HTML attributes for me.
Me (and the folks I work with) aren't much in the way of coders. We're simple folks, haha. User experience add-ons like this would get used more by us than things like physics and bones.
In the meantime, take a look at display: contents. As for blend modes … they’re browser native. My implementations are simply workarounds to mitigate the downsides of Hype’s container structure, which I believe are unnecessary. As demonstrated in my 3D example, these containers tend to cause more problems than they solve. I genuinely hope they’re removed in version 5.0.
How is that problem managed? Previously, you might try device detection, multiple event listeners, using JavaScript to determine the features supported by the browser. You can even see in Hype that actions have parentheses… On Mouse Down (Touch Start).
I was getting ready to write a function to monitor the devices. If it's a mouse event, do this… if it's a touch event, do that… except it's not so simple and my app crashed immediately. Do I use… Try / Catch? Do I use a toggle? A button on first click?
It was getting complicated!
Fortunately, PointerEvent is baseline. I simply changed my event listeners to use pointerdown, pointermove, and pointerup. Now the puzzle is starting to work on mobile.
I suppose Tumult could decide it's not worth the hassle to rewrite code that already works. However, this supports “pen” inputs, which could create interesting possibilities… pressure, width, tilt …but I suppose that is rare. Controller support would be better. That's why this is a housekeeping idea.
Yes, this would be a good idea to migrate to more "modern" event tracking. Definitely more of a refactoring though, it is definitely an "if it ain't broke" situation... though that's not to say there are some edge case issues I wonder if this would help with. Filed, thanks!
I just saw the news that there are new baseline CSS units…
While working on the Jigsaw game, I switched to using newer css units. They're very convenient. I was using vmin and vmax a lot.
Although, I'm not sure if I had gotten the centering perfect. It seemed like something was off. I was busy solving other issues, so I forgot about it. Also, I had forgotten about Apple's annoying “Cover Notches” problem.
It was nice to see a possible solution… small viewport and large viewport …and even better… dynamic viewport. I haven't experimented with it yet, but I think there's a general idea here… this is a nice feature!
So, I added it to the list of ideas for Hype 5 features. Perhaps it's a good idea for Hype to better support CSS units, to do something besides pixels. Part of the problem of designing websites lately are all of the screen sizes. I often end up throwing elements in a group and just scaling the group, but that can be a problematic. Recently, I've been trying to avoid using scale() and these new CSS units have been useful in getting that done.
Yes, we have items on our feature list for adding other units. It is mostly a UI/preview challenge in not wanting to add complexity and since the units actually have meaning be able to properly show that in the situations where they matter. Sadly keeping everything in 'px' is the most simple way to present and modify elements.