Hi adam,
Thank you for yourappreciation. I noticed that there are severalimplementations of setTimeout. the first: setTimeoutNativeas aglobal function It's used in the virtual-DOM diff flush agorithm. the second: Timer module (aka.WXTimerModule) as a Weex Module written in Java It’s used by JS Bundle code. They both perform Javareflection and JNI call. IMHO, we can replaceTimer module with ‘setTimeoutWeex’ to test its capability. Ifit turned out to work well , we can rename 'setTimeoutWeex/setintervalWeex' to `setTimeout/setinterval` and deprecate ’setTimeoutNative’ andTimer module so as to use a unified and moreefficienttimer functionality. 原始邮件 发件人:Adam fengcxfe...@gmail.com 收件人:dev...@weex.incubator.apache.org 发送时间:2017年4月7日(周五) 11:41 主题:Re: reply：How to improve the animation in weex Excellent work for the new native timer. I have reviewed the PRhttps://github.com/apache/incubator-weex/pull/228/files. Maybe `setTimeoutWeex` is aproperintermediate name, but not a final name. There are already several `setTimeout` implementations in our SDK(e.g. global setTimeout and timer module), thus make them hard to maintain. How do you think about the name evolution, When will be the most suitable time for the new timer to rule them all ? Thanks. Adam Feng On 2017年4月7日 +0800 AM11:03, wrote: nativerequestAnimationFrameimplementation
