This tutorial demonstrates how to seamlessly integrate WebGL effects into existing <image></image>
and <video></video>
elements on a webpage. While several resources address this topic, this guide simplifies the process, focusing on the crucial connection between standard web pages and WebGL. We'll build an interactive image slider with a dynamic mouse hover effect.
The core functionality of the slider and intricate WebGL/GLSL shader details won't be covered extensively. However, the demo code includes comments and links for further learning. Note that we're using WebGL2 and GLSL 300, which are not compatible with Safari or Internet Explorer. Use Chrome or Firefox for the demos. For production use, consider loading both GLSL 100 and 300 shader versions, using GLSL 300 only when curtains.renderer._isWebGL2
is true (as shown in the demo).
Step 1: Build Your Webpage
Create your HTML, CSS, and JavaScript as usual. Our example is an image slider, but the principles apply broadly. The slider features:
- Slides spanning the full page width.
- Momentum-based dragging and snapping to the nearest slide.
- Exit and enter animations for slides.
- An interactive hover effect.
GreenSock Animation Platform (GSAP) is used for animation and dragging, offering plugins for drag interactions, momentum, and text line splitting. If you're unfamiliar with GSAP sliders, explore the demo code for guidance. These DOM elements will be synchronized with our WebGL rendering.
Step 2: WebGL Rendering with CurtainsJS
We'll render images using WebGL. This involves:
- Loading images as textures in a GLSL shader.
- Creating WebGL planes for images and applying textures.
- Positioning and scaling planes to match their DOM counterparts.
CurtainsJS simplifies this process by handling the synchronization between DOM and WebGL elements during scrolling and user interactions. Here's the essential JavaScript:
// Create a Curtains instance const curtains = new Curtains({ container: "canvas", autoRender: false }); // Single rAF for GSAP and Curtains function renderScene() { curtains.render(); } gsap.ticker.add(renderScene); // Curtains parameters const params = { vertexShaderID: "slider-planes-vs", fragmentShaderID: "slider-planes-fs", uniforms: { // ... } }; // Create planes for each slide const planeElements = document.querySelectorAll(".slide"); planeElements.forEach((planeEl, i) => { const plane = curtains.addPlane(planeEl, params); if (plane) { plane.onReady(function() { plane.htmlElement.closest(".slide").classList.add("loaded"); }); } });
The updateProgress
function needs modification to update WebGL planes:
function updateProgress() { // Update slider animation.progress(wrapVal(this.x) / wrapWidth); // Update WebGL planes planes.forEach(plane => plane.updatePosition()); }
Basic vertex and fragment shaders are needed to display textures. These can be loaded via <script></script>
tags or using backticks (as in the demo). The vertex shader positions planes, while the fragment shader processes pixels. Remember the shader variable prefixes: in
, uniform
, and out
.
Step 3: Implementing WebGL Effects
Now, let's add effects. Our inspiration video features:
- Color inversion.
- A fisheye effect around the mouse.
- Animated radius around the mouse.
- Smooth radius animation.
- Image translation based on mouse position.
Shaders lack memory between frames. To animate effects (like the radius), use JavaScript variables and pass them to each frame.
Modify shaders to invert colors outside the radius and create the fisheye effect. The focus here is the DOM-WebGL connection, so shader details are minimized, but comments are provided.
Finding pre-made WebGL shaders for websites is challenging. ShaderToy and VertexShaderArt offer impressive shaders, but not necessarily for typical website effects.
Step 4: Connecting JavaScript and Shaders
Add interactivity by passing uniforms to shaders and modifying them based on user interactions.
Declare uniforms in shaders:
// Vertex shader uniform vec2 uMouse; // Fragment shader uniform float uRadius; uniform vec2 uResolution;
Add uniform values to the Curtains parameters:
const params = { // ... uniforms: { mouse: { name: "uMouse", type: "2f", value: mouse }, radius: { name: "uRadius", type: "1f", value: radius.val }, resolution: { name: "uResolution", type: "2f", value: [innerWidth, innerHeight] } } };
Create event listeners and animations:
const radius = { val: 0.1 }; const radiusAnim = gsap.from(radius, { val: 0, duration: 0.3, paused: true, onUpdate: updateRadius }); function updateRadius() { planes.forEach((plane, i) => { plane.uniforms.radius.value = radius.val; }); } // ... (mouse event handling code)
Update updateProgress
to keep WebGL mouse synced.
GSAP's callbacks (like onComplete
) and frame-rate independence are advantageous.
Further Enhancements
Add effects like turbulence and displacement. Displacement involves moving pixels based on a gradient lightmap. Animate displacement power and intensity based on drag velocity. Curtains also offers a React version. Share your creations!
The above is the detailed content of Creating WebGL Effects with CurtainsJS. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
