enyo-animated library: announcement & call for participation

[Doug Reeder]

I’ve started a library for practical 60 fps animated Controls:
https://github.com/DougReeder/enyo-animated

Demo at
http://hominidsoftware.com/animboot/

I’ve started with something easy: toasts. I welcome contributions and improvements (there is not yet support for browsers which don’t support CSS transitions).


Doug Reeder
reed...@gmail.com
https://ello.co/dougreeder
https://twitter.com/reeder29
http://reeder29.livejournal.com/

http://hominidsoftware.com

[Ruben Vreeken]

Hey Doug,

Looks cool! I like the toast curve animations.

Might be cool to integrate with the new animation infrastructure being developed for v2.6? That way perhaps specific types of animations could be mixed into any control.

--

Ruben Vreeken

[reed...@gmail.com]

Is the animation infrastructure documented anywhere?

-- Sent from my HP Pre3 running webOS

---

--
You received this message because you are subscribed to the Google Groups "Enyo Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enyo-developme...@googlegroups.com.
To post to this group, send email to enyo-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/enyo-development/36753f03-2ef0-4a96-af84-0ae7574a7672%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ruben Vreeken]

Not yet, the code is on github though (in master branch, I think).
It's quite modular and the basics are not very hard to follow and I'm pretty sure it wouldn't be hard to backport into 2.5 or 2.4 either.

I find the best way to follow what's goin on is simply to watch enyo on github.

--
Ruben Vreeken

[gray.norton]

Just to clarify, the new animation code on GitHub is essentially still an R & D project at this point — it’s only on working branches, and is not part of the 2.6 release.

At the moment, most of this work is being done by a “satellite” Enyo team within LG, with some amount of guidance and oversight from the core team.

It is, however, something that we are keenly interested in moving forward and would like to get into a release as soon as we’re comfortable that we have the abstractions and the APIs right.

- G

--

You received this message because you are subscribed to the Google Groups "Enyo Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enyo-developme...@googlegroups.com.
To post to this group, send email to enyo-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/enyo-development/57eb21ef-212f-4ca8-bbae-bda23b899ae6%40googlegroups.com.

[Ruben Vreeken]

Oops, sorry there Gray, I falsely assumed the changes were meant for v2.6.

I would personally love to see the new animation code materialize into a part of core or at least an official library. So far, its pretty cool, thats for sure!

Let me know if there's anything I can do to help get things right.

--

Ruben Vreeken

On Friday, November 6, 2015 at 11:47:36 PM UTC+1, gray.norton wrote:

Just to clarify, the new animation code on GitHub is essentially still an R & D project at this point — it’s only on working branches, and is not part of the 2.6 release.

At the moment, most of this work is being done by a “satellite” Enyo team within LG, with some amount of guidance and oversight from the core team.

It is, however, something that we are keenly interested in moving forward and would like to get into a release as soon as we’re comfortable that we have the abstractions and the APIs right.

- G

From: Ruben Vreeken <ruben....@gmail.com>
Reply-To: "enyo-dev...@googlegroups.com" <enyo-dev...@googlegroups.com>
Date: Friday, November 6, 2015 at 11:33 AM
To: "enyo-dev...@googlegroups.com" <enyo-dev...@googlegroups.com>
Subject: Re: [enyo-dev] Re: enyo-animated library: announcement & call for participation

Not yet, the code is on github though (in master branch, I think).
It's quite modular and the basics are not very hard to follow and I'm pretty sure it wouldn't be hard to backport into 2.5 or 2.4 either.

I find the best way to follow what's goin on is simply to watch enyo on github.

--
Ruben Vreeken

--
You received this message because you are subscribed to the Google Groups "Enyo Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enyo-developme...@googlegroups.com.

To post to this group, send email to enyo-de...@googlegroups.com.

[chris van hooser]

So is the plan for this library to have each control specifically optimized to get 60 fps? Is this going to be more for mobile?

Is there a coding style/animation style you want to keep consistent throughout the library? (like naming properties, css restrictions, etc)

Would be willing to work on some things, i do have some already that would just need to be updated and tested more, and filled out with documentation, etc.

[Doug Reeder]

The plan is to use modern APIs, such as the CSS transitions and animation APIs, and *only* animate properties that current GPUs can efficiently animate - specifically position, scale, rotation and opacity. Thus, they should work well on mobile as well as desktop (though low-end mobile hardware might not achieve 60fps).

The plan for fallbacks on older browsers is to not animate - toast will just appear and disappear, and so forth. A sluggish or janky animation is worse than none. The CSS APIs have been around for years, so few old devices could readily achieve 60fps with web technologies.

For coding style, I favor camelCase for variable and CSS classes. Naming things in the NounModifier style helps code completion tools. I’d like to use LESS, but couldn’t get it to work in my demos.

The Controls are intended to evoke smoothly-working machinery. animated.Toast slides like a well-engineered CD tray, with no bouncing as it stops. animated.ToastCurve is a more fanciful, like science-fiction machinery. Users aren’t supposed to pay attention to the animation - just get an impression of well-designed software.

A number of things can be done with just position, scale, rotation and opacity - one such would be a button that, when tapped, expands to fill its parent and fades into a new pane.

> --
> You received this message because you are subscribed to the Google Groups "Enyo Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to enyo-developme...@googlegroups.com.

> To post to this group, send email to enyo-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/enyo-development/3ff3d742-85cf-4495-a885-6bc58c55b805%40googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.