Posts Tagged: web dev

Shakes Fist at Sockets

My personal project of the last few days is to start chipping away at my moblogging app. Roland Tanglao and I have been talking since the Big Adventure in May about working together to get my mobile blogging app idea off the ground.
Basically, I know that if I can get a php script to post to this blog via the Atom or XML-RPC protocol, then I can get my mobile to do it via a python app. I have now spent more than 12 hours spread out over 2 days researching the various protocols, reading docs, and then trying to get several different php scripts to post a simple blog post to Movable Type 4.3’s Atom or XML-RPC scripts.
Tonight, I kept getting errors that either the scripts aren’t able to authenticate (both Atom & XML-RPC) or with XML-RPC I keep getting a “32300:transport error – could not open socket”.
Darned sockets, I shake my fist at you.

Google I/O 2009, Day 2

Google I/O 2009, Day 2
Photo taken by Ms. Jen with her Nokia N95.

Here is my transcription of two sessions from Day 2, 05.28.09, of the Google I/O 2009. Per my usual, the following is a combination of live quotes from the speaker, notes off the slides, some paraphrase and a few of my own asides.
So far, Brett Slatkin’s Offline Processing on App Engine: A Look Ahead has been my favorite of the day. Lunch conversation with Prashant and Bastian was delightful.

(more…)

Google Wave Announced

Google Wave Announced
Photo taken by Ms. Jen with her Nokia N95.

Thur 05.28.09 – Google I/O keynote was Lars Rassmussen, Stephanie Hannon, and Jans Rassmussen giving a demonstration on the new Google Wave that is currently in development and the team is inviting the attendees of Google I/O to participate in developing the product and open source code before public release.

(more…)

Google I/O 2009, Day 1

Here is my transcription of two sessions from Day 1, 05.27.09, of the Google I/O 2009. Per my usual, the following is a combination of live quotes from the speaker, notes off the slides, some paraphrase and a few of my own asides.
Chris Nesiadek’s presentation on Android’s Interaction Design was my favorite of the day.

(more…)

Off to Google I/O

Off to Google I/O
Photo taken by Ms. Jen with her Nokia N95.

Wed 05.27.08 – Due to my plane being an hour late, I may miss the first session on how to code for Android. Even if late, I am looking forward to the Google App Engine and Android sessions today and tomorrow.

My One True New Love : Google App Engine

I have read up and checked out the Google AppEngine in a cursory fashion a couple of times in the last few months, even to the point of signing up for an invite before it was publicly open and downloading the SDK. But life and work and play were too busy, so I didn’t have time to really delve into GAE with any intent and real application.
Until today. Last Friday night, a much admired friend passed away in a car accident and on Sunday I was asked if I would develop a memorial web application for friends, family, and colleagues to post photos and stories up. I said yes and ran through my head quickly all the possible ways we could do it. Given the resources at hand it seemed that PHP, be it hand rolled or Cake PHP would be the only approach to take given the time & server constraints. Yikes.
I really struggle with PHP, I dislike all the verbage, punctuation, and braces. When I am able to make a whole app work in it, I am vastly relieved. But most of the time the butt kicking that PHP delivers is greater than my feelings of accomplishment.
One of the things that I do adore about Python and Ruby is that they both are lean and make sense. There is not butt kicking, only happy writing, testing and deploying. Except most host servers don’t like one to run a good Python or Ruby framework such as Django or Ruby on Rails. So if a client or friend already has a server and a domain and wants to move forward fast, much of the time Django and Ruby on Rails gets ruled out. Thus, the evils of PHP reassert themselves.
After sending most of yesterday and this morning debating of how I should plan and construct the memorial site, a meteor of insight flashed through my head… Google App Engine.
GAE is free (for now), uses Python and Django (happy days!!!!), it has great tutorials on top of all the Google resources. No reinventing the wheels with PHP and/or Cake PHP.
So this afternoon I started experimenting with GAE and discovered very quickly that between its webapp extension and the images/Picasa API that I would be able to develop the whole memorial application with very little fuss and stress.
Here is a quote from an email that I sent to the folks organizing the memorial:

Google AppEngine is a dreamy love bug of a dev environment, I may have to marry it. PHP is formally now dead to me. Normally 6 hours into a dev project I am not happy but really really really really really frustrated and writing snarky twitters about how much I *hate* PHP. But no… Love love love love the Google.

Google, thank you for making my life easier today when I would rather be crying than developing.