vivshaw

declare namespace             ⵔ             {
             type             Ѻ
      =never;type             ⵔ
                =            "ⵔ"
             type             〇
                =            "〇"
             type             O
                =             〇
                |             ⵔ
             type             o             <

micimize

 
   C=   XD   =1
      D= '8'
   OwO  =(
     o=0,
     O=  XD
            ^('-')>     XD
     <(' - ')^                  XD
               ^('-')^   XD
          ==`    `==               XD

chenglou

Interesting part (unmounting & API) is at the end if you're not interested in the rest =).

Stress Tests

This animation proposal is just an attempt. In case it doesn't work out, I've gathered a few examples that can test the power of a future animation system.

1. Parent is an infinitely spinning ball, and has a child ball that is also spinning. Clicking on the parent causes child to reverse spinning direction. This tests the ability of the animation system to compose animation, not in the sense of applying multiple interpolations to one or more variables passed onto the child (this should be trivial), but in the sense that the parent's constantly updating at the same time as the child, and has to ensure that it passes the animation commands correctly to it. This also tests that we can still intercept these animations (the clicking) and immediately change their configuration instead of queueing them.

2. Typing letters and let them fly in concurrently. This tests concurrency, coordination of an array of ch

jgranick

<?xml version="1.0" encoding="utf-8"?>
<project>
	
	
	<!-- <meta />
		
		Use meta nodes to set metadata for your application. The description is ignored
		on most targets, but is useful for packaging like Chrome Apps or Opera Widgets.
		
		For compatibility with Android and webOS, the package name must include at least