-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AnimateCSS #3113
AnimateCSS #3113
Conversation
install animate.css in vendor create animateCSS.js modify index.html
ok... I will solve localy :/ |
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. @@ Coverage Diff @@
## develop #3113 +/- ##
===========================================
- Coverage 26.15% 25.66% -0.49%
===========================================
Files 53 54 +1
Lines 11502 11760 +258
===========================================
+ Hits 3008 3018 +10
- Misses 8494 8742 +248
|
~ Issue #3111 ~ So... I purpose to you to make a test with syntax: Result: The news will come from the left, wait in the middle and come out the right Note: I repeat, it's a testing code, and need to be really merged properly with |
tested this with the same result |
@rejas says I know, I have to do better implementation Should I do better? (Of course) |
Sorry for not being more active on your PR, I really like the feature but with a newborn I cant concentrate right now much on these PRs (contrary to small stuff like dependency updates that dont take much brain power) Expect more feedback next week, then I might have more time to think about it. |
@rejas: congratulations to you ! This is happiness ! Take your time, a newborn is more important than this PR (I know the time and energy it takes!) |
I will try to do something cleaner because a test code is not made to be in production |
I realize that it's not that easy to do something cleaner @rejas, Veeck when you have some time, can you inspect ? |
Would it be possible to have something more "verbose" when calling the updateDom? Something more like Also what do you think about having the module animation configurable (just like position):
? As for the cleanliness of the code: I dont mind testing code in there, as long as the API to the modules is well-thought of. The actual implementation can be changed easily later, the API stays for a long time :-) |
Oh yes!!! very good idea. You prefer On the other hand, what bothers me, if we put all the animations in the same object that would mean that we can use the "animateOut" in the "animateIn" and vice versa I think you would like that if the name of the requested animation does not exist, we fall back on the default MM² animation Warning:
|
…nfig * add animateIn and animateOut in module definition * use directly the name of the animation * option.animate use the name of animation * can't be override with option.animate if animateIn / animateOut are defined in module definition
(sometime e2e scares me...) |
Just because humm... I'm crazy ! I just add possibility to use animateIn on start of MM² @rejas : what do you think about that ? |
@rejas : Veeck, If you want to see again ;) can I start writing the doc? |
sorry for the long turnaroundtime, lots of stuff to do and the cold is already creeping in... |
* (animateCSS.js) `_AnimateCSSIn` -> `AnimateCSSIn` * (animateCSS.js) `_AnimateCSSOut` -> `AnimateCSSOut` * (main.js) Rename `AnimateCSSOut` and `AnimateCSSIn` in accord with animateCSS.js * (main.js) Add Log.debug in animate functionality * (main.js) correct var haveAnimateName to let haveAnimateName * (main.js) Add options object for updateDom() for control speed and animate * (module.js) change value name speed -> updateOptions for more visibility and in accord with new functionality
no problem, I'm just doing my best for the next release :) Note: when #3179 is fixed, can you retry test suite? Thx Veeck |
With #3181 the test shouldn't fail anymore. I'm looking forward to this feature. Thanks @bugsounet 🙂 |
Merged develop myseld, lets see the test results :-) |
Happy crazy test! 😁 |
Ah, screw it, will merge it, we can cleanup further later if necessary (and I dont want to have @bugsounet waiting longer). This is too nice to not have, thx a lot for your work! |
I will start to write MagicMirror Doc Note: It’s a shame there isn’t a develop branch on the doc |
That's a good idea to have a develop branch, where we could collect the changes until the next release. Then we would merge it into the main branch. |
we will also have to see with @MichMich something like "https://dev-docs.magicmirror.builders/" to see develop branch result |
I've added a |
Thx @MichMich, |
I see this bugs:
--> result it will stay en hide state I think event listener (is animateCSS file) is not a proper solution |
… multiple call (#3200) PR: #3113 I see this bugs: AnimateCSS merge hide() and show() animated css class when we do multiple call --> result it will stay en hide state I think event listener (is animateCSS file) is not a proper solution I correct it with like traditional code with timer Fix too: AnimateIn on first start
Hi,
This is my testing code for AnimateCSS for
show()
,hide()
,updateDom()
Naturally, we have to do better !
I voluntarily modify
newsfeed
andcompliments
in order to testNote: I will correct checks later... it's a test...