Skip to main content

How To Write Your First Jetpack Extension

I've been meaning to this for months, and I just kept putting it off. So many other things going on, so I didn't think I had the time. I decided to take a look this morning, finally, and put in the energy required to try this cool looking stuff out.

Took me ten minutes.

If you don't care about writing a Jetpack extension, but you have Jetpack installed, you might want to try out what I wrote. "Twitter, Who Am I?" is the name and making your currently-logged-in user at twitter.com obvious is the game. You'll get a nice label above all the pages, so you don't accidentally follow Ashton Kutcher with your business account.

The tutorial is fantastic, so I'm not going to try and rewrite or replace it, but I do want to make some comments about the process of getting into this. Firstly, the tutorial on the website is the same as that in the about page, but crippled. Same text, no interactive features. The tutorial built into Jetpack lets you edit and try out the samples, and the website uses the identical text without those features. It still tells you to push the install button, which doesn't exist. Use the about page.

It isn't obvious enough from the website how to get started. You can get to the tutorial and documentation, but none of it makes it obvious what to do with the stuff when you write it. The documentation for actually installing and distributing seems hidden. Again, the about page comes to the rescue. I'm going to assume they expect you to install Jetpack, get the about page up after the restart, and look at that stuff right away. If you don't, you're going to get lost.

Go to the about page and click the "Develop" tab. This will give you the install and deploy overview, as well as an editor you can test code from without installing the jetpack permanently.

I don't know if anything will come of it, but I created a subreddit for any interested parties.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad. Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems. There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day. The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad. You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You u