Jump to content
Search Community

Green-Alpha

Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by Green-Alpha

  1. I agree with what you said @OSUblake but this mean 0 support for blur or any other simple effect that we can apply frequently.

     

    With this point of view we will never see

     

    gsap.to(elem, {
      blur : 10
    })

    on gsap, and this mean ignore an important stuff because the implementation can't fit with all case of use, and use "tricks" to achieve the simple goal.

     

    I ask myself : when and how many time i will use the filters with complex structure ? Probably 0.1% of time, and when this case will happen, i will easily switch to fallback by specifying the filter manually.

     

    But I really understand that you want keep the fit all logic !

  2. Thank you for this replies :)

     

    @OSUblake Houston, we got a problem ^^ I keep it in mind, for now I will go with simple filters, because i parse filters and get an object like :

     

    {
      dropShadow : ['0 0 10px #000'],
      blur : [10]
    }

    So this will be "inline", but i don't think i will have to set this property with specific order.

  3. Hello,

     

    Is it possible to extend gsap properties ? I mean we set individual properties "translate, scale..." and then set CSS transform to translate/scale... on element.

     

    I think gsap doesnt handle properties like blur, brightness because of old IE have a specific behavior with CSS filter property, right ? Anyway I have to find a way to do it quicker than  :

     

    gsap.to({
    	blur : 0
    }, {
    	duration : 1,
    	blur : 10,
    	onUpdate : function() {
    		elem.style.filter = [...];
    	}
    });

     

    Like :

     

    gsap.to(elem, {
      duration : 1,
      blur : 5,
      brightness : 2
    });

     

    What is the best way to achieve this ? or more generally how to extend properties ?

     

    Thanks !

×
×
  • Create New...