{"id":943,"date":"2021-09-22T12:23:31","date_gmt":"2021-09-22T12:23:31","guid":{"rendered":"https:\/\/www.practicallynetworked.com\/?page_id=943"},"modified":"2021-10-05T16:59:22","modified_gmt":"2021-10-05T16:59:22","slug":"practical-mac-networking","status":"publish","type":"post","link":"https:\/\/www.practicallynetworked.com\/practical-mac-networking\/","title":{"rendered":"Practical Mac Networking: Growl Makes Your Mac Chatty"},"content":{"rendered":"

If you’re looking for a simple, flexible way to make sure you know about what’s going on with one computer from the comfort of another, Growl 1.1 might be for you.<\/b><\/p>\n

\"\"<\/p>\n

I like to know what’s going on in my digital world. It’s a habit I picked up when I was managing a cranky networked app for a high school, and I’ve never lost it. Outage notifications were always better when they came from a script rather than from an irate teacher who’d just lost her network connection halfway through sixth period attendance.<\/p>\n

These days, I don’t have irate teachers to deal with: Just the family LAN and a few hosted domains I share with several guests. I’d still rather know something’s wrong from a fairly dispassionate automated notification; and if I can get notifications for less important things I’m happy about that, too.<\/p>\n

Late last week\u00a0the Growl project<\/a>\u00a0announced Growl 1.1, a revamped notification framework for Macs. If you’re looking for a simple, flexible way to make sure you know about what’s going on with one computer from the comfort of another, Growl might be for you. If you’re running services on a platform besides the Mac and can run scripting languages like Perl or Python, you can signal Macs listening for Growl notifications over the network.<\/p>\n\n\n\n
\n
What’s That Term?<\/strong><\/span><\/div>\n

Not sure what a particular term means? Check out the searchable\u00a0PracticallyNetworked Glossary<\/a>.<\/b><\/span><\/b><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

\"\"<\/p>\n

Growl provides the pieces applications need to send graphical alerts to a Mac display. There are a number of Mac apps that talk to Growl<\/a>, including assorted mail clients, Web browsers, download programs, timers and more. Each includes a list of possible notification topics specific to the application: received mail, completed downloads, alarms, buddies signing on and off IM and a lot more.<\/p>\n

By way of an example, let’s look at Transmit, an FTP client I\u00a0reviewed last year<\/a>. Transmit includes some handy features for doing backups and folder synchronization over the Internet. A folder sync, for instance, guarantees that the stuff in a directory sitting on a remote server matches the contents of a local directory.<\/p>\n

\"\"<\/p>\n

As the screenshot in Figure 1 shows, Transmit offers three notification events for Growl: completed downloads, completed uploads and completed synchronizations. Each of those events can trigger a Growl alert, causing an alert to pop up on the user’s display, as in Figure 2.<\/p>\n

As a simple notifier system, Growl’s handy for a number of reasons: It standardizes the sorts of alerts you receive in terms of how they look and where they appear. You can customize where they appear and how long they stay on the screen and whether they’re accompanied by sound. The number of display styles make it easy to create visual cues for how important an incoming alert is. With Growl acting as a broker for all your notifications, you can avoid a clutter of windows competing for your attention since Growl neatly stacks its alerts for you.<\/p>\n

Over the Network<\/h3>\n

\"\"<\/p>\n

Alerts local to the computer you’re working on are only part of the Growl picture, though. It also includes network functionality that makes it possible to send and receive notifications for applications running on another computer. Out of the box, it works with computers on the local network, as shown in Figure 3.<\/p>\n

The computer “ornithopter” in that screenshot is a local laptop. When Growl displays a notification on my desktop system, it also sends a notification to the laptop. The laptop is also set to send notifications to the desktop system.<\/p>\n

That network functionality is useful for a number of purposes: Chat and voice apps such as Skype and Adium send Growl alerts, so there’s no need to juggle multiple clients between laptop and desktop if you move between machines much. If you start a long backup on one machine using Transmit, it can send a notification to a second machine when the backup’s done.<\/p>\n

Growl has also been extended to work with common scripting languages such as the\u00a0Mac::Growl Perl interface<\/a>\u00a0and Python’s\u00a0GrowlNotifier class<\/a>. So any platform that can run these languages (as well as Java, Ruby, Tcl or even PHP) can send Growl notifications.<\/p>\n

Support for these languages is available via the Growl SDK, which you can download from\u00a0the Growl developer pages<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

If you’re looking for a simple, flexible way to make sure you know about what’s going on with one computer from the comfort of another, Growl 1.1 might be for you. I like to know what’s going on in my digital world. It’s a habit I picked up when I was managing a cranky networked app for a high school, and I’ve never lost it. Outage notifications were always better when they came from a script rather than from an irate teacher who’d just lost her network connection halfway through sixth period attendance. These days, I don’t have irate teachers <\/p>\n","protected":false},"author":2,"featured_media":5596,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/943"}],"collection":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/comments?post=943"}],"version-history":[{"count":0,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/943\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media\/5596"}],"wp:attachment":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media?parent=943"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/categories?post=943"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/tags?post=943"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}