Yes, the "cloud". I hate that buzzword. I see it everywhere, and seemingly every day I see tech articles and tweets extolling its virtues, heralding it as the next big thing - a means to trade being tethered to a general-purpose computer at a desk for being tethered to a faceless corporation's ecosystem, accessed through whatever locked-down devices they see it fit to support.
Of course, as with anything that takes control and privacy away from users, there is backlash. _Tonight at 11: are your Facebook photos really private? The truth may surprise you._ Next thing you know you have parents making their children wear infrared LED hats to birthday parties. In order to capitalize on this panic some services have started advertising themselves as an alternative to cloud storage. Not all of them, however, understand what "cloud" storage means.
Like this recent email from my credit union (emphasis mine)...
Introducing My Virtual StrongBox® – our New Online Safe Deposit Box Service!
My Virtual StrongBox allows you to safely store copies of critical documents such as birth certificates, insurance policies, wills and more online, without having to rely on the "cloud."
With My Virtual StrongBox, you have immediate access to your documents – where and when you need them – with the assurance that they are stored on the same dedicated secure devices where we keep your eStatements and other financial information. Plus, as a Northwest Federal eStatement user, you have access to 100MB of document storage at no charge.
Start safely storing and organizing your important documents. Login to your eStatements directly or through Online Banking, to create your own My Virtual StrongBox today.
So, I've been working on further revisions to my app. The most notable of these revisions involves switching action bar implementations from GreenDroid to ActionBarSherlock. While this will benefit me tremendously as I'll be able to use native Android 3.0+ components when running on those platforms, it means that I need to start using Fragments as well as the rest of the Android Support Package.
I've be saving much of what I have learned for another post, but I felt like sharing this tidbit right now. One thing that quickly became apparent was that a custom dialog that I was using (with positive/negative buttons) was not going to cut it, as the system dialogs were rendering the button strip differently...
So I've been developing an Android application on and off for the past few months. In the latest iteration of the app, I wanted to make some options that were hidden in a menu more discoverable. The accepted way of doing this in Android is through adopting the Action Bar design pattern. As described in the official Android Developers Blog entry on the matter:
The Action bar gives your users onscreen access to the most frequently used actions in your application. We recommend you use this pattern if you want to dedicate screen real estate for common actions. Using this pattern replaces the title bar. It works with the Dashboard, as the upper left portion of the Action bar is where we recommend you place a quick link back to the dashboard or other app home screen.
Awesome, right? A unified UI paradigm for Android. Let me just add the widget to my Activity... umm, uhh... where is it? Nowhere in the Android 2.x SDKs. Instead, Google decided to kill two birds with one stone and encouraged developers to look at the source code for the Google I/O schedule app. This way people could not only learn how to use and implement the pattern, but they can also see what a well-written Android app is supposed to look like.
That's all well and good, but what about the lazy efficient among us, who don't want to reinvent the wheel and write the same instrumentation every time we make an Activity? Once again, Google to the rescue. With the advent of library projects, the ADT plugin for Eclipse makes importing standalone/reusable components into your existing project easy. After this feature was made available, the number of rich, third-party libraries for Android skyrocketed. Among these were several that had reusable Action Bar controls. After some experimentation, I settled on GreenDroid.
GreenDroid's claim to fame is the notion that you need to alter very little of your existing code to get attractive, functional UI components. Since my project was mostly complete at the time of implementation, this was a huge plus. And, for the most part, it ended up being true.
Spambots exist to teach people a lesson - never give your credit card numbers to websites proffered by nubile girls with webcams and far too much free time on their hands. These bots usually follow a script of "Hi, how are you? Oh, that's nice. I'm bored and fresh out of the shower. I'm going to go on my webcam and expose myself on the internet (because that's what us twentysomethings do). Here's the site!"
Recently, one messaged me on AIM (yes, I still use it), so I decided to have a little fun with it. The conversation is after the break.
I'm currently working on some much-needed updates to an AppEngine service that processes and serves content based on a CSV version of a spreadsheet. One of these new features is the ability to upload the spreadsheet via an HTML form. Of course, being early-ish on a Sunday morning, there was a little head scratching...
<html> <body> <form action="/admin" method="post"> <div><input type="file" name="csvfile" accept="text/csv"></div> <div><input type="submit" value="Update CSV"></div> </form> </body> </html>
Looks ok, right? Not quite.
self.request.get("csvfile") only returns the file name! I must be forgetting something. After my coffee kicked in, I took another look at it and facepalmed. The following modification returned what I wanted.
Sure enough, adding the "enctype" attribute has my code returning the contents of the CSV file.
Moral of the story? Don't code before your morning intake of caffeine.
Someone pinged me to say that I need to update this more often... or at all, really.
My goal with this blog was to fill it with useful content, like clever hacks, product reviews and original musings. I didn't want to turn it into a diary. And I won't. That being said, here are a few things I feel are of note...
- Droiiiiiiiid... Yeah, I dropped the Storm like a bad habit. I'm now rocking a HTC Droid Incredible, and it lives up to it's name. The minute I was able to, I rooted it and installed CyanogenMod 6 to get the stock Android experience (plus some).
- Vrooooom... A car, I need a new one. I'm currently trying to decide between a hybrid or ICE Honda Civic. I'd go with the extra $$$ for a hybrid, but the reduced acceleration is kind of a turn off. I figure this is a decision best made after test driving. Don't want to put the horse before the carriage.
- 10001101... I've been dabbling in writing Android applications. Of course, finding the motivation to follow through on a junk project is very difficult. Work still has me pounding away at ASP.NET/C#. For all of the negative flack MS gets, I really do like the features of the ecosystem.
I'll be updating the site/blog some more over the next few weeks. I promise!
Note: This is an old review that has been sitting in my draft folder. Rather than delete it, I decided to publish it. The content may be outdated as I was testing the first official release.
Recently, Twitter made waves in the tech world by buying Tweetie (renaming it Twitter for iPhone) and launching their own BlackBerry App World and Android [QR here] clients. I've been a long-time ÜberTwitter user, but decided to see what sort of experience the official Twitter app for BlackBerry could provide. Click past the jump for my review!
Still getting things set up here. Looking forward to getting back into the blogging saddle.