One of the features that has always been planned for MagicBrush-Photo has been the ability to upload or publish images to Picasa and Flickr.
Right now I'm in the midst of incorporating this feature into the release plan. The GData APIs for cocoa are making this straight forward enough, but the tricky part is making the experience fit in with the overall Mac user expectation.
For instance, a user has a reasonable expectation of being able to store their account information for Picasa or Flickr in their keychain.
Once you can authenticate to either site, you need to present the complex behavior of the web application in a simplified manner. Should users be able to only upload? Should they be able to view previously uploaded images (to ensure they're not duplicating things)? Should they be able to edit tags and descriptions for images already uploaded, or just when they initially upload them? Complexity grows quickly.
Stay tuned to see how MagicBrush-Photo handles these. If you are interested in helping beta test these features, give me a shout.
Saturday, April 12, 2008
Wednesday, April 09, 2008
Moving Toward 1.2
MagicBrush-Photo was stalled slightly at version 1.1.5. I knew what I wanted to add by way of features, and had a development branch working, but unfortunately my "paying job" was consuming more of my time and energy than I planned.
I should probably caveat that I'm not your typical programmer (at least I like to think I'm not). I've got a full-time non-programming management job at a fortune 500 company within the IT organization. For the past year I've been loaned out on a special project team doing a bunch of neat things within a couple of our markets. I've run the gamut from launching new products and services to implementing different business model pilots and a slew of other cool things.
It's been fun (mostly), and a lot of hard work.
But it has seriously diminished my free time to program and enhance my software. At the same time, Leopard has been released, and the niche I had targeted is beginning to transform into a very competitive landscape. It would be easy to back off and let MagicBrush-Photo languish.
But that's not what I want to do.
1. I like to solve interesting problems.
2. I like to have control of how I work.
3. I like the Macintosh platform.
4. I like the idea of "not working for the man".
5. I like being able to keep my coding skills fresh.
While my morale regarding GreenWave Software was a little down early in the year, I've found it helps to remember why I enjoy programming in the first place. I don't get to use this set of skills much at work (and frankly don't think I would enjoy it if I had to code in a corporate environment).
When I stop and think about these reasons, I find I am more focused on moving the needle with MagicBrush-Photo and a few other projects I have in the hopper.
An Aside
I should probably caveat that I'm not your typical programmer (at least I like to think I'm not). I've got a full-time non-programming management job at a fortune 500 company within the IT organization. For the past year I've been loaned out on a special project team doing a bunch of neat things within a couple of our markets. I've run the gamut from launching new products and services to implementing different business model pilots and a slew of other cool things.
It's been fun (mostly), and a lot of hard work.
But it has seriously diminished my free time to program and enhance my software. At the same time, Leopard has been released, and the niche I had targeted is beginning to transform into a very competitive landscape. It would be easy to back off and let MagicBrush-Photo languish.
But that's not what I want to do.
Why I Program
1. I like to solve interesting problems.
2. I like to have control of how I work.
3. I like the Macintosh platform.
4. I like the idea of "not working for the man".
5. I like being able to keep my coding skills fresh.
While my morale regarding GreenWave Software was a little down early in the year, I've found it helps to remember why I enjoy programming in the first place. I don't get to use this set of skills much at work (and frankly don't think I would enjoy it if I had to code in a corporate environment).
When I stop and think about these reasons, I find I am more focused on moving the needle with MagicBrush-Photo and a few other projects I have in the hopper.
Now, back to coding ;-)
Wednesday, January 23, 2008
Software Concepts
I've been in a little rut lately, with insufficient time to make major changes to MagicBrush-Photo, though I believe that will change soon.
At the moment, driving to and from my paying job is about the only time I seem to have to think about the programming. I've got a few new features to implement in MagicBrush-Photo, but I've also got a couple of simple project ideas I'm kicking around.
Here for posterity (and any comments) they are:
At the moment, driving to and from my paying job is about the only time I seem to have to think about the programming. I've got a few new features to implement in MagicBrush-Photo, but I've also got a couple of simple project ideas I'm kicking around.
Here for posterity (and any comments) they are:
- A better syncing tool to keep my iTunes libraries in synch across multiple machines and user accounts. On our home machine, my wife and son have their own iTunes accounts, we have a back-up of the library on another shared drive, and I use one (or two) laptops for most of my music purchasing. Keeping everything in synch is a pain. I've looked at various solutions from rsync to Unison to Slingshot, but not been really happy. What I'd like is:
- an easy method to identify differences between directories (music or otherwise)
- The ability to synch those two directories at a file level (I don't need file diff capability)
- A clean UI for managing these tasks
- The ability to set up synch rules and run the process via script or timed event
I think I know how to do this, so I might just whip one out as a coding refresher and to get fully up to speed with Objective-C 2.0 - A tool to help create and maintain a SWOT analysis. This is definitely a niche need, but I think it could be pretty cool if done right. God knows I'd love to have such a tool in my daily job. My ideal solution would force the user to iterate over their Strengths, Weaknesses, Opportunities, and Threats to clarify their thinking as well as document the action plans that emerge from a true SWOT analysis. Think of it as GTD for business planning.
Subscribe to:
Posts (Atom)