For Developers: More on 3.0

I just wanted to give an update to developers about the current status of 3.0. As I've began the coding process and started to think about the actual implementation of new features, I've decided that it will be more and more practical to create an API specifically for Clip and Share. You can get a preview of what the API looks like and how it will work by finding the API Reference page in the wiki. (It hasn't been posted to the front page of the wiki yet because it's still not even a complete rough draft of what things will be like!)

The addition of an API framework to Clip and Share will hold several advantages and will allow for more focused, quality development in future iterations of the software. Here are just a few of the advantages:

• It will be much easier for even advanced end-users to add their own functionality to the extension. If someone wants to add a simple feature such as support for a new network, just a basic knowledge of JavaScript and a glance over the API reference will help them get things accomplished.
• Development of features can be more consistent across the board. Rather than running a different chunk of JavaScript code for each supported network, one chunk of code can handle ever object fed to it in the same manner. This will greatly simplify and expedite the development process.
• Having an API prevents developers from having to learn the entire codebase just to add a simple feature.
• This new codebase will allow for different types of developers to focus on different things. People who are more interested in changing the core functionality of the software can focus on making changes directly to the API.js file while others may wish to focus on building on top of the existing API. In other words, there will now be a means for doing both high- and low-level development on the software.

Unfortunately, the development of the API will take a little more time, so don't expect the 3.0 release for at least a couple more weeks. I want to make sure that I implement this API properly and will be taking everything into consideration as I do so!

I'm excited about making this software more open source friendly and gradually opening up the possibilities for what future versions will be able to do!

Jordan Meyer, Project Manager