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 URL's added here will be added as <link>
s in order, and before the CSS in the editor. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.
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.
If the stylesheet 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 CSS 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.
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 Skypack, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ES6 import
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.
<script id="fragShader" type="shader-code">
uniform sampler2D tex;//The main texture
uniform sampler2D norm;//The normal texture
uniform vec2 res;//Our screen dimensions
uniform vec4 light;//Our light source information
void main() {
vec2 pixel = gl_FragCoord.xy / res.xy;
vec4 color = texture2D(tex,pixel);
vec4 normalVector = texture2D(norm,pixel);//We get the normal value of this pixel
vec2 lightPosition = light.xy / res.xy;//We normalize the light source
lightPosition.y = 1.0 - lightPosition.y;
//We calculate the direction from the light to this pixel
vec3 LightVector = vec3(lightPosition.x - pixel.x,lightPosition.y - pixel.y,light.z);
//By "up" direction of our normal map has the value (0.5,0.5,1.0) in terms of rgb
//So we offset by that amount
normalVector.x -= 0.5;
normalVector.y -= 0.5;
//We normalize our vectors to compute the direction
vec3 NormalVector = normalize(normalVector.xyz);
LightVector = normalize(LightVector);
// Compute the diffuse term for the Phong equation
float diffuse = 1.5 * max(dot( NormalVector, LightVector ),0.0);
//Toggle light system on or off
if(light.w == 0.0){
gl_FragColor = color;
} else {
gl_FragColor = color * diffuse;
}
}
</script>
/* We want our scene to span the entire window */
body { margin: 0; }
//@author Omar Shehata. 2015.
//We are loading the Three.js library from the cdn here: https://cdnjs.com/libraries/three.js/
var scene;
var camera;
var renderer;
function scene_setup(){
//This is all code needed to set up a basic ThreeJS scene
//First we initialize the scene and our camera
scene = new THREE.Scene();
camera = new THREE.PerspectiveCamera( 75, window.innerWidth / window.innerHeight, 0.1, 1000 );
//We create the WebGL renderer and add it to the document
renderer = new THREE.WebGLRenderer();
renderer.setSize( window.innerWidth, window.innerHeight );
document.body.appendChild( renderer.domElement );
}
//Initialize the Threejs scene
scene_setup();
//Pull the shader code from the html
var shaderCode = document.getElementById("fragShader").innerHTML;
//Our textures are up on github
var textureURL = "https://raw.githubusercontent.com/tutsplus/Beginners-Guide-to-Shaders/master/Part3/images/blocks.JPG"
var normalURL = "https://raw.githubusercontent.com/tutsplus/Beginners-Guide-to-Shaders/master/Part3/normal_maps/blocks_normal.JPG"
THREE.ImageUtils.crossOrigin = '';//Allows us to load an external image
//Load in the texture and the normal
var texture = THREE.ImageUtils.loadTexture(textureURL);
var normal = THREE.ImageUtils.loadTexture(normalURL);
//Set up the uniforms we'll send to our share
//More info on uniform types: https://threejs.org/docs/#Reference/Materials/ShaderMaterial
var uniforms = {
tex : {type:'t',value:texture},//The texture
norm: {type:'t',value:normal},//Normal
res : {type: 'v2',value:new THREE.Vector2(window.innerWidth,window.innerHeight)},//Keeps the resolution
light: {type: 'v4',value:new THREE.Vector4()}//Our light source, we will use the 3 numbers as have x,y and height away from the screen. 4th value is whether the light is on or not
}
//We stick our shader onto a 2d plane big enough to fill the screen
var material = new THREE.ShaderMaterial({uniforms:uniforms,fragmentShader:shaderCode})
var geometry = new THREE.PlaneGeometry( 10, 10 );
var sprite = new THREE.Mesh( geometry,material );
//Add it to the scene
scene.add( sprite );
//Move the camera back so we can see it
camera.position.z = 2;
uniforms.light.value.z = 0.3;//How high up our light source should be
uniforms.light.value.w = 1.0;//Turn light on
//Render everything!
function render() {
requestAnimationFrame( render );
renderer.render( scene, camera );
}
render();
document.onmousemove = function(event){
//Update the light source to follow our mouse
uniforms.light.value.x = event.clientX;
uniforms.light.value.y = event.clientY;
}
document.onmousedown = function(event){
//Toggle lighting system
if( uniforms.light.value.w)
uniforms.light.value.w = 0.0;
else uniforms.light.value.w = 1.0;
}
Also see: Tab Triggers