I thought other folks might be interested too.

Joe

-------- Original Message --------
Subject: asm screenshots
Date: Tue, 08 Dec 2009 15:26:39 -0800
From: Joe Blaylock <jrbl@slacNOSPAM.stanford.edu>
To: piotr.praczyk@gmailNOSPAM.com

As requested, here are some screenshots of the author special modes demo. I haven't done anything to clean these up; they're raw grabs of my alpha code running in my dev. browser session.

The pink indicates that the code isn't finished. When it's done, I'll turn it white, naturally.

In ASM0 you see that there's not much to it visually. Most of the action is just in the fact of its layout, and in the keyboard shortcuts (which don't all work yet. But most do.)

In ASM1 you can see that two of the checkbox columns have been "folded" by clicking on their titles. The folds (those vertical bars) can be clicked to bring the columns back.

The checkboxes maintain state with the affiliation text input areas. So if you type into the very last row, "INFN, Naples", then when you move focus that box will check itself. This will happen even if the checkbox column in folded.

This is shown in ASM3, where I've unfolded a checkbox column and unchecked in one column, and checked in another column, for the third row from the bottom. The box I checked is still hilighted with a little dotted box. You can see that changing the checkboxes changed the contents of the input box.

One of the things you can't see in these screenshots is copy/cut/paste, which works with the standard Windows keyboard accelerators, slightly modified (s-c-a-c,x,v) on a by-row basis. So if you've got input focus in the box that says "Barone, F." and you hit s-c-a-c, and then hit s-c-a-v, then that row - with its values and checkbox statuses, will be reproduced below so that it occurs twice. Rows can be deleted by cutting them and simply never pasting them back in.

One of the features that's broken is movement by keyboard. My intention was to overload tab, so that it would move between input fields and only input fields (not other page elements), and so it would wrap back to the beginning when the last input field was reached. I've had a lot of trouble making this work though, and realized the other day that this is probably because tab is one of the special browser keys. So I'll probably work on making that do the right thing after I've done some other, higher-priority jobs. (and had time to think about what key sequence I should use.)

I've fallen behind on integration with other tools. I'm working on pulling likely affiliations from BibKnowledge right now. Well, not right now since I'm emailing you. But approximately now.

Joe