Horzontal Page Transition Animation: “Bulldoze” with page loop

Horzontal Page Transition Animation: “Bulldoze” with page loop

For a video look here: https://plus.google.com/115366157037831519359/posts/N4vKniRC4pe

– Set Script 1 in positionchanged event of your container

– Set Script 2 somewhere easy accessible (create a shortcut/tick show in lightning menu)

– enable “snap to pages”

– don’t use items over page bounds, this would look stupid.

– zooming may break the animation.

How to use:

Enable the effect: Run script 2.

Edit screen: – Run script 2 (disables animation)

– edit as much as you want (add items, move items, remove items.)

– run script 2 again.

Please report all bugs!

And give feedback

Update 30.3.

– improve reliability

http://www.pierrox.net/android/applications/lightning_launcher/wiki/doku.php?id=script_animation_bulldoze

]]>

6 Commentsto Horzontal Page Transition Animation: “Bulldoze” with page loop

  1. Anonymous says:

    < ![CDATA[

    Wow.

    ]]>

  2. Anonymous says:

    < ![CDATA[

    That’s why I need the mentioned events. It’s just annoying always disable and enable animation manually.

    ]]>

  3. Anonymous says:

    < ![CDATA[

    With a lot of icons this script doesn’t run smooth anymore. Someone knows how to improve runtime?

    ]]>

  4. Anonymous says:

    < ![CDATA[

    Specifying my question:


    – is JSON.parse a heavy operation?


    – is LL.g(/s)etScripttag a heavy operation?


    – is getScaleX as heavy as setScale?

    ]]>

  5. Anonymous says:

    < ![CDATA[

    Could you share the desktop please ? I will run a profiler session to get accurate results.


    Everything in Javascript is heavy, but operations dealing with items modification and subsequent redraws are heavier than the script execution itself. I believe that most of the time is taken in bindings.


    JSON.parse is expensive (stringify too).


    LL.setScripttag is rather expensive because data are persisted immediately. This could be improved by deferring file write if needed. getScriptTag is cheap because the tag data is kept into memory.


    getScale is rather cheap too, although it involves some maths.

    ]]>

  6. Anonymous says:

    < ![CDATA[

    Updated.

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *