Peter Armstrong

Planned Weekday Schedule to Reduce Information Consumption Overload and Improve Productivity

Peter Armstrong — Wed, 25 Aug 2010 04:52:55 +0000

Let’s see how this goes…

Planned Weekday Schedule

700 - 715 : wake up, shower, dress
715 - 740 : breakfast & commute to train
740 - 840 : commute & write or work on train
840 - 900 : commute to office
900 - 1130 : work alone
1130 - 1200 : email
1200 - 1300 : lunch
1300 - 1630 : work alone or with others
1630 - 1650 : commute to train
1650 - 1740 : commute & work on train, pick 3 things to accomplish tomorrow
1740 - 2000 : dinner & family time
2000 - 2100 : exercise (weights, elliptical training while reading RSS, Hacker News, TechCrunch, Twitter & Reddit on iPad)
2100 - 2300 : relax, write or work

The ideas here are to:
1. Batch email to be done once a day.
2. Do my individual effort work in the morning, and if necessary, in the evening. The afternoon can be a “work with others” time when beneficial.
3. Exercise every day. The iPad is good for is surfing the web while elliptical training, so if I limit my information consumption habit to that time and device, then I will not only exercise daily but I’ll break the habit of consuming information on my laptop. (I’ve also just unsubscribed from about 75% of my RSS feeds.)
4. Actually write and launch Lean Publishing. I actually have something to say now, so no more procrastinating!

A Huge Thanks To Giles Bowkett for Helping Leanpub!

Peter Armstrong — Wed, 05 May 2010 04:11:53 +0000

So, back in December of last year, Giles Bowkett announced that he was starting doing consulting. At that time, Leanpub was going through a direction crisis, since I was realizing that we were in fact building a full-fledged publishing platform, based on our blog-to-book workflow that we had evolved in order to publish Eric Ries’ Startup Lessons Learned blog as a book.

I was starting to realize that the direction we had chosen (a custom Flex + Rails app) was possibly not the right way to go, since while it made sense for the PDF-generation workflow, it made less sense for the publishing platform. My fear was that if the blog-to-book approach that we were using for Eric Ries’ book was indeed the future of Leanpub, we would end up needing to create a full-featured blogging platform or else get really good at totally seamless RSS feed importing.

This was the setup and my frame of mind when I saw Giles’ post about his starting consulting. Since I’ve been part of the Ruby community for a while (writing a somewhat popular book and organizing the Vancouver Ruby/Rails meetup), I was already familiar with Giles.

I knew two things:
1. He would be extremely blunt.
2. He would be completely honest.

So, who better to pay as a consultant?

The last thing I wanted was someone to say nice things to me in order to get or keep my business! So, I signed up for Giles’ consulting program, explained the Leanpub idea to Giles and gave him a demo of the current app.

I had already known that the app was at a very early stage and had a long way to go. However, after spending an hour with Giles, going over the goals of the app, its current state, and the direction we intended to go, I realized a couple things:

1. The app was much worse than I had thought.
2. Essentially all the useful code was in the book generation, and not much would be lost by throwing away the UI and starting over.

This was simultaneously depressing and liberating.

I went to Whistler and thought through the Leanpub problem some more. I realized that not only should we throw away the Flex UI (which was my code, and which totally sucked) but we should also throw away the Rails app as well!

I realized that instead we should base Leanpub on WordPress MU. After all, we were fundamentally building a new publishing platform, and this publishing platform was putting blogging at its core. (We had our work with Eric Ries to thank for this realization: hooray for Steve Blank’s Customer Development and Eric Ries’ Lean Startup approaches!)

So, since we were building a book publishing platform based on blogging, why reinvent the wheel when WordPress was already an extremely powerful and popular blogging platform, and when WordPress MU could handle multiple users and blogs on the same system?

WordPress MU it was.

It’s hard to throw away your own code, but the lightness I felt after typing rm -rf app/flex was invigorating.

Since this realization, we started building the new Leanpub in January in our spare time. (Ruboss is itself a consulting company, after all: we’re bootstrapping Leanpub, and we have families to feed and mortgages to pay!) Over the past few months we have made significant progress with Leanpub, and we’re already farther ahead than we would have been if we had kept going down the path that we had chosen. (We even built a new Flex app–but just to organize the structure of a book, since using the WordPress Pages editor to do this is extremely cumbersome and unintuitive.)

We have Eric Ries to thank for the blog-to-book workflow, but personally I have Giles to thank for essentially making me see my app with fresh and much more critical eyes.

So…

Thanks Giles!

If you are building an app and are looking for honest advice, I highly recommend contacting Giles. This is not a replacement for the Customer Development process, it’s a useful addition to it… My recommendation if you work with Giles is to essentially do the Customer Development process with him: talk to him as though you’re trying to make him a customer. That’s what I did, and it was well worth it…

Photos from San Francisco Trip

Peter Armstrong — Tue, 27 Apr 2010 07:00:08 +0000

After a fantastic conference on Friday, it was nice to relax a bit on the weekend…

First, I can’t resist the juxtaposition…

Also, the wine and scenery was great…

My Humble Contribution to Steve Blank’s Talk

Peter Armstrong — Sat, 24 Apr 2010 07:22:35 +0000

As you probably know from Twitter, Steve Blank gave an absolutely fantastic talk at the Startup Lessons Learned conference today.

I’m proud (and more amused than I probably should be) to say that I made a small photo contribution to it!

I suppose I should read the book on the chairlift instead…

…or just leave the book in the snow while I snowboard!

My (Attempted) Reality Distortion Field

Peter Armstrong — Fri, 23 Apr 2010 06:25:55 +0000

Steve Blank made a great post today called Turning on your Reality Distortion Field, explaining how he recommends doing a 30 second, < 100 word elevator pitch.

I've so far been pretty terrible at improvising these, so I decided to actually write one down this time. Here it is, all 99 words of it…

Imagine a world in which authors can actually make money writing books…

Imagine a world in which authors know who their readers are, and can have a meaningful conversation with them about their books—before they’re even “published”…

Imagine a world in which authors could apply Customer Development and Lean Startup principles to the process of writing and publishing a book…

If you imagine that world long enough, you realize that the authors who know their readers the best are bloggers, and that the future of publishing is turning blogs into books. Automatically.

That future is called … Leanpub.

Cheesy? Good? Comments please…

Why Lean Publishing Makes Financial Sense for Authors, based on my Flexible Rails Royalties

Peter Armstrong — Fri, 16 Apr 2010 06:08:50 +0000

Since I’m Canadian, I have a genetic predisposition to not talking about success — even very modest success. So, I haven’t really gone into details about the financial success of Flexible Rails, since that would be unseemly.

Now, however, it’s in the best interest of my company (Ruboss) to do so, since it makes my point about what we’re trying to do with Leanpub a lot more obvious. If I’m going to try to convince you that Lean Publishing is the future of publishing, I need better data than stupid pictures drawn with a sharpie.

So, I’m using my experience with Flexible Rails as a case study for why Lean Publishing makes financial sense for authors. I’m going to spend this post going into details of how I managed to make decent money from Flexible Rails, which was a modest success for a niche book. I made about $34,000 from the PDF alone, and about $48,000 total from it. Even better, it launched my company!

You can do much better than $34,000 from a PDF! For example, this is only about 3-5% of what 37signals made from Getting Real, which (as far as I know) is the gold standard for success of a PDF book. (Yes, they made about a million dollars from a PDF!) Their story is well-known, so I don’t need to tell it here…

In fact, I’d say that my modest success story is more relevant to you, since chances are you resemble me more than DHH or Jason Fried. Unlike them, I was not famous when I self-published Flexible Rails; I was a nobody, living in Parksville, BC, working remotely for a Silicon Valley company in the mortgage industry. I didn’t have a famous blog. I hadn’t created a famous product or web app framework. (These statements are still true today! Well, mostly true: I live in Maple Ridge now and I have my own company, but I’m still not famous, nor have I created a famous product or web app framework!)

Yet I managed to make a lot more than what authors typically make from books (which is typically under $10,000, from what I hear). This wasn’t because my book was a better book. It was because the way that I published it was better. I published it early, and I published it often. (Sound familiar?)

Flexible Rails went through 23 unfinished revisions on Lulu before becoming a Manning book. During that time, I built a community of readers around the raw manuscript, so that when I switched to Manning to produce a finished product (and get the channel revenue that I had no access to) I had grassroots buzz around the book.

Anyway, stop tal-tal-talkin ’bout blah, blah, blah, chances are what you want to see is numbers. So, here you go (these look images look better when viewed full size in their own tab):

The Self-Published Numbers (While Flexible Rails Was In-Progress)

The Self-Published + Manning Numbers (Flexible Rails Was Published in Q1 2008)

As you can see, the revenue from non-ebook sales and from non-direct sales was negligible. So, it really is all about the ebooks. Screw the iPad, PDF FTW!

I’ll go over what this all means in a lot more detail in a future post…

Why Leanpub Has No DRM or “PDF Document Security” and Never Will

Peter Armstrong — Fri, 16 Apr 2010 04:02:40 +0000

Note: This is based on my emailed reply to a prospective Leanpub author. I shouldn’t write emails on the train, since they tend to expand to fill the remainder of my train commute home — and I probably make the prospective customer fall asleep after the second paragraph!

I was asked today whether we had plans to offer PDF document security on Leanpub. This was my reply…

Speaking as someone who has spent over 1000 hours writing 2 technical books, both of which are constantly pirated on the internet:

We offer absolutely no PDF document security at all.

I doubt we ever will.

We may offer a footer (e.g. “This book was sold to peterarmstrong@gmail.com”) in the future, if customers ask for it. This may reduce the type of “innocent” sharing with friends that currently happens with books, but it won’t be any real security against piracy: these types of footers are easily removed.

I know that both my books are pirated: I see them show up an automated search I have set up in Google Reader. While I wish every one of those copies was a sale for me, I realize that hardly any would have been sales. In fact, I’d rather that someone pirates one of my books than buys a competing book: in the future, these people may buy something else I produce. (This is Microsoft’s approach with Windows in developing markets, and it’s served them well.)

Our position is that anything digital can be copied, and the way you succeed as an author is by making your content easy to buy and good enough to grow a community around.

Right now the best selling book on Leanpub is The Venture Hacks Bible, which is about 1000 pages of content that can currently be read for free on the internet. (The book is just their blog, after all. We shout that fact from the rooftops, and on the cover of the book!)

However, people have still bought the PDF (we have a great conversion % of unique visitors). Why? Well, primarily since it’s more convenient for them to buy the PDF to read it offline than it is to read years of the blog archive or to try to find a copy to pirate.

This approach has worked well for other people: 37signals made about a million dollars on sales of Getting Real, even though it was a DRM-free PDF.

Now, I wasn’t nearly as successful with my books as they were, but I still made over $25,000 in royalties on DRM-free PDFs of my Flexible Rails book (over $13,000 of which while I was self-publishing it). And Flexible Rails was only a modestly successful book about a very niche topic: how to use Adobe Flex with Ruby on Rails.

My point is that if you start famous (like 37signals) or as a complete nobody (me), you can make good money selling DRM-free PDFs. You just need to write good content and build a community around it…

The Venture Hacks Bible is now on Leanpub!

Peter Armstrong — Mon, 12 Apr 2010 05:29:44 +0000

We’re done our pricing experiments, and we’ve settled on a price of $19 for now. (It won’t get any cheaper, but we’re not ruling out making it more expensive as it grows…)

So, it’s the official launch of The Venture Hacks Bible, which is now linked from the Venture Hacks homepage!

The Venture Hacks Bible is a constantly-updated version of the entire Venture Hacks blog. (We regenerate it once a month.) It’s currently about 1000 pages.

For posterity, since I think we’ll look back at this as a major moment in Leanpub history, here’s a screenshot of the link on the Venture Hacks sidebar:

Woo hoo!

This is a triumph for the Lean Startup / Customer Development approach, btw. The entire blog-to-book workflow which is the foundation of Leanpub was created out of interaction with a customer, and iterated on until we got to this point. I’ll blog more about that later…

Hello! Flex 4 - Diffs Between Flex 4 Beta 2 and Flex 4 Final

Peter Armstrong — Sat, 10 Apr 2010 21:22:47 +0000

I am currently revising the ebook of Hello! Flex 4 to use Flex 4 Final instead of Flex 4 Beta 2, which is what the first printing of the book uses.

However, in order to be totally transparent, here is every diff in the Hello! Flex 4 source code from Flex 4 Beta 2 and Flex 4 Final.

As you can see, almost all the changes are just the halo to mx namespace change I mentioned earlier. (If this change hadn’t been made, the book would have been almost completely unchanged.)

(This will hopefully be the most boring blog post I’ll ever write!)

Chapter 1

Session 01

~/hf4[master]$ diff -r code_Flex4Beta2/session01/src code_Flex4Final/session01/src diff -r code_Flex4Beta2/session01/src/Hello.mxml code_Flex4Final/session01/src/Hello.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”>

Session 02

~/hf4[master]$ diff -r code_Flex4Beta2/session02/src code_Flex4Final/session02/src diff -r code_Flex4Beta2/session02/src/Tester.mxml code_Flex4Final/session02/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 03

~/hf4[master]$ diff -r code_Flex4Beta2/session03/src code_Flex4Final/session03/src diff -r code_Flex4Beta2/session03/src/BindingToModel.mxml code_Flex4Final/session03/src/BindingToModel.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”> diff -r code_Flex4Beta2/session03/src/OneWay.mxml code_Flex4Final/session03/src/OneWay.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”> diff -r code_Flex4Beta2/session03/src/TwoWay.mxml code_Flex4Final/session03/src/TwoWay.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”> diff -r code_Flex4Beta2/session03/src/TwoWayBindingClobbersModel.mxml code_Flex4Final/session03/src/TwoWayBindingClobbersModel.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”>

Session 04

~/hf4[master]$ diff -r code_Flex4Beta2/session04/src code_Flex4Final/session04/src diff -r code_Flex4Beta2/session04/src/TodoList.mxml code_Flex4Final/session04/src/TodoList.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”>

Session 05

~/hf4[master]$ diff -r code_Flex4Beta2/session05/src code_Flex4Final/session05/src diff -r code_Flex4Beta2/session05/src/TodoList.mxml code_Flex4Final/session05/src/TodoList.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”>

Chapter 2

Session 06

~/hf4[master]$ diff -r code_Flex4Beta2/session06/src code_Flex4Final/session06/src diff -r code_Flex4Beta2/session06/src/Tester.mxml code_Flex4Final/session06/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 07

diff -r code_Flex4Beta2/session07/src/Tester.mxml code_Flex4Final/session07/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 08

~/hf4[master]$ diff -r code_Flex4Beta2/session08/src code_Flex4Final/session08/src diff -r code_Flex4Beta2/session08/src/Tester.mxml code_Flex4Final/session08/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 09

~/hf4[master]$ diff -r code_Flex4Beta2/session09/src code_Flex4Final/session09/src diff -r code_Flex4Beta2/session09/src/Tester.mxml code_Flex4Final/session09/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 10

~/hf4[master]$ diff -r code_Flex4Beta2/session10/src code_Flex4Final/session10/src diff -r code_Flex4Beta2/session10/src/Tester.mxml code_Flex4Final/session10/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Chapter 3

Session 11

~/hf4[master]$ diff -r code_Flex4Beta2/session11/src code_Flex4Final/session11/src diff -r code_Flex4Beta2/session11/src/Tester.mxml code_Flex4Final/session11/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 12

~/hf4[master]$ diff -r code_Flex4Beta2/session12/src code_Flex4Final/session12/src diff -r code_Flex4Beta2/session12/src/Tester.mxml code_Flex4Final/session12/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” 30c30 < liveDragging="true" height="50" value="@{_bread}"/> — > liveDragging=”true” height=”50″ value=”{_bread}”/> 49c49 < --- > 51c51 < --- >

Session 13

~/hf4[master]$ diff -r code_Flex4Beta2/session13/src code_Flex4Final/session13/src diff -r code_Flex4Beta2/session13/src/Tester.mxml code_Flex4Final/session13/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 14

Session 14a:

~/hf4[master]$ diff -r code_Flex4Beta2/session14/session14a/src/ code_Flex4Final/session14/session14a/src/ diff -r code_Flex4Beta2/session14/session14a/src/OnlyConnect.mxml code_Flex4Final/session14/session14a/src/OnlyConnect.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/session14/session14a/src/components/BoardDisplay.mxml code_Flex4Final/session14/session14a/src/components/BoardDisplay.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 14b:

~/hf4[master]$ diff -r code_Flex4Beta2/session14/session14b/src/ code_Flex4Final/session14/session14b/src/ diff -r code_Flex4Beta2/session14/session14b/src/OnlyConnect.mxml code_Flex4Final/session14/session14b/src/OnlyConnect.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/session14/session14b/src/components/BoardDisplay.mxml code_Flex4Final/session14/session14b/src/components/BoardDisplay.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 14c:

~/hf4[master]$ diff -r code_Flex4Beta2/session14/session14c/src/ code_Flex4Final/session14/session14c/src/ diff -r code_Flex4Beta2/session14/session14c/src/OnlyConnect.mxml code_Flex4Final/session14/session14c/src/OnlyConnect.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” 8c8 < initialize="board.newGame()"> — > initialize=”boardDisplay.newGame()”> 15c15 < board.playerOneFill : board.playerTwoFill; --- > boardDisplay.playerOneFill : boardDisplay.playerTwoFill; 28c28 < — > 30c30 < fill="{getColor(board.playerOneTurn)}"/> — > fill=”{getColor(boardDisplay.board.playerOneTurn)}”/> 32c32 < text="Player {board.playerOneTurn ? '1' : '2'} Turn"/> — > text=”Player {boardDisplay.board.playerOneTurn ? ‘1′ : ‘2′} Turn”/> 34c34 < — > diff -r code_Flex4Beta2/session14/session14c/src/components/BoardDisplay.mxml code_Flex4Final/session14/session14c/src/components/BoardDisplay.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” 26c26 < private var _board:Board; --- > public var board:Board; 32c32 < _board.newGame(); --- > board.newGame(); 36,39d35 < public function get playerOneTurn():Boolean { < return _board.playerOneTurn; < } < 41,42c37,38 < _board = new Board(); < _board.newGame(); --- > board = new Board(); > board.newGame(); 62c58 < switch (_board.getData(row, col)) { --- > switch (board.getData(row, col)) { 74c70 < var row:int = _board.playerMove(column); --- > var row:int = board.playerMove(column); 77c73 < var winner:int = _board.checkWinner(); --- > var winner:int = board.checkWinner(); ~/hf4[master]$

Session 15

~/hf4[master]$ diff -r code_Flex4Beta2/session15/src code_Flex4Final/session15/src diff -r code_Flex4Beta2/session15/src/Tester.mxml code_Flex4Final/session15/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Chapter 4

Session 16

Session 16a:

~/hf4[master]$ diff -r code_Flex4Beta2/session16/session16a/src/ code_Flex4Final/session16/session16a/src/ diff -r code_Flex4Beta2/session16/session16a/src/Tester.mxml code_Flex4Final/session16/session16a/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 16b:

~/hf4[master]$ diff -r code_Flex4Beta2/session16/session16b/src/ code_Flex4Final/session16/session16b/src/ diff -r code_Flex4Beta2/session16/session16b/src/Tester.mxml code_Flex4Final/session16/session16b/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 16c:

~/hf4[master]$ diff -r code_Flex4Beta2/session16/session16c/src/ code_Flex4Final/session16/session16c/src/ diff -r code_Flex4Beta2/session16/session16c/src/Tester.mxml code_Flex4Final/session16/session16c/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 17

~/hf4[master]$ diff -r code_Flex4Beta2/session17/src code_Flex4Final/session17/src diff -r code_Flex4Beta2/session17/src/Tester.mxml code_Flex4Final/session17/src/Tester.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/session17/src/components/HPanel.mxml code_Flex4Final/session17/src/components/HPanel.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 18

~/hf4[master]$ diff -r code_Flex4Beta2/session18/src code_Flex4Final/session18/src diff -r code_Flex4Beta2/session18/src/Tester.mxml code_Flex4Final/session18/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 19

~/hf4[master]$ diff -r code_Flex4Beta2/session19/src code_Flex4Final/session19/src diff -r code_Flex4Beta2/session19/src/Tester.mxml code_Flex4Final/session19/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” 10c10 < @namespace mx "library://ns.adobe.com/flex/halo"; --- > @namespace mx “library://ns.adobe.com/flex/mx”; diff -r code_Flex4Beta2/session19/src/styles.css code_Flex4Final/session19/src/styles.css 2c2 < @namespace mx "library://ns.adobe.com/flex/halo"; --- > @namespace mx “library://ns.adobe.com/flex/mx”;

Session 20

~/hf4[master]$ diff -r code_Flex4Beta2/session20/src code_Flex4Final/session20/src diff -r code_Flex4Beta2/session20/src/Tester.mxml code_Flex4Final/session20/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 21

~/hf4[master]$ diff -r code_Flex4Beta2/session21/src code_Flex4Final/session21/src diff -r code_Flex4Beta2/session21/src/Tester.mxml code_Flex4Final/session21/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Chapter 5

Session 22

~/hf4[master]$ diff -r code_Flex4Beta2/session22/src code_Flex4Final/session22/src diff -r code_Flex4Beta2/session22/src/Tester.mxml code_Flex4Final/session22/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 23

~/hf4[master]$ diff -r code_Flex4Beta2/session23/src code_Flex4Final/session23/src diff -r code_Flex4Beta2/session23/src/Tester.mxml code_Flex4Final/session23/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 24

~/hf4[master]$ diff -r code_Flex4Beta2/session24/src code_Flex4Final/session24/src diff -r code_Flex4Beta2/session24/src/TestTitleWindow.mxml code_Flex4Final/session24/src/TestTitleWindow.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/session24/src/Tester.mxml code_Flex4Final/session24/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Chapter 6

Session 25

~/hf4[master]$ diff -r code_Flex4Beta2/session25/src code_Flex4Final/session25/src diff -r code_Flex4Beta2/session25/src/Tester.mxml code_Flex4Final/session25/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Session 26

~/hf4[master]$ diff -r code_Flex4Beta2/session26/src code_Flex4Final/session26/src diff -r code_Flex4Beta2/session26/src/Tester.mxml code_Flex4Final/session26/src/Tester.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/session26/src/components/AddressForm.mxml code_Flex4Final/session26/src/components/AddressForm.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx”

Chapter 7

~/hf4[master]$ diff -r code_Flex4Beta2/ch07/src code_Flex4Final/ch07/src/ diff -r code_Flex4Beta2/ch07/src/SocialStalkr.mxml code_Flex4Final/ch07/src/SocialStalkr.mxml 5c5 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/FollowingGroup.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/FollowingGroup.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/LoginPanel.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/LoginPanel.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/MainApp.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/MainApp.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/MapPanel.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/MapPanel.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/TwitterGroup.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/TwitterGroup.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/UserListItemRenderer.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/UserListItemRenderer.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo"> — > xmlns:mx=”library://ns.adobe.com/flex/mx”> diff -r code_Flex4Beta2/ch07/src/com/socialstalkr/components/YouGroup.mxml code_Flex4Final/ch07/src/com/socialstalkr/components/YouGroup.mxml 4c4 < xmlns:mx="library://ns.adobe.com/flex/halo" --- > xmlns:mx=”library://ns.adobe.com/flex/mx” ~/hf4[master]$

Typesetting Error in Session 1 in Hello! Flex 4

Peter Armstrong — Mon, 05 Apr 2010 19:27:29 +0000

There is an error in Session 1 of Hello! Flex 4. This error got introduced during typesetting. I have been raked over the coals for this in a one-star review of the book here.

The short version is you need to change the code in Session 1 to this:



   text="Hello! Flex 4"
    fontSize="128"/>

For the long version, this is the reply that I posted to that review…

Hi Steven,

I’m Peter Armstrong, the author of Hello! Flex 4.

You are correct that on page 6 of the book, the text is:

This is obviously a bug. The corrected text should be:

I am very sorry that I missed this error.

Now, there’s actually an interesting reason why this happened…

The initial completed manuscript of Hello! Flex 4 was written against Flex 4 Beta 1. In Beta 1 of Flex 4, you did not write s:Label, you wrote s:SimpleText.

I just dug up my completed manuscript, and here’s what the code sample was:

Note that it is correct. Besides pasting all the code in from the IDE into the manuscript, I also went the other way during the development editing process, pasting code from the manuscript back into Flash Builder. Everything worked.

Now, a few days before Hello! Flex 4 was going to press, Adobe delayed the ship date of Flex 4 from Q4 2009 to Q1 2010. They also released Beta 2 of Flex 4.

In Beta 2, Adobe changed s:SimpleText to s:Label, thus breaking the entire book!

Now, the book had already gone through all the editing and had been typeset. But, we obviously couldn’t ship the book like that. So, my instructions were to go through it and change all s:SimpleText to s:Label. This was done correctly everywhere in the book, except for in this one example in which case the text attribute got deleted.

Unfortunately, this happened to be the first example in the book!

I can assure you that I have compiled and run the code many times, during Flex 4 Beta 1, Beta 2 and (after the book was released) with Flex 4 Final.

So, to be clear, the full source code of this example (with Flex 4 Beta 2) should have been:

This is exactly what you say you needed to change the text to be. So, you’re completely correct.

However, if you had published that in a Flex 4 book you wrote, you would also be wrong!

See, there’s one more wrinkle… With Flex 4 Final, the full source code of this example should have been:

Spot the difference? The library://ns.adobe.com/flex/halo namespace got renamed to library://ns.adobe.com/flex/mx. This namespace change was made after Hello! Flex 4 went to press.

(This is my second book about Flex, and the joys of writing a technical book never get old!)

So, if you are using the final version of Flex 4 with the book examples, remember, always replace:

xmlns:mx="library://ns.adobe.com/flex/halo"

with

xmlns:mx="library://ns.adobe.com/flex/mx"

There are a couple of other minor changes, which are fully explained at the following blog post I made yesterday:
http://www.peterarmstrong.com/?p=169

This post has a link to the updated source code which works with Flex 4 Final.

If you do give the book another chance, what I highly recommend doing is downloading the updated code and using that, instead of typing in the code from the book.

Thanks,
Peter Armstrong