I think I'll try making the Button show up and down states. Sounds easy enough to spike something.

During a boring on-line meeting, I went ahead and put in the visibility logic. Let's see how things look now.

Dungeon content has aspects of model and aspects of view. Let's wrap it in a ContentView and then evolve to something more cohesive. Sort of Part I.

A few little changes to content this morning trigger some further improvement this afternoon. It's better than it was, and more capable too.

There's something not quite right about the design. Can we suss it out, or should we make it a bit worse? Lots of musing, very little code.

Sprites, yesterday and today. Refactoring the Content design, because Sprites.

Sometimes I'll refactor, over time, from design A to design B, and then decide to refactor back to B, or something very much like B. That's not a problem with the approach I'm demonstrating: it's a feature.

PubSub could hold onto objects that should be dead. Two attempts and much fumbling later, I've learned a bit but have no solution that I like.

Amid horrendous technical difficulties, I propose to build a Strategy-based content item. In an astounding plot twist, we drop the Strategy idea!

Having chosen Strategy over Mixin, we'll get down to doing it for real.

I made some changes to the scaling of images. I'll report on that, but what I really want to do is to eliminate some duplication. I surprise myself.

The 'art' that I have for the game comes at various scales. We need some way to accommodate that. Outcome: OK, but there's a tiny telltale scent of corruption. Squidgy.

A couple of little changes from yesterday. Mostly just speculation, vague design thinking. I create an abstract class and draw an up-button.

Yesterday's idea for selecting random tiles seems tasty. Let's try it. Is it a kind of Composite Pattern? Answer: a firm 'kind of'.

I made one new texture last night, on my iPad. So I think I'll point the game to the recently-purchased set.

There is Massive Duplication in my texture-finding code. I plan to remove that. It goes rather nicely.

Today I propose to change the Border code to return a 'meaningful' string rather than those 0-15 integers. I figure I can handle something that tricky, probably.

We've agreed that our current borders scheme works, but isn't quite what we need. Let's see how to make some progress in how we make this dungeon. This pass, we prepare the soil.

Having 'done' borders, I'm learning what I want. 'Making App' vs 'Shipping App'. A bit of philosophy, a bit about why I write these words.

I have a bit of time this afternoon. Let's see what we might do about borders that would be better.