Archive for the ‘Tools’ Category

Rich Manalang

Introducing the new GitHub for HipChat add-on

By Rich Manalang | 8 months ago | 7 Comments

Several months ago, we introduced a new way to integrate with Bitbucket using HipChat API v2’s Add-on capabilities. And although it took a while, today we’re announcing the new GitHub for HipChat Add-on. We’re using the same v2 API behind our Bitbucket integration to power our new GitHub for HipChat add-on.

The new GitHub for HipChat add-on makes it easy to pipe in all of your GitHub notifications into one or more HipChat rooms, using GitHub’s rich set of webhooks. You can set up notifications for all of the events you see below:

You can subscribe any room to as many repositories as you want and tailor the events for each room and repository. After it’s all configured, your notifications will look like this:

Ready to try it out? Find the new GitHub for HipChat add-on in your admin console. Find your room configuration screen, select the room you want to add this to, then click on the Add-on link on the sidebar. You’ll see the GitHub add-on in the “Find new” tab.

The new GitHub add-on for HipChat brings important information about your dev process right into HipChat. So what are you waiting for? Go set it up!



Elena Gorman

HipChat + PagerDuty for real-time DevOps collaboration

By Elena Gorman | 1 year ago | 0 Comments

Like many agile development teams, we rely on PagerDuty to monitor and respond to DevOps incidents. We use each other’s tools every day, so we’re excited that they now support incident-based webhooks for all users. It’s only natural that we teamed up with them for their first webhook-based integration.

Web-hooks based notifications from PagerDuty in HipChat

PagerDuty now integrates with HipChat using webhooks for real-time DevOps collaboration

Thanks to this integration, our users receive notifications from PagerDuty (like triggers, acknowledgements, resolves, assigns and escalations) in a HipChat room.

Since HipChat launched with native Android and iOS clients, that means you can monitor PagerDuty alerts even when you aren’t near your desk.

Alex Solomon, CEO of PagerDuty, says “this integration is easy to set-up and highly customizable, allowing users to receive updates where they get their work done.” On our end, we like how fast it was to set up and we’re excited to see the added functionality it brings to our community.

Integrate PagerDuty into HipChat by following the guide here.

Garret Heaton

XCode tips for TextMate users

By Garret Heaton | 4 years ago | 0 Comments

Switching from TextMate to XCode to work on the upcoming HipChat iPhone app has been a little painful. TextMate has some incredibly helpful features that I feel very unproductive without. Luckily some of them can be enabled or emulated. Here’s what we’ve found:

Go to File (Command-T)

TextMate's Go to File popup - so awesome!

The Go to File popup is probably TextMate’s most beloved feature. After using it for a while it seems amazing that its not part of every IDE out there. XCode’s “Open quickly” (Command-Shift-D) doesn’t cut it because it doesn’t do partial matching on the filename.

There are two options (both paid tools) for adding this functionality to XCode:

  1. PeepOpen — $12, beta software, great potential but not actively maintained
  2. Code Pilot — $30, more mature and full of other nice features

If you want to bind either tool to Command-T you’ll need to unbind XCode’s default key binding for the “Show Fonts” dialog first. To do that, open your XCode preferences and clear out option shown here.

Key Bindings

The “Delete line” (Control-K) and “Duplicate line” (Control-Shift-D) shortcuts can be added system wide by placing the following in ~/Library/KeyBindings/PBKeyBinding.dict:

    "^$K" = (
    "^$D" = (

Full details and other options are available in this Stack Overflow post.


TextMate's Twilight theme in XCode

Using the same theme in all your IDEs can make it a lot easier to jump between them seamlessly. Here’s a tool you can use to convert your existing TextMate theme to work in XCode: XThemes.

There’s also a downloadable version of the Twilight theme for XCode here.


Unfortunately there’s no way to get a tab-based display in XCode, so you’ll have to get good at switching between files using your Command-T replacement or via one of the suggestions here.

We hope these tips can make you a little more productive in XCode. If you’re looking for more make sure you check out this Stack Overflow thread. Oh and keep an eye out for the HipChat iPhone app.

Pete Curley

How Adobe ruined Fireworks CS4/CS5

By Pete Curley | 4 years ago | 11 Comments

Adobe Fireworks is my secret weapon as a web-designer. It has the power of Photoshop but sports an interface and tool-set geared towards rapidly creating multiple versions of pixel-perfect mockups. Two of my favorite features: “Pages” where I can quickly create different versions in one file, and “Styles” where I can save our styles (buttons, dropdowns, etc.) and re-use them over and over again. I still do my finished pixels in Photoshop but the layout, margins, and typesetting is all Fireworks.

I’m a stickler for mockups that look EXACTLY how they will look in the browser. We like working off of pixel-perfect mockups when implementing new features. I don’t waste time making complicated specs and they don’t have to question what they’re building. The new versions of Fireworks (CS4/CS5) have made this impossible to do.

Why Fireworks CS3 is awesome

Fireworks has several text alias options. The one I always choose is “System Anti-Alias.” This will render fonts exactly how that font will look in a web browser.

Font rendering in Fireworks CS3

Font rendering in Fireworks CS3

Why Fireworks CS4 and CS5 are not awesome

When Adobe released Adobe CS4 I was shocked to see that when they updated the text engine, they removed the System Anti-Alias option. It is now actually impossible to get your mockups to duplicate browser text. For me, this was a clear deal-breaker.

Font rendering in Fireworks CS4/CS5

Font rendering in Fireworks CS4/CS5

Here are all of the alias options that Fireworks CS4/CS5 have:

All the font options in CS4 and CS5

All the font options in CS4 and CS5

It’s too bad, because Adobe has updated Fireworks CS4 and CS5 to be faster and more stable. The hardest part now is finding places to acquire Fireworks CS3 legally.

Garret Heaton

How HipChat works: SMS chat with Twilio

By Garret Heaton | 5 years ago | 10 Comments

Earlier this week we released a mobile alerts feature allowing users to hook up their cell phones and participate in one-on-one chats while away from the computer. Having SMS support is important to us because just about everyone has a cell phone but not necessarily a smart phone capable of running our web chat. Adding SMS support turned out to be quite simple thanks to Twilio. Here’s why:

1. Cost – At first we thought we’d have to use short codes to send our messages. They’re the 5 or 6 digit numbers you can text vote on American Idol, get crappy ringtones, etc. Unfortunately they’re about $500/mo each (and some companies will charge you much more). We also looked at using a shared short code but you can’t do two-way SMS (send and receive) with them. Twilio lets you use local numbers for $1/mo that can send up to 1 message per second. This means we can just add more numbers as our volume increases. Finally, each message (in or out) is just $0.03.

2. Setup speed – It takes about 90 days and a bunch of approvals to get a short code, probably because you can use them to charge people monthly fees. Allocating a local number on Twilio takes about 15 seconds (even less if you do it through their API).

3. Two-way messaging – We need to be told about replies to the messages we send so mobile users can actually have conversations. We also need to use a different phone number for each chat session you have so that we know who you’re replying to (that’s where the short codes get really expensive). Twilio will hit a URL we provide with information about each incoming SMS so we can deliver them to the right person.

Note: If you’re just doing low-volume one-way messaging you can probably get away with email-to-SMS gateways.

4. Clean API – Twilio’s REST API is easy to use, and has a PHP library available. We just wish they had JSON support. By the way, we’re getting really close to releasing our own API!

5. Good support – They were far more helpful and responsive than other SMS gateway providers. We had the feature built and working in about 2 days.

We hope everyone enjoys the new SMS chat feature and that some of you will have the pleasure of adding SMS (or voice) support to your own app.