At least you tried
]]>Until Twitter gets this more stable and I get oauth fully integrated, I can't continue to make Faces.app available.
]]>I built GithubNotifier mostly just to tinker with their API. I leveraged [CocoaREST][2] from Steven Degutis and added support for Github's API as I went. You can check those addtions on my fork here.
There are some caveats though. For starters, the network data API from Github doesn't show what branch a given commit was made to, so if I pushed an update to branch development, the API simply details the commit, but doesn't include which branch. When the Growl notifications are made, a click-back is created so that if a user clicks on the message your default browser will open to user/repo/commits, but if the commit was on a separate branch, you wont see it initially. You may have to look around in the branches to see more details on it.
I have a support request in to Github to include branch and owner information in the commit data returned in the network API call, but they may or may not choose to implement it.
You can checkout or fork the project here, patches are welcome.
]]>
At least you tried
]]>In a future post I'll do a walkthrough of the basic setup, from cloning the repository, setting up the submodules, and getting a working example.
]]>
II'm finally releasing my first app, Faces.app, as a beta. Faces is an OS X desktop application that manages your profile picture across your Twitter account(s). After linking your account, Faces will pull down your current avatar and display it in the grid and from there you can add any image to the grid and upload them to your account(s) with a simple drag and drop.
Faces is a beta application and currently requires OS X 10.6 and an active Twitter account. The app will remain free for the 1.0 cycle and will remain in beta until I get OAuth implemented before the June cutoff for basic auth via Twitter's API.
You can download the latest here (ver 1.0b7). Download temporarily removed due to issues at Twitter with profile images, see this update
Since Matt has created and official source of MGTwitterEngine I feel like it's gained a lot of momentum. There are 8 active forks, feature requests and bugs reports starting to accumulate in the issues list, and over 180 watchers.
]]>In addition I've added a tab to the demo app to show some of these. In it you can view user information by name (SDGithubTaskUserShow) and get a list of repositories (SDGithubTaskGetRepos). The tableview is set run a new task to find forks of the selected repository (SDGithubTaskGetRepoNetwork) on selection change.
The GithubDelegate is kind of a cumbersome class in that it handles all of the task results even though the API returns different results for each task. Ideally I would use a specialized class to delegate for each task, but it's just for demonstration.
]]>To accomplish this I'm extending Steven Degutis's CocoaREST framework to support the Github API in my fork of the project. So far I've got repository listings by username, and showing forks in the network setup. There's a lot more to integrate but I'm not sure how much I want to demo in the UI.
I also added a tab strictly for Github, with the idea being a tab for each API supported, but I haven't dug into any other API beyond Twitter or Github's I'm not sure when those will come. Patches welcome of course.
]]>@rentzsch: yup, I'm sold. Awesome tech+community.
I attended C4[2] back in 2008 where the crew from 280 North gave a presentation on the Cappuccino web framework. I have mixed feelings about Cappuccino, the technology itself seems amazing but it's a big leap from "normal" users web app experience. I plan to spend a weekend with it and try it out for myself.
]]>(1) Not everyone who shits on you is your enemy.
(2) Not everyone who gets you out of shit is your friend.
Selected excerpts from the Five Minute Management Course
]]>]]>"The question isn't who is going to let me; it's who is going to stop me." ~ Ayn Rand
First, the Droid is not near a bulky and ugly as the pictures I had seen lead me to believe. For whatever reasons I thought it was larger and thicker, but it was really quite nice.
Secondly, I've never seen such a responsive Android phone; in my experiences with the G1 and a recent HTC I was not impressed with the lag/sluggishness, but the Droid seemed spot on.
It’s great to see a good implementation of Android. I haven’t heard how the Google Nexus One is, but I have high hopes for Android being a good competitor to the iPhone and iPhone OS. Competition will (hopefully) make both stronger.
]]>there's practically no human emotion with Google when it comes to technology. Everything is statistical and analytical. While you could argue that being this way is way superior to "feeling" and "emotion"- it might be 95% of the time -- you still will almost always lose that charm and that amazing feeling of connecting to something.
This sums up my feelings about a lot of products when compared to Apple. If you've met me, you may know I have a thing for Apple products, and it's not because I'm a blind fan-boy, instead it's because their products are easy to make a emotional connection to. There's a lot of thought, hard work and love put into most of them, and it's easy for me to make a human connection to them.
]]>