Dekok: React’s GUI isn’t.

 
Jordison: My solution to interruption is and always has been relative animation. By relative I mean animating additvely from the old value minus the new value to zero. Top secret but I have actually been animating an array of children, in React, which is why your conversation caught my ear.

Delillo: The trick is that itโ€™s additive. Everything I do is additive animation.

Mikez: Trucchi: thanks. yeah, I’m gonna pitch this

Brashears: Looks like what we should be using

Bruchman: I have a derivate work of the web-animations-legacy.js shim reconfigured to feel more like Core Animation, and some demos Iโ€™ve been working on.

Groeschel: Http://codepen.io/kvndy/pen/YyXLWp?editors=001

Kling: Http://codepen.io/kvndy/pen/meJYEj?editors=001

Crowder: SoCalled: L8D informed me of ngAnimate’s means of handling arrays, which is it auto-watches them for changes. If a change is detected, any ng-repeat elements will then have proper cl***es added to them for things that change. The cl***es added include the begin, active and end of the animation. I’m not sure that helps in any other situation than something entirely changes

Rosetti: The first is additve keyframe blending. The second is implicit animation. Both are examples of that derivate work

Hoeck: I have a huge chunk of stuff I’m moving in clipboard before I can venture there, gimme a few and I’ll take a look ;

Roaoo: I am very interested in ngAnimate. Provides a lot of the hooks for animation, as I understand it.

Messore: Adds in cl***es when certain things events in general occur and you just use standard CSS to handle those added/removed cl***es properly

Wisse: Kind of. Got to try it out, look at more examples of course

Like: Hey folks, now that all popular browsers support defineProperty, i.e. getter and setter

Trucchi: SoCalled: you still have to define CSS animations yourself, it just automates how they get applied for you

Braskett: When should one use getFoo setFoo and when just getter setter foo?

Jeffress: Hannibal_Smith: http://hijinksensue.com/comic/surface-tension/

Mayhugh: Profsimm: why would you want to use either?

Jeffress: Hannibal_Smith: note the date

Floch: Dekok: well, you know. My current example is I have an API for a panel. And you can get the panel title and set it.

Baas: Ahaha dash yes I also noticed how they copied it

Pluid: Dekok: I also have properties like “focused” and “blocked”

Trucchi: Profsimm: honestly? getter/setter is a bit of a code smell, even though it’s nifty at first glance. Best not to use it except for very specific cases, since it leads to side effects where they might not be expected

Woge: Dekok: also, x, y, width, height

Rane: Profsimm: if you make all your objects immutable you won’t have that problem :

Burdon: But dash in the end this even was really bad.but I was really without words when Apple insist on “app are the future”

Gambrell: Now that a good number of apps are hybrids

Trucchi: Profsimm: like, if I set obj.foo, I typically don’t expect to be triggering anything

Hendericks: Dekok: that literally doesn’t make sense for GUI ๐Ÿ˜›

Trucchi: But if I call a function that does, I’ll have lookeda t the docs for that function and know that it causes something to happen

Burba: Or even better, when you don’t need an app at all because.you have a browser

Strozzi: Profsimm: it’s the thing that makes *the most sense* for GUIs. Look at React, for example

Randklev: Trucchi: I know, right. But it’s a habit from before defineProperty was available.

Pinke: Trucchi: I have worse concerns. Sometimes setting is not so simple. ***ign a value and done. It may require more params

Jeffress: Profsimm: that’s why objects have methods ๐Ÿ˜€

Paliotta: Dekok: React’s GUI isn’t immutable, you just rebuild an immutable definition, delta is extracted, then applied to a mutable GUI