Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

richardCANE last won the day on June 18 2014

richardCANE had the most liked content!


  • Content Count

  • Joined

  • Last visited

  • Days Won


richardCANE last won the day on June 18 2014

richardCANE had the most liked content!

Community Reputation

6 Newbie

About richardCANE

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
    Vienna, Austria
  1. Dear Supporters! After a couple of days of development, I have finally arrived to 2 main conclusions regarding which techniques should I use. I am still learning the Tween/Timeline/Lite/Max frameworks, but my current project will be done with: 1.: As these frameworks are highly optimized, even 50-125 tweens at once did not chew significant resources from the test machines, so most of the time I will stick with TweenLite.to(...). 2.: In other, less often cases I will mix TweenLite.to(...) with the suggested CSSRulePlugin and for "fixed tweens" (basically motions without prop changi
  2. Hi Jamie! Thank you for the CodePen efforts! I am seriously considering on using the CSSRulePlugin as you showed me. I will try out Carl's solutions and yours too. I will get back here with my experiences soon.
  3. Hey Carl! Thanks for the CodePen examples! I did not know, that I can use "{timelineMaxInstance}.tweenTo(...)", nor that "method" to switch the "progress" between 0 and 1 along with the "ease" too correspondingly. THAT IS A GREAT FEATURE, AMAZING CAPABILITY! My jaw dropped on this feature of TimelineMax. I will definitely try it and get back with the results.
  4. Hey Rodrigo! Thanks for the CodePen! One of my first thoughts on this issue during my previous days whas just one TimelineLite and play back-and-forth, basically something like: //... in the onEvent function // ..... if( !active ) { timeline.play(0, true); // play from 0th and surpress events } else { timeline.reverse(); // play reversely } // ..... ...and this would really work most *.easeInOut and for linear/none easing functions. However, for the sake of swiftness, I try to tween UI, but also provide fast and usable interface. Therefore, I use Expo.easeOut easing func
  5. Hey Jonathan! Thank you for your response! The "Example 1" - http://codepen.io/jonathan/pen/xcFHu you forked does not work, when you click rapidly (please try out yourself - click rapidly for 10-20 times, the tweens "die"). As for the "Example 2" - if you read what I wrote, what is my situation with the lots of tweens, I deliberately do not want to instantiate 40-50-60 TweenLite instances on every state changes (so fundamentally on every "onClick" events) again and again in functions. The TweenLite and TimelineLite (and the "Max"-es) are insanely great tools, when tweens are ne
  6. My current project (JavaScript/GSAP) needs lots of tweening on different elements at the same time (it will be a heavily tweened/animated site). In "lots of" I mean 50-75 "TweenLite.to"s per click event, in total about 150-300 css properties to tween. It would be used all over the site on elements (buttons, menus, forms). Most of the elements will have 2 states, an "active" and an "inactive" state, basically when the user clicks on a menu, the menu will be activate, click again/elsewhere and goes to inactive. To efficiently manage the tweens, I would like to use TimelineLite, create a
  7. hi all! i have a flash ( Flash CS4 - AS3 ) site with a loader.swf that loads 20 components ( 01.swf -> 20.swf ) . each component uses TweenMax with tweenings and functions and i know that TM is small ( and of course F***** Awesome ), but when i import into each of the components the final filesizes ( .swf ) will be increased with 200-300 kbytes ( 20 x 10/15 kB ). is there a way to compile the TM alone to a swf file ( example: tweenmax.swf ) and the loader loads the tweenmax.swf first, before the other components and the components can use TM without import and compile to each compon