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.
import zim from "https://zimjs.org/cdn/02/zim_three";
const scaling = "fit"; // this will resize to fit inside the screen dimensions
const width = 1024;
const height = 768;
const color = black;
const outerColor = dark;
const assets = "mercury.jpg";
const path = "https://s3-us-west-2.amazonaws.com/s.cdpn.io/2104200/";
const waiter = new Waiter({corner:0, backgroundColor:blue});
const frame = new Frame(scaling, width, height, color, outerColor, ready, assets, path, waiter);
function ready(frame, stage, stageW, stageH) {
zog("ready from ZIM Frame"); // logs in console (F12 - choose console)
// 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
// we will use ThreeJS to show the planet and ZIM to do interface
// ZIM has a helper module for ThreeJS called three.js that makes it easy!
const outerSpace = new Three({
frame:frame,
width:stageW,
height:stageH,
// pull camera out perpendicular from monitor 400
cameraPosition:new THREE.Vector3(0, 0, 400)
});
if (outerSpace.success) { // otherwise no WebGL
const scene = outerSpace.scene;
const camera = outerSpace.camera;
var planet;
var swiper;
const loader = new THREE.TextureLoader();
loader.load(path+assets, texture=>{
// MESH
const geometry = new THREE.SphereGeometry(200, 40, 40);
const material = new THREE.MeshLambertMaterial({map: texture});
planet = new THREE.Mesh(geometry, material);
// ThreeJS use x, y and z on position and rotation properties
planet.position.x = 30;
scene.add(planet);
// LIGHT
// MeshLambertMaterial needs to have light to see it
// MeshBasicMaterial does not - but then you don't get shading
// You could also add AmbientLight but we don't need it...
// Move the light around in x, y, z to get the desired effect
// set() is a way to do x, y, z all at once
const light = new THREE.PointLight(white);
light.position.set(-500,550,800);
scene.add(light);
// ZIM Swiper for rotating planet when swiping on stage
// rotation is in radians (small)
swiper = new Swiper(stage, planet.rotation, "y", .002);
// below would let you zoom in and out based on vertical swiping
// new Swiper(stage, planet.position, "z", 2, false, -400, 0);
// start the planet off rotating but then move to swiper when stage is pressed
// assign the Ticker call to a variable to be able to remove it later
const rotate = Ticker.add(()=>{
planet.rotation.y -= .001;
});
// "stagemousedown" is whole stage - "mousedown" is only on an object on the stage
swiper.on("swipeup", ()=>{
Ticker.remove(rotate);
start();
}, null, true); // true to call function only once then remove event
});
function start() {
// ThreeJS sits on top of the first ZIM Frame's stage
// Add a second frame on top of the ThreeJS for interface
// The stage will be transparent if no color is set
// nextFrame will pass event through to the next ZIM Frame
// Note: you can't interact with ThreeJS and ZIM at the same time
new Frame({
scaling:scaling,
width:width,
height:height,
ready:ready2,
nextFrame:frame
});
function ready2(frame, stage, stageW, stageH) {
// Here is the data for the List and tips
// NOTE: this data is not real - but could be ;-)
// See the commented out area below on how we made this data - it took 5 minutes...
const craters = ["Caloris", "Degas", "Beethoven", "Hokusai", "Abedin", "Eminesu", "ZIM", "Rembrandt", "Dickens", "Debussy", "Abu Newas", "Balagtas", "Copland", "Navoi", "Derain"]
const data = [[-0.51,296.19],[-1.42,180.74],[-1.93,544.98],[-2.59,133.58],[-2.95,481.56],[-3.9,214.89],[-4.25,502.7],[-5.27,523.84],[-5.81,170.98],[-5.94,367.74],[-6.48,143.34],[-7.7,180.74],[-8.23,538.48],[1.02,522.22],[0.48,175.86]]
var tipTimeout;
const list = new List({
list:craters
})
// make sure we specify this stage otherwise it gets put on the first stage
// and we will not have updated that first stage at this time
// so if we left off stage, when working in the second stage, we would not see the list
// SUMMARY - when working on a stage other than the first stage,
// we have to specify the stage for things like center(), loc(), pos(), Ticker.add(), Pane(), Grid(), etc.
.pos(30,100,null,null,stage)
.alp(0)
.animate({alpha:.5}, .7)
// using tap instead of change so can locate current selection again if needed
.tap(()=>{
// we do not want to rotate planet more than 360 degrees to get to data
// so set the planet to the modulus of 360 immediately in Swiper
// this means the Swiper will set the rotation the modulus and not damp to it
swiper.immediate(planet.rotation.y%(2*Math.PI));
// now damp to the desired location to animate the planet
// we could use ZIM animate() but for ThreeJS we need to set up a proxy object
// which is a few extra steps... so we just use the swiper
swiper.desiredValue = data[list.selectedIndex][0]; // rotation data
// but clear any previous timeout calls just in case
// this is why we declared tipTimeout outside the tap function
// so the next time we tap, we can clear it
// alternatively, we could have removed the tap event until the timeout has completed
// This type of event manipulation is often present in Interactive Media
// we have been doing it since Macromedia Director back in the nineties
if (tipTimeout) tipTimeout.clear();
tipTimeout = timeout(.8, ()=>{
// make a tip with the list text and the y data
// makeTip is a custom function with a Circle and a Tip (an auto positioned Label)
makeTip(list.text, data[list.selectedIndex][1]);
});
});
// start the List off with no selection
list.selectedIndex = -1;
function makeTip(text, y) {
// we could use clear or null instead of faint
// but we are going to drag the circle around to create the data
// clear or null would not let us drag the middle of the circle
// just left this in there for demonstration - would normally set to null
let circle = new Circle(50, faint, white, 2)
.center(stage)
.mov(35) // shift over in the x to match planet center
.loc(null, y-10) // apply the y data
.alp(0)
.animate({alpha:1}, .5)
// .drag({all:true}); // drag was set to record y position
// // used for recording rotation and y position for tips
// new Circle(10, null, white, 2).center(circle);
// stage.on("stagemouseup", () => {
// circle.x = stageW/2+48; // force the x position - could set boundary on drag
// zog("[" + decimals(planet.rotation.y,2) + "," + decimals(circle.y,2) + "]");
// });
let tip = new Tip({
text:text,
backgroundColor:white,
color:black,
shadowColor:-1,
outside:true, // outside the circle
target:circle,
align:"center",
valign:"bottom",
margin:14,
corner:0,
size:20
}).alp(0).show(null,1000000000).animate({alpha:.6}, .5);
// remove the tip on stagemousedown
// could reuse the tip, etc. but it is tricky to properly center an edited tip
// so just rebuild it all in the function
// NOTE: this was commented out to record data
stage.on("stagemousedown", ()=>{
tip.dispose();
circle.removeFrom();
}, null, true); // only once
}
// makeTip(); // used for recording data
}; // end frame2 ready
} // end start function when stage first pressed
} // end ThreeJS model in place
// Label is on first stage
new Label({text:"ZIM with ThreeJS", color:white}).alp(.8).sca(.8).pos(30,30);
stage.update();
// FOOTER
// Please see a greeting message - then come visit us at ZIM https://zimjs.com
createGreet();
// call remote script to make ZIM Foundation for Creative Coding icon
createIcon();
// DOCS FOR ITEMS USED
// https://zimjs.com/docs.html?item=Frame
// https://zimjs.com/docs.html?item=Circle
// https://zimjs.com/docs.html?item=Label
// https://zimjs.com/docs.html?item=Tip
// https://zimjs.com/docs.html?item=Waiter
// https://zimjs.com/docs.html?item=List
// https://zimjs.com/docs.html?item=tap
// https://zimjs.com/docs.html?item=drag
// https://zimjs.com/docs.html?item=animate
// https://zimjs.com/docs.html?item=pos
// https://zimjs.com/docs.html?item=loc
// https://zimjs.com/docs.html?item=mov
// https://zimjs.com/docs.html?item=alp
// https://zimjs.com/docs.html?item=sca
// https://zimjs.com/docs.html?item=removeFrom
// https://zimjs.com/docs.html?item=center
// https://zimjs.com/docs.html?item=Grid
// https://zimjs.com/docs.html?item=Swiper
// https://zimjs.com/docs.html?item=timeout
// https://zimjs.com/docs.html?item=decimals
// https://zimjs.com/docs.html?item=zog
// https://zimjs.com/docs.html?item=Ticker
} // end of frame ready
Also see: Tab Triggers