New Features Today

Published in: API, Development, NewsPosted by Tyler on 07/05/06

I pushed out a new version of Snipplr early this morning. There are a lot of improvements – both above and under the hood. In deciding what to work on over the holiday weekend, I picked out the best suggestions from all the emails I’ve received and combined that list with my own bug fixes.

New Languages

\n\n* AppleScript * Lisp * SVN * XML

New Features

\n\n* You can add your location to your profile. * You can add your website to your profile. * Each user can now pick which language tabs they want to appear throughout the site. This allows me to keep the list short and prevent wrapping as often as possible. * Snipplr’s layout has been change a little, too. The tag cloud was beginning to take up too much room on the page, so I’ve moved it to the side bar (and increased the width of the sidebar).

Update: Added an option to specify the number of snippets per page. (Thanks, Luis!) Also, I recorded a short screencast showing how to drag the language tabs for people who are having problems.


\n\n* The back and forth paging links are now located at the top and bottom of the page. * Lots of internal bug fixes.

Coming Soon

\n\nHere’s what I’m working on currently and plan to roll out this weekend.

  • Code comments. Let users leave comments on other people’s snippets.
  • Snippet ratings. Users can rate snippets 1 – 5 to help others find the best ones quickly.
  • Revamped RSS feeds allowing you to make a feed from any page. This will let you subscribe to individual tags. (Another much requested feature.)
  • Releasing an “official” Snipplr API using XMl-RPC. Right now the TextMate bundle communicates using a simple GET/POST query. I hope having a documented API will encourage developers to write plugins for BBEdit, Vim, Emacs, and all the other text editors out there.
  • I’m also toying with the idea of classifying snippets based on spoken language. So people who only speak English can ignore all the Spanish snippets and vice-versa. Thoughts?

Again, as always, please let me know of any bugs you find or suggestions you have. You can leave your comments below or contact me here.


RSS Icon Subscribe to comments
Posted By: George on July 10th, 2006

Tyler, I was wondering if you are planning on implementing a line-by-line comminting feature (kind of like Flickr allows you to attach a comment to a random region of the image). This will enable public code reviews of sorts. And for an even more advanced piece of functionality, how about a version-controlled snippets?

Posted By: Tyler on July 10th, 2006

Ooo, attaching comments to specific lines is a very cool idea. I was planning on adding comments in general, but targeting them to lines numbers offers some neat possibilities.

Version controlled snippets have been available since day one (sort of). When you view a snippet, on the right hand side of the page there is a drop down menu listing all the snippet’s previous versions. You can view any revision by choosing it from the list.

This probably brings up the question, how do you create a new version of a snippet? Simple. Just edit the snippet. When you save your changes, Snipplr will automatically save the new version and archive the old one.

Posted By: George on July 10th, 2006

I haven’t noticed the version drop down – very cool! Now, how about a diff view? 🙂

Posted By: Tyler on July 10th, 2006

Is that a challenge? 😉

Posted By: iLuke on July 18th, 2006

Have you considered adding a “public” and “private” section of the code? I have some code that I would rather not store in the open. It would be nice to be able to label some of my code as “private” and know that it is only accessible by me.

Just a thought, though 🙂
Great work, Tyler.

After my sister’s wedding this week, I’ll be whipping up a widget for OS X 10.4 users.

Posted By: Tyler on July 18th, 2006

Awesome. Can’t wait for the widget.

Public / private snippets are on the way. They’re not at the top of my todo list, but they’ll be added before too long.

Leave a Reply

You may use Markdown to format your comment.
HTML renders as source code.