Use Growl to allow notifications in DMDirc on OS X

100%

Use Growl to allow notifications in DMDirc on OS X

✓ Published0🌍 Public

Last edited Dec 21, 2012

Created on Dec 21, 2012

This example shows how DMDirc, an IRC client, can send desktop notifications on macOS when a channel message mentions the user’s nickname. It uses DMDirc’s redirect and exec plugins to invoke the `growlnotify` command-line tool from the Growl notification framework. A trigger on `CHANNEL_MESSAGE` routes the message text through a response that runs `/usr/local/bin/growlnotify` with the sender name, channel, and message content. A condition tree filters messages using a `STRING_CONTAINS` comparison against `$SERVER_MYNICKNAME`, ensuring only relevant messages trigger the notification.

AI-generated description

Similar vizzes

Loading thumbnail…

Create a notification within a sketch plugin

This example shows how a Sketch plugin can display a native macOS notification to the user. The code creates a new `NSUserNotification`, assigns it a unique identifier, and sets its title, subtitle, and informative text. It then retrieves the default notification center and delivers the notification. The data is hard-coded strings, and the implementation relies on the Sketch plugin API’s `NSUserNotificationCenter` and `NSUserNotification` classes.

KKevinGutowski

51% match

Loading thumbnail…

open Adium from Albert

This example demonstrates how to trigger a chat in Adium from the Albert launcher using an AppleScript. It shows a workflow where a user types a contact name into Albert, which then passes that query as a command-line argument to an `osascript` call. The script activates the Adium application, searches for a contact whose display name contains the provided text, and opens a new chat window with that contact, falling back to an error dialog if the user is not found. The code uses the Adium scripting dictionary and Albert’s `{query}` placeholder, highlighting integration between a system-wide launcher and a messaging app.

TTBD

49% match

Loading thumbnail…

Gist d8d02005e92053aa5eac546ddd0b170d

This example demonstrates a Minecraft plugin that broadcasts a greeting to all online players. The code defines a `mindControl` function that retrieves the list of online players via the Bukkit `getOnlinePlayers()` method, then iterates through the player list to send each player a chat message saying "Hi" using the `chat()` method. It also uses `magik.dixit(server)` to display a server-side message. The visualization highlights the plugin’s event-driven structure and its use of the MagikCraft API, specifically the `magikcraft.io` library, to interact with the game server.

44xDMG

47% match

Loading thumbnail…

ducksboard

This example demonstrates a lightweight workflow for sending real-time data to a Ducksboard dashboard. It constructs a JSON payload containing a timestamp and a message object, then uses the `msg.http` request API to POST that data to a specific Ducksboard value endpoint. The code authenticates with an API key and displays the server's response, showing how to push a simple message to a live dashboard widget. The example relies on the Ducksboard HTTP push API and the `msg` library for making the HTTP request.

TTBD

46% match

Loading thumbnail…

Gist 660bf021ec250dfb10016d384d524bd7

This example shows a real-time chat application where users exchange messages through a Node.js server. The visualization tracks message flow and user activity using a force-directed graph rendered with D3.js’s `d3.forceSimulation` for node positioning and link physics. Each user appears as a node, with edges connecting them to messages they send, while color and size encode online status and message frequency. The code uses Socket.IO for live data updates and D3’s `transition.attrTween` to animate new nodes and links smoothly as events arrive, making the conversation pattern immediately visible.

FFrankieFabuloso

45% match

Loading thumbnail…

requirebin sketch

This example demonstrates a simple event-driven messaging system using the Barracks library. It shows how multiple listeners can respond to the same named event, with two separate handlers writing personalized greetings to the document. The code creates a dispatcher instance, registers two 'hello' listeners, and triggers the event with the name 'Loki'. The visualization highlights the sequence of output generated by both listeners when the event fires.

HHypercubed

44% match

Loading thumbnail…

Reminder for signing Git commits

This example visualizes a reminder system for signing Git commits, showing how a terminal-based script triggers a notification workflow. It uses the `tty.bash` script, which exports `GPG_TTY` to ensure GPG signing works correctly in interactive terminal sessions. The visualization captures the command-line environment where the script runs, highlighting the integration between shell configuration and Git’s commit-signing process. The rendering relies on standard Bash syntax and environment variable handling, with no external data sources or graphical libraries—it presents a purely code-driven scenario focused on developer tooling.

CCliffordAnderson

43% match

Loading thumbnail…

Gist 10794

This example demonstrates a GitHub repository interaction system built with Ruby and the GNCommand event framework, showing how drag-and-drop actions on repository URLs trigger context-specific behaviors. The visualization highlights the branching logic that detects whether a dropped URL points to a repository, a tree, or a commit, with placeholder sections for handling forks, files, and users. The code uses the GNCommand API’s `:drop` event scoped to `github.com` and parses URL path components via `path.pathComponents`. While the rendering approach is not visible, the focus lies on the event-driven decision tree that maps URL structures to potential GitHub actions.

CCaged

43% match