0 views collected around this technical thread.
This article explains how to use the onload event to determine when an Img element has finished loading, provides JavaScript examples for sequential loading, discusses why onreadystatechange is unsuitable, and explores when browsers issue image requests and how CSS affects them.
This article introduces JD’s self‑developed HarmonyOS image library, explaining the background, research on existing solutions, the decision to build a C++‑based cross‑platform library, its modular architecture, performance optimizations, quality assurance mechanisms, and future development plans.
This article explains how to enhance image loading in Flutter mobile applications by using placeholders, skeleton screens, error handling, thumbnail generation, and the BlurHash library, providing code examples and practical recommendations for a smoother user experience.
This article examines Flutter's native image loading mechanisms, compares them with Android's traditional image frameworks, discusses the challenges of duplicated resources and memory usage, and details two external‑texture approaches—ShareContext and shared memory—providing code examples and practical recommendations for mobile projects.
The T7 browser kernel’s ResourceScheduler lets developers assign importance=high to IMG tags and CSS background images (as well as JS and link resources), adjusting sub‑resource loading priority so critical images load faster on the first screen, especially when many concurrent requests compete for the same domain.
Baidu's T7 browser kernel introduces a ResourceScheduler tuning mechanism that lets front‑end developers set image loading priority via an importance attribute or CSS property, enabling high‑priority above‑fold images to load faster while low‑priority resources are throttled under heavy domain request competition.
This article provides an in‑depth overview of Glide 4.11, covering its basic usage, the four‑step request lifecycle, six‑step image loading flow, caching mechanisms, initialization, configuration options, and common interview‑style questions for Android developers.
This article explains how Flutter loads and caches images, analyzes the underlying source code of key classes such as PaintingBinding, ImageCache, ImageProvider, and RenderImage, and provides practical techniques for reducing memory usage and preventing OOM in large Flutter applications.
This article provides an in‑depth tutorial on Glide 4.11, covering its basic usage, the four‑step decode task startup, six‑step image loading flow, caching mechanisms, initialization process, and extensive configuration options for Android developers.
This article walks through creating a functional Python clone of the classic Plants vs Zombies game, detailing supported plant and zombie types, level data storage, image resource organization, and the implementation of graphics loading, frame handling, state management, and animation logic using Pygame.
The article dissects Glide’s lifecycle management by tracing how Glide.with creates a singleton RequestManager via RequestManagerRetriever, caches headless RequestManagerFragments, forwards Activity/Fragment callbacks through ActivityFragmentLifecycle to pause, resume, or clear image requests, monitors network changes with a ConnectivityMonitor, and responds to memory pressure via component callbacks, thereby integrating Android component lifecycles, connectivity, and memory management into its image‑loading engine.
This article explains various Flutter image loading techniques—including AssetImage, NetworkImage, FileImage, MemoryImage, CachedNetworkImage, and FadeInImage—provides detailed source code analysis of the Image widget and its underlying classes, and discusses performance considerations and potential optimization strategies.
The article dissects Glide’s five‑level caching system—active resources, memory cache, resource and data disk caches, and network cache—explaining how active weak references feed the LRU memory cache, how DiskCacheStrategy governs transformed and raw data storage, and how I/O and network tasks run on separate executors while network responses are cached before delivery.
The article analyzes an OOM issue in the Beike Android app caused by large image memory usage, compares Picasso and Glide memory footprints, describes the refactoring effort required to switch libraries, explains Glide's two‑level caching mechanism, and highlights the performance and stability benefits for pre‑Android 8.0 devices.
This article examines the internal implementation of the Android Picasso image‑loading library, detailing its singleton initialization, request creation, builder pattern usage, caching mechanisms, delayed loading, and the workflow of actions, handlers, and thread execution to illustrate how images are fetched and displayed.