development

A companion app to the Catholic News Live website, my new CNL app has been approved for sale on the iTunes App Store.

You can purchase the CNL app for $0.99 here, or read more about the app (and see some pretty screenshots) on the Catholic News Live website. Catholic News Live delivers the latest Catholic News to your computer and iPhone, and pulls in news from over 50 different Catholic sources, every five minutes.

The App's highlight features are the ability to view news on a world map, and to share news via whatever social media you use. It's a very simple, but very powerful little app that will help you stay in tune with what's going on with the Catholic Church.

Just a little bit of an overview of a couple things I'm working on / where I've been:

The sparsely-attended 'Scaling the Drupal Community' session, led by webchick and heyrocker, was one of the few sessions I've attended at DrupalCon Chicago that held my interest throughout. And, since a few people on IRC asked me to post my session notes, I thought I'd do so and put them up on the Planet.

If you, like me, thought there were too many awesome sessions during this timeslot that you decided to go to another one, then this post is for you—I believe that anyone invested in Drupal's future stands to gain something from reflecting on what webchick said at the session.

Now, on to the notes. I will give a summary of a statement by webchick, then my reflection (kind of a Q&A format):

On 'Drupal Answers' vs. a drupal.org solution for Drupal Support

Drupal Answers is a new Stack Exchange site for answering Drupal questions, and it's in public beta right now. The site is hosted off the 'drupal.org' family of sites, and has a few hundred users so far...

Webchick: Webchick basically stated that she's leaning towards what we already have (with slight adjustments). She mentioned that there's no good answer for the question of motivating people to help support drupal newbies without incentives (a karma or reputation system).

Also, she said that moving the support away from drupal.org is potentially very dangerous; this could lead the 'newbie' community away from the 'expert' community (which tends to discuss things in drupal.org issue queues. Right now, 'newbies' typically hang around in drupal.org forums, and 'experts' typically stick to their trackers and issue queues.

I'm happy to announce that my first iPhone App—Catholic STL—has been accepted by Apple for the iTunes App Store, and is available for free starting today!

The Archdiocese of St. Louis also announced the App this morning, and has a 'mobile app' section on the website with screenshots, an introductory video, and more information about the App. The App is free, so what are you waiting for? If you live in St. Louis, or are visiting, go ahead and download it now.

The App basically lets users find parishes and sacrament times/parish information in the first section, read news in the second section, and read and post prayer requests on the Archdiocesan website in the third section.

After having jumped into the pool of mobile app development head first (more on that to come), I finally have a little more perspective when it comes to developing for iOS vs. Android.

One of the first things that I did when I started developing an App for iOS is purchase an iPod Touch. There's no way I wanted to be using my iPhone for all my development work, and I needed a device I could acquire quickly, at a low cost (i.e. without a contract), and not worry about battery life, durability, etc.

Plus, I know tons of people with iPod Touches already—most are people who don't want to spend an outrageous amount of money on a 'smartphone' plan with one of the major US carriers, but want a great mobile computing device/PDA/media player.

So, buy the iPod Touch for ~$200, download Xcode, and you're good to go for iOS development. Plus, the whole App Store process, while it's a bit convoluted at times, is very well structured, and offers developers easy avenues towards getting an app from development to sale to success with little effort required.

Of course, as I'm getting nearer and nearer the App's release, I'm hearing calls from all corners of Geekdom, "When you gonna release for Android?!" And the more frequent the cries of distress, the more frequently I look around for ways that I can/should start developing for Android.

Today we released Visibility for Mac, a free Mac OS X application that helps you make invisible files visible, easily. Check it out!

This year, one of my resolutions is to become a more experienced programmer—not only in web development (I can hold my own with PHP, server scripting, and web design languages)—and one of the measurable achievements I'd like to accomplish is having apps on the Mac App Store and iOS App Store.

I submitted a new Mac App, Visibility*, on January 9, and was hoping the app might be reviewed quickly so I could experience a few days on the Mac App store soon after its launch. Well, after more than two weeks of waiting, the App is still 'Waiting for Review.'

Following the advice of some other developers on Apple's Developer Forums, I submitted an expedited app review support ticket... and didn't get a response for over a week!

From the response email:

Thanks for your email and feedback. In order to get as many developers into the Mac App Store as possible we are reviewing apps on a first-come first-served basis. The size of any individual app or its fixes do not have an impact on when the app will enter In Review state.

We will get to your application as quickly as possible.

Just posted for my own reference - here's my workflow for updating a D6 (probably also D7) website using drush. Comprehensive information about all drush commands can be found on the http://drush.ws/ website. If you're not yet drinking the drush kool-aid, you need to—if you use a Linux server, of course.

1. Visit admin/reports/updates page on your site, read through any relevant release notes for required updates (to check if there are special requirements for said update).
2. $ drush @site pm-updatecode <module1_shortname> <module2_shortname> (add all modules to be updated)
3. $ drush @site updatedb (updates the site database - update.php)
4. $ drush @site cc all (clears all caches on the site)

The reason I do this manually, instead of running something like pm-update or pm-updatecode is that I like the granularity and security of doing all the updates discretely—especially when I'm updating a larger site, where I like to know exactly what's happening when I update.

I've begun working a lot more with Drupal multisites, as doing so saves a lot of time in certain situations (usually, when you have a large group of sites that use the same kinds of Drupal modules, but need to have separate databases and front-end information.

One problem I've finally overcome is the use of actual domain host names for development (i.e. typing in dev.example.com instead of localhost to get to a site). This is important when doing multisite work, as it lets you use Drupal's built-in multisite capabilities without having to hack your way around using the http://localhost/ url.

Here's what I did to use dev.example.com to access a dev.example.com multisite in a Drupal installation using MAMP (the dev.example.com folder is located within Drupal's /sites/ folder):

Catholic News Live - a little site I whipped up yesterday afternoon. Still in early, early beta. If you're interested in joining and helping sort items into channels (and maybe other perks sooner or later), please email [email protected].