I realized I had filtering on at github which is why I didn't see my issue reports.. thanks for fixing them! I need to get it setup to compile from github so I can check that out.
I've been putting a bunch of time into playing with this. Cools code helped me a ton, so thank you

Squirrel has some nice little benefits.
As I checked out Cools code, I noticed a library of sorts would be extremely helpful. So I started working on one (a .nut file) which will not only make things a bit simpler in dealing with layout objects, but also adds animation handling!

It looks something like this for a layout:
fe.do_nut("simplelayout.nut");
local layout = SimpleLayout();
local snap = layout.addArtwork("artSnap", "snap", 100, fe.layout.height / 2, 262, 200);
snap.enableShadow(true);
snap.addAnimation("translate", { when = Transition.FromOldSelection, path = [ [ fe.layout.width / 2, -200], [fe.layout.width / 2 , 300 ]], easing = "out", tween = "quad", reverse = true} );
snap.addAnimation("property", { when = Transition.FromOldSelection, property = "alpha", reverse = true } );
snap.addAnimation("translate", { when = Transition.ToNewSelection, path = [ [ fe.layout.width / 2, -200], [fe.layout.width / 2 , 300 ]], easing = "out", tween = "quad"} );
snap.addAnimation("property", { when = Transition.ToNewSelection, property = "alpha" } );
I have added property animator (like alpha, x, y, width, height, rotation, etc..) and a translate animator which is basically just an x, y at the same time but contains some other abilities. You can see when you do addAnimation, you can provide a config of sorts with various options. I'll probably make this a lot easier with some predefined configurations that non-coders would find easier.
In the library, I actually wrapped the objects in a new class because not only does it extend functionality of the original objects but each object can include multiple objects. Right now, I just have an extra object that duplicates the original for a shadow but this could be expanded later to have full fledged objects like a marquee wheel or something similar.
This could be something that you may want to include via code or just a .nut file that is available as an extra library. Once I have more I can let you or someone else play with it.
Another question: when I do this, I want my included .nut file to attach to the transition and tick functions.. but as it stands, it doesn't seem like I can point those functions to a function in the included .nut file. For now, I just have a transition and tick function in my main layout.nut and it redirects them to the functions in the class of the included file.