An Atom package that scans and displays colors in your project files, supporting CSS pre-processors like Sass, Less, and Stylus.
Pigments is an Atom editor package that scans source files in a project to identify and visually display colors. It builds a palette of all colors used, highlights them directly in the code, and supports color conversion and search functionalities. It solves the problem of managing and visualizing color schemes across large projects, especially those using CSS pre-processors.
Web developers and designers using the Atom editor who work with CSS, Sass, Less, or Stylus and need to visualize and manage colors within their codebase efficiently.
Developers choose Pigments for its deep integration with Atom, robust support for major CSS pre-processors, and powerful features like project-wide color search and palette building. Its customizable highlighting and conversion tools streamline color management without leaving the editor.
An Atom package to display colors in project and files.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports multiple render modes like background, outline, and dot for inline previews, with customizable scopes to target specific file types or exclude comments via regex.
Builds a searchable palette of all color variables across the project, accessible via command palette, making it easy to visualize and manage color schemes.
Handles variables and transformation functions from Sass, Less, and Stylus, as noted in the parser specs, supporting common web development workflows.
Allows conversion between HEX, RGB, RGBA, HSL, and HSLA notations directly from the editor or command palette, with customizable keybindings for efficiency.
Prioritizes broad compatibility over parsing complex language constructs, so it may fail to evaluate advanced pre-processor expressions, as admitted in the README.
The creator has been inactive for months, and the project relies on community contributions, leading to potential unresolved bugs or compatibility issues with newer Atom versions.
Scanning large projects can be resource-intensive, with a configurable delay to mitigate impact, but this may still cause lag in extensive codebases.