It would have been a more structured source list than in previous versions.) (It would also have had separate sections for smart feeds and scripted feeds. Remember that this was 2011, and Google Reader was all most people thought of when they thought of RSS readers. Taking a cue from Mail, it would have had zero or more top-level âGoogle Reader (account name)â folders and one âOn My Macâ folder. I should describe the planned source list change. The app would have handled Google Reader and stand-alone feeds itself â but a developer would have been able to add additional types of accounts. And if you needed to do more, you could.) Account Type Plugins Enough was given to you for free that you didnât have to do much more than configuration plus an http call. I could ship a sharing plugin that wouldnât be included in the standard release, or ship one that could be included later. It also would have allowed me to ship plugins outside the normal release process. With the explosion of new places to send your content (Twitter, Pinboard, Pocket, and on and on) I realized it would be difficult to keep up and cover everything.Ī sharing plugin allowed you to create a user interface (if needed) and to send a URL and text wherever you wanted. And theyâd use protocols, so the plugins wouldnât have had to link to anything. They would all have had Objective-C APIs. I got pretty far along in defining some of the plugin types, to the extent that the app was using the plugin API under-the-hood.īelow are the types I was considering. This was especially true with themes â because theyâre fun to make and fun to try out.įor NetNewsWire 4.0 I wanted to take this to the next level and provide additional ways to extend the app. This meant more publicity for the app and it meant people could easily find these extensions that helped them get more out of the app. People liked to publish their scripts and themes. They were out of the way of the average user, and added a bunch of value for power users.Īlong the way I discovered that there was a marketing benefit too. Since NetNewsWire was a productivity-style RSS reader rather than a casual reader, it made sense to add these kinds of features. Not everybody used them, but the people who did use them really liked them. Create scripted feeds (using AppleScript, Ruby, Python, etc.).Create custom themes (with HTML, CSS, and JavaScript).There were already some things developers could do: The idea was pretty simple: make NetNewsWire extendible by other developers. And Black Pixelâs plans are most likely different from my plans, which is expected and totally a-okay.Īside from general modernization and performance and memory use enhancements, my big plan was plugins. The next step would have been the full (non-Lite) 4.0 for Macintosh, but we sold NetNewsWire to Black Pixel. The last version of NetNewsWire I shipped was NetNewsWire Lite 4.0 for Macintosh. This was a long time ago, and it wasnât necessarily the best plan â but it was the plan.
0 Comments
Leave a Reply. |