720kb / angular-fx Goto Github PK

I think it would be better if "infinite" is an attribute directive like

<a href="#" ngfx-fade-out="3 > 2" ngfx-infinite>Fadeout</a>

instead of

<a href="#" ngfx-fade-out="3 > 2" class="infinite">Fadeout</a>

[ng-].ng--start{
not working -> display:initial;
working -> display:inherit;
}

For now, animation on IE10-11 is not smooth. It's choppy.
Need to fix timings perhaps?

Reduce file sizes asap

TODO: slide animations

ng-slide-down=""
ng-slide-up=""
ng-slide-left=""
ng-slide-right=""

extra animations (away from animate.css) goes to angular-fx.css

animate.css is not the only one animations lib, we should use also add support for more libs maybe

Then you would be able to add "ngfx-slide-down" as an attribute instead of "ngfx-slide-down='true'" if you don't want any logic inside the attribute.

Hello,

Is there a way to provide an in and an out animation on the same element?

For example:

<div ngfx-fade-in="var == true" ngfx-fade-out-down="var == false">...</div>

Thanks!

ng-fx="{
'default':('hide' || 'show'),
'speed': ('slow' || 'fast' || 'medium')
};

OR

ng-fx-speed=""
ng-fx-default=""

I'm adding the shake animation to a password modal, when the password is wrong it will shake, and this works great so far, however, when I try to submit the wrong password again, it won't shake a second time. What would be the process to get this to work?

So far I have this code

ngfx-shake="modal.wrongPassword"

And in my controller on a wrong password I have this

++vm.wrongPassword;

How can I get something that makes this fire the animation multiple times in a row without having to have some sort of timeout to reset the value after the animation is done

bower

ERROR: $compile/multidir

directives with isolate scope

Check on Safari, Firefox etc..

Maybe better to serve also sub files to choose animations we want to use

I found that

ngfx-shake="ctrl.someCondition"

Does not work, wheras

ngfx-bounce="ctrl.someCondition"

does work.

Looks like there is some statements missing in the helper css file perhaps as angular-fx.css does not contain any keywords matching ´shake´.

Not that big of a deal, just wasted quite some some as I thought I was missing some dependency or the like and debugged the shake directive to confirm that it was indeed triggered.