Dec. 30th, 2011


Dec. 30th, 2011 09:04 am
philkmills: Phil and guitar (Default)
Having created this account primarily for the purpose of software testing, I note that it would become more useful in that regard if it had content. :-)

While thinking about what I could put here, I got the idea that I might use it as...a journal! I think it would be an interesting -- to me! -- experiment to see if I could keep a log or diary of what I'm doing, primarily as it relates to software development. As I imagine the content and structure, I realize that it would be very low on entertainment value. (Possibly better on an 'educational' scale but even there, unlikely to be great.) I won't be cross-posting it.

For anyone who finds this boring beyond belief, feel free to drop me from your reading list! I understand completely. :-)
philkmills: Phil and guitar (Default)
In order to give some context for my proposed development journal, I suppose I should start with a couple of existing items: some description of the project and its present status.

What I want to create is a client application that runs on iOS and provides access to host systems running LiveJournal code or code derived from it. Although clients exist, I don't know of any that focus on working offline with the ability to defer and 'batch' actions related to a journal. This gave rise to my completely unimaginative working title of "Offline-Journal" for the application. Another goal is to create this as (what Apple calls) a Universal application, meaning it will run on iPhone/iPod/iPad devices as a single build and single download.

The state of the application at the moment is that the iPhone/iPod version of the UI is about 80% done and the iPad one is somewhere around 50%. I've written code that acts as a proof of concept for most of the host features I want to access. There are a couple of those that still need to be verified, including RSS access...something I've never tried.

This morning's job was to create a storyboard1 as a way of verifying that the various screens and controls are connected in sensible ways. The result was that I realized I needed two more view controllers: one for previewing posts and another for selecting among draft messages for extra editing or to post. Those now exist in skeleton form. Barring scope creep, I now have the high-level view of the iPhone UI in place -- just add logic.

1A storyboard is Apple-speak for a new way of graphically designing user interfaces that focuses on views and transitions between them as one thing. It has the advantage over similar 3rd-party tools of producing a runnable application shell as its end product.
philkmills: Phil and guitar (Default)
  • Completed the logic for moving between views on an iPhone/iPod. Any button or gesture that brings a new set of views onto the screen or dismisses the current one is now functional.

  • Identified views that don't need to exist on an iPad and coded around those in the controllers that are shared between devices. (Although I want this to work on smaller screens, working with them makes me happy that I originally waited until the iPad came out to get involved in iOS programming.)

April 2012

2223 2425262728

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 25th, 2017 12:37 am
Powered by Dreamwidth Studios