HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html>
tag. If you want to add classes there that can affect the whole document, this is the place to do it.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. If you need things in the <head>
of the document, put that code here.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.
To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit-
or -moz-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
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.
You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
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.
You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.
If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.
You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
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.
Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
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
// http://www.snorkl.tv/challenge/
// REFERENCES for ZIM at http://zimjs.com
// see http://zimjs.com/learn.html for video and code tutorials
// see http://zimjs.com/docs.html for documentation
// see https://www.youtube.com/watch?v=pUjHFptXspM for INTRO to ZIM
// see https://www.youtube.com/watch?v=v7OT0YrDWiY for INTRO to CODE
// CODE HERE
// 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)
.center()
.animate({
from:true,
props:{alpha:0},
time:2
})
.tap(()=>{ // restarting
loop([tile,g,r,b], o=>{o.replayTween()});
});
const g = new Rectangle(tile.width,10,green)
.reg(0)
.pos(0,-12,LEFT,BOTTOM,tile)
.animate({
props:{scaleX:0},
from:true,
ease:"linear",
time:6
});
const r = new Rectangle(50,50,red,lighter,3)
.loc(tile.getChildAt(3*8), null, tile)
.animate([
{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)
.animate([
{props:{x:"-150"}, wait:2, ease:"bounceOut", call:rotate},
{props:{y:"150"}, wait:1, time:2, ease:"quadOut"}
])
function rotate(target) {
target.animate({
props:{rotation:"360"},
wait:2,
ease:"backOut"
});
}
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
// });
// TWEEN CONSIDERATIONS
// 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
// DOCS FOR ITEMS USED
// https://zimjs.com/docs.html?item=Frame
// https://zimjs.com/docs.html?item=Rectangle
// https://zimjs.com/docs.html?item=tap
// https://zimjs.com/docs.html?item=animate
// https://zimjs.com/docs.html?item=stopAnimate
// https://zimjs.com/docs.html?item=pauseAnimate
// https://zimjs.com/docs.html?item=loop
// https://zimjs.com/docs.html?item=pos
// https://zimjs.com/docs.html?item=loc
// https://zimjs.com/docs.html?item=center
// https://zimjs.com/docs.html?item=Tile
// https://zimjs.com/docs.html?item=zog
// FOOTER
// call remote script to make ZIM Foundation for Creative Coding icon
createIcon();
}); // end of ready
Also see: Tab Triggers