Pen Settings



CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URLs added here will be added as <link>s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.

+ add another resource


Babel includes JSX processing.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

+ add another resource


Add Packages

Search for and use JavaScript packages from npm here. By selecting a package, an import statement will be added to the top of the JavaScript editor for this package.


Auto Save

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.






                // as of ZIM 5.5.0 you do not need to put zim before ZIM functions and classes
const frame = new Frame("fit", 800, 600, lighter, dark);
frame.on("ready", ()=>{ // ES6 Arrow Function - similar to function(){}
	zog("ready from ZIM Frame"); // logs in console (F12 - choose console)

	// often need below - so consider it part of the template
	let stage = frame.stage;
	let stageW = frame.width;
	let stageH = frame.height;
	// I have a feeling I might regret this!  
	// But it is always great to learn and challenge yourself!  
	// Thanks Carl for the challenge
	// I like your messages to on the post 

	// see for video and code tutorials
	// see for documentation
	// see for INTRO to ZIM
	// see for INTRO to CODE


    // 10.9.1 BETA - introducing seconds
    // ZIM powered has been milliseconds based - inherited from CreateJS
    zim.TIME = "seconds";
	STYLE = {centerReg:true};	
	const tile = new Tile(new Rectangle(50,50,light,lighter,3), 8, 7)
        .tap(()=>{ // restarting
            loop([tile,g,r,b], o=>{o.replayTween()});

	const g = new Rectangle(tile.width,10,green)

	const r = new Rectangle(50,50,red,lighter,3)
		.loc(tile.getChildAt(3*8), null, tile)
			{props:{x:"150"}, wait:2, ease:"bounceOut", call:rotate}, // default ease is quadInOut
			{props:{y:"-150"}, wait:1, time:2, ease:"quadOut"}
	const b = new Rectangle(50,50,blue,lighter,3)
		.loc(tile.getChildAt(4*8-1), null, tile)
			{props:{x:"-150"}, wait:2, ease:"bounceOut", call:rotate},
			{props:{y:"150"}, wait:1, time:2, ease:"quadOut"}
	function rotate(target) {
	STYLE = {}
	stage.update(); // this is needed to show any changes
	// const s = new Squiggle().pos(0,40,CENTER)
    // const c = new Circle(20).addTo().animate({
    //     props:{path:s},
    //     rewind:true,
    //     loop:true,
    //     drag:true,
    //     startPaused:false,
    //     time:3
    // });


    // With ZIM, we chain animate() to objects
    // although can use CreateJS Tween() to chain to tween
    // like with GreenSock - or use GreenSock, etc.
    // 95% of our tweens are just on the object
    // pauseAnimate() and stopAnimate() are methods or global functions
    // and can be used to pause or stop animations 
	// or animations with shared ids
    // but storing completed tweens to replay them would be bad
    // we animate particles, etc.
    // so... run a replayTween() on the object

    // ZIM has series animations with an array of animation objects
    // These will run one after another so avoids calculating waits
    // We can run animations on different objects in a series
    // but nested series are not supported at this time
    // Where an object animates and then two or more objects animate
    // we are unable to run both those objects in a series
    // This leaves us back at running the subsequent objects
    // in the first object's callback function
    // or setting waits on the subsequent objects
	// So, well aware of these drawbacks 
	// but having used a chained Tween for a number of years, 
	// I find that chaining to the object is a lot easier most of the time 
	// I would definitely not want to go back. 
	// Agreed, in cases of a series of animations and calls, it can't be beat. 
	// But in making Interactive Media as opposed to more authorative works,
	// The animations usually happen on interaction
	// and seldomly require a complex series - or one beyond the ZIM series system.
	// Flattening the Tween chaining 
	// and moving the options into parameters 
	// makes sense in ZIM with the ZIM DUO technique 
	// of traditional parameters or configuration objects 
	// new Circle().center().animate({scale:2}, .7); 
	// // or 
	// new Circle().center().animate({
	// 	props:{scale:2},
	// 	time:.7,
	// 	rewind:true
	// }); // or on one line if desired


	// call remote script to make ZIM Foundation for Creative Coding icon

}); // end of ready