Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2018

// Call createGrid from Ext.onReady() to render the simple grid
// to a div with id of 'divUiHook2'.
function createGrid() {

//==============================================
// code from Listing 7.1
//==============================================
var arrayData = [
['Jay Garcia', 'MD'],
['Aaron Baker', 'VA'],
['Susan Smith', 'DC'],
['Mary Stein', 'DE'],
['Bryan Shanley', 'NJ'],
['Nyri Selgado', 'CA']
];

var nameRecord = Ext.data.Record.create([
{ name:'name',mapping:0},
{ name:'state',mapping:1}
]);

var memoryProxy = new Ext.data.MemoryProxy(arrayData);
var arrayReader = new Ext.data.ArrayReader({ id:0 },nameRecord);

var store = new Ext.data.Store({
reader:arrayReader,
proxy:memoryProxy
});

store.load(); // this was missing -mfn
console.log(store.getCount()); // this is what clued me in -mfn

//==============================================
// code from Building_our_simple_gridpanel.html
//==============================================
var cm = new Ext.grid.ColumnModel([ // 1
{
header : 'Full Name',
sortable : true,

// changed this from fullName
dataIndex : 'name' // 2
},
{
header : 'State',
dataIndex : 'state'
}
]);

var gridView = new Ext.grid.GridView(); // 3
var selModel = new Ext.grid.RowSelectionModel({ // 4
singleSelect : true
});

var dummyGrid = new Ext.grid.GridPanel({ // 5
renderTo : 'divUiHook2', // changed from getBody.
//autoHeight : true, // replace with constant
height : 200, // constant height
width : 250,
store : store, // 6
view : gridView, // 7
colModel : cm, // 8
selModel : selModel,

title : 'Our first grid'
});
} // eo fn createGrid

I'm finally getting to the point that my hands hurt from typing too much, especially my index fingers, thumb, and wrists. I use a Microsoft Natural Keyboard Pro, which has helped in the past, but it's not enough. I think the reaching for gthy is getting to me. The mouse isn't helping either.

So for the usual reasons, I'm considering Dvorak.

How to Switch to a Dvorak Keyboard Layout: 8 steps - wikiHow:

In this sample paragraph, 70% of the letters are on the home row in Dvorak, with 15% top and 15% bottom. In QWERTY 30% are on the home row. Beware, it takes a little getting used to, especially if you're transitioning from a standard QWERTY keyboard.
...
The standard QWERTY keyboard layout was designed to prevent typewriter jams (which is no longer necessary with computers), whereas the Dvorak layout was designed specifically to be easy on the hands.

The problem is, of course, that we don't just use keyboards for typing English any more. And there's a good negative in that piece, however, that got me thinking... "Depending on your operating system, keyboard shortcuts such as CTRL+C may lose their convenient placement."

So the question for becomes, even if I could rethread my head around the layout, how would I do in VIm?

Let's check the vim Wikia entry for "Using Vim with the Dvorak keyboard layout":

Many Dvorak users have no problem learning the normal Vim commands with a Dvorak layout. The movement keys may not look it at first but are in fact pretty intuitive -- J and K are on the middle and index fingers of the left hand, right next to each other in the same order as on the qwerty layout, while H and L are the index and pinky fingers of the right hand, so the one for left is on the left -- again perfectly accessible.

[from the comments from the same page:]

I have been using Dvorak (as X keyboard map) and Vim for about two years now, without *any* adjustments (concerning Dvorak) to Vim at all, and it works great. The solution imho is to simply remember Vim commands by their name, rather than their keyboard position (e.g. I think I want to d(elete) 2 w(ords), and hit d2w without thinking about the key positions (my fingers know the position themselves).

I have a hard time buying that. Why do I want to leave roguelike controls again? Sounds like a mess.

It's an interesting example of standards inertia.

Guess I'm looking for a new keyboard.

EDIT: I think I'm trending towards this camp.

Effectively my brain was trying to wire three kinds of cursor movement modes:

1) Dvorak Vim with remappings (when I'm on my own machine)

2) Dvorak Vim with no remappings (when I'm on someone else's machine and have the keyboard remapped)

3) Qwerty Vim (when I'm on someone else's machine and don't have the keyboard remapped)

This is, simply, too much. Your life as a programmer is hard enough without you having to learn three different spatial layouts for text editing commands.

Labels: keyboard, pain, standards

public void DoWork(Stream input) { StreamReader sr = new StreamReader(input); string s = sr.ReadToEnd(); sr.Dispose(); NameValueCollection qs = HttpUtility.ParseQueryString(s); string firstName = qs["firstName"]; string lastName = qs["lastName"]; // Do work here }

Let's start by playing, "One of these things is not like the others." I guess the picture plates (the slick pages with reproductions of pictures) make the Jobs biography more difficult to print independently, though I'm not sure I would have known if the plates were missing.

The four non-Jobs biographies are all exactly the same height and width, if not thickness. The fonts are different, which I expected, but what I didn't expect is that the paper itself changes from book to book. I'd really be interested to see how the Science Fiction Book Club's deal reads. It's not so strange that they can print essentially every book the same size (wonder if they make special SFBC bookshelves too), but that the paper used inside comes closer to mactching the full-sized books is surprising. To be clear, as an example, A Perfect Blood has the slightly pulpy, textured paper (sort of an older paperback feel) that I'm used to the Hollows series having, I think. Evolutionary Void is white, smooth, hybridized-with-Bible-paper stuff.

I can't figure out exactly what they've changed. This page's criteria so far is the closest to helping me see what's different other than size. End papers are, indeed, white in these books, even when the paper isn't. There isn't a price on the books, on the jacket or the jacket's bar code, just as that page suggests. Strangely, that's true for the dust jacket for Steve Jobs as well -- it looks like it too has an SFBC jacket. There is a pretty plain looking, seven digit number on the back, outside dust jacket cover for each book that I don't recognize. For these books, those numbers are...

Jobs: 1349911
Perfect Blood: 1350398
Evolutionary Void: 1316162 (I'd somehow missed that this is 2¢ in hardback at Amazon. ARGH. IDIOT.)
Reamde: 1344352
Brooks omnibus: 1348717

So it looks like that number represents the order that the book club publisher got 'em.

(I'm a little steamed over my stupidity on Evolutionary Void right now. ARGH. Stupid. I actually overpaid on this one... $4.01 for Amazon used shipped, $1+(18.70/5) = $4.74 for the SFBC edition. STUPID.)

Oh well. So that's interesting. I'll see if I can't get some pictures up of the paper changes that are a little higher quality than the picture, above.

UPDATE: While reading last night, I think I figured out where the obvious cost cutting is. I mean, less paper is one, the slightly cheap feel of the cover is another (this is not a library friendly cover by any stretch), but the way the pages are bound is exceptionally suspect. It's just glued in. I'm pretty sure I read something about that process while Googling around before, but it wasn't quite so obvious until last night.

The Isaacson Jobs bio has real, threaded binding, so I'm sticking with my guess that that's publisher printed with SFBC jacket.

I'll compare the Harrison book to a hardback I have at home and post some pictures.

For anyone keeping score, the SFBC standard printing is...
1.) Smaller than a "real" hardback
2.) Often on different paper (though that needs more research)
3.) Has an inexpensive hard cover that's pretty light.
4.) Has a dust jacket without a price, but with what's now a nine digit "order of release" (potentially) book club number printed on the back.
5.) White endpapers.
6.) Is inexpensively glue-bound.

Labels: SFBC