Gist b920d015b95bc608e2f5

100%

Gist b920d015b95bc608e2f5

✓ Published0🌍 Public

Last edited Jul 24, 2014

Created on Jul 24, 2014

The example shows two Homebrew formula definitions, `flash_player.rb` and `flex_sdk.rb`, that install Adobe Flash Player Debugger and Adobe Flex SDK respectively. The code uses the Ruby `Formula` class from Homebrew to specify download URLs, SHA1 checksums, and homepage metadata for each package. Both formulas define an `install` method that copies downloaded files into the Homebrew prefix and, for Flash Player, creates a symbolic link to `/Applications`. The Flex SDK formula also prints terminal instructions for adding the SDK to the user’s `PATH` using the `ohai` command.

AI-generated description

Similar vizzes

Loading thumbnail…

SSH Brew Setup

This example visualizes the SSHpass formula setup process, showing the sequence of build and installation steps for a Homebrew package. The visualization uses a direct graph representation, where nodes correspond to the formula’s Ruby methods (`install`, `test`, and the implicit `require`), and edges depict the control flow from the formula class definition to the system commands. The data source is the Ruby source file `sshpass.rb`, which contains the formula’s URL, SHA256 checksum, and custom build logic. The rendering relies on a custom layout algorithm, likely using D3’s force simulation to position nodes and SVG paths for the edges, highlighting the dependency between the configuration script and the `make install` step.

AAnsonT

64% match

Loading thumbnail…

Brew script for installing packages and applications on OSX

This visualization uses a horizontal bar chart to summarize the categories and counts of software packages installed via a Homebrew shell script. The chart encodes each tool’s install command type (e.g., `brew install` vs. `brew install --cask`) using color, with bars grouped by functional category like programming languages, dev tools, and communication apps. Data is derived directly from the script’s parsed `echo` section headers and package lines, rendered using D3.js for scalable vector graphics (SVG) layout and axis generation, while hover interactions reveal exact package names. The underlying data source is the public GitHub gist by CliffordAnderson, with the script logic illustrating dependency-free package management on macOS.

CCliffordAnderson

59% match

Loading thumbnail…

Gist 785d5d6a4bd9ed9227e9477a432b092f

This example shows a shell script that automates building dynamic XCFrameworks for WebRTC-based libraries across multiple Apple platforms, including tvOS, visionOS (xrOS), and Mac Catalyst. It demonstrates how to configure builds for device and simulator targets using GN and Ninja, with settings like `rtc_objc_prefix = "LK"`, deployment targets, and enabled codecs like libaom and dav1d. The script generates platform-specific framework bundles by invoking `gn gen` with different `target_environment` values, then runs `ninja` to compile each variant. It also toggles debug symbols and stripping based on the input mode, highlighting a structured approach to cross-compiling and packaging iOS-family frameworks.

AAgoujil2saad

55% match

Loading thumbnail…

TV News Workstations

This example shows the software stack a TV newsroom installs on a new Mac workstation, listing programming languages, development tools, and web browsers. The visual layout is generated from a gist by CliffordAnderson, using the Homebrew package manager commands in `brew-install-script.sh` as its data source. Concrete tools named include `brew cask install` for GUI apps, along with `git`, `node`, `r`, `atom`, and `neo4j`. The chart likely maps the script’s text into categorical groupings, though the visualization method itself is not specified in the provided code.

CCliffordAnderson

55% match

Loading thumbnail…

A list of applications and utilities for Library Lab Macs

This example shows a categorized inventory of software for Library Lab Macs, organized by purpose such as programming languages, dev tools, and communication apps. The visualization is generated from a single shell script, which lists the applications and utilities installed via Homebrew, with each category as a segment of the display. Using a force-directed layout of the `d3.forceSimulation` API, the categorical nodes are positioned in a clustered arrangement, while the script’s explicit `brew cask install` and `brew install` commands provide the underlying data. Text labels and category groupings are rendered directly from the script’s comment headers, without any additional data transformation or external source.

CCliffordAnderson

54% match

Loading thumbnail…

Debugging rbtrace under GoogleSketchup

This example visualizes the command-line build and runtime errors encountered while compiling the rbtrace gem for Google SketchUp on macOS. It shows a terminal-style log where a linker warning about an unsupported i386 file format is followed by dyld lazy symbol binding failures for `_msgpack_unpack_next`. The text uses a monospaced font and dark background to mimic console output, with the error lines highlighted in red to draw attention to the root cause.

TTBD

52% match

Loading thumbnail…

Gist 57845

This example demonstrates how to access and manipulate the Xcode application’s scripting interface from Ruby. It uses the ScriptingBridge framework to connect to Xcode via its bundle identifier and create a new group object using the classForScriptingClass method. The code also patches SBElementArray to properly convert its elements to an NSArray, avoiding a known crash. The script then prints the class name of the newly created group, showing the successful instantiation of the scripting object.

CCaged

52% match

Loading thumbnail…

Gist f01d812faefd538a9228175105471468

This example demonstrates the installation of Yarn through the command line, showing the sequence of steps required to add the Yarn repository, update system packages, and verify the installation. The visualization uses a terminal-style interface that displays each shell command as text output, including `curl`, `sudo apt-key add`, `echo`, `tee`, and `sudo apt install`. The code relies on standard terminal rendering in a web page, with no external charting or data libraries, and the source is a plain-text script captured from a Gist.

MMistyBlunch

51% match