Trashcan icon in arrowpad
Chuck Shotton noticed there's no way to delete stuff in the arrowpad interface. Now there is.
But be careful cause you need a keyboard to undo. Still need to figure that out.
Screen shot of the new feature.
An internal "virtual" keyboard
This change has no user interface at this time, but if it works it will get one.
The keyboard in Fargo is now virtualized. This means that there's a layer between the physical keyboard presented by JavaScript and the one used by the outliner. So we should be able to make this something the user can modify.
If it works here, I'll also add it to the Concord open source release.
Coders who want to see what the key definitions are, have a look in this JavaScript file.
Also, not all the mappings are done yet, there are keystrokes that are caught at a higher level, in the Fargo app, not in Concord. They have to be accounted for as well.
Cmd-keystrokes for Expand and Collapse
An oversight, there should have been keystrokes for Expand and Collapse.
These keystrokes go all the way back to ThinkTank for the Apple II, circa 1981 or so. Pretty ancient stuff.
Cmd-comma expands and cmd-period collapses.
The mnemonic for this is that the symbol over the comma is < which looks a bit like expanding. And > looks like collapsing (even though the meaning of the characters is opposite).
As a bonus, inherited from Frontier, cmd-shift-comma toggles expand and collapse state of the bar cursor headline
Experimental feature: The Arrow Pad
The arrow pad is designed to make reorganizing and navigating in an outline easy on a tablet like the iPad.
It's not finished, there's still tweaking to be done, but I wanted to get an idea of how it works for people before going further.
To access the arrow pad, choose the command from the Outliner menu.
Screen shot below.
There are two buttons and four arrows.
The leftmost button says either Navigate or Reorg.
If it says Navigate, the arrows move the cursor.
If it says Reorg, the arrows reorganize the outline.
The arrows move in the indicated direction, when you click them.
The rightmost button says either Expand or Collapse.
When you're in text mode in the outline, the arrow pad automatically goes into Reorg mode.
Pretty sure I found and fixed the problem that was causing some files to become encrypted without the user deciding to encrypt them. If you were experiencing the problem, and found it reproducible, please let me know via a comment here, whether this fix worked or not. Thanks!
The Outliner menu was getting too long to fit on a laptop screen.
Solution: Create a new menu with the reorganization commands separated from the other outliner commands.
There are six commands in the new Reorg menu:
Move Up
Move Down
Move Left
Move Right
Promote
Demote
There's a new checkbox in the right margin that shows you whether or not the active outline is encrypted.
It's only visible for editable outlines, and if you've set an encryption password.
The checkbox is still present in the Outline settings dialog because there are circumstance where the right margin is not visible.
Update: 1.22a fixes a bug in the code that displays the checkbox. It was reporting a file was encrypted even when it was not.
It's possible that the keystroke problems in the with Firefox with Fargo's Find and Find again commands are cured in this release.
In previous versions, when you pressed Cmd-G, Fargo would do its Find again thing, as it's supposed to, but the browser would also try to do a Find of its own.
I got some help from the developer of keypress.js, David Mauro, and implemented his suggestions in 1.21.
If you had problems with Firefox please say if it works or not (and of course if any new problems are introduced, speak up as well).
I thought I had Find working but it didn't work for Ron Chester's outline.
Turns out he had lots of headlines with the same created attribute.
As noted, the Find command was assuming that this attribute could be used as an identifier, but clearly that wouldn't work in this case, so I rebuilt the Find command without making this assumption.
I've asked Ron to check it out and let me know if the new version works.
Fixed a bug in Find again, where it would always loop back to the top in certain circumstances. The error was ridiculous, and I went looking in the wrong direction for it, so it took a lot longer than it should have to fix. Still learning how to do this programming thing.
One caveat, the way Fargo tells when it's reached the cursor headline is by looking at the created attribute on headlines as it's searching. If the cursor headline does not have a created attribute, we add one. Under normal circumstances it's put there automatically by Fargo as you enter text into your outline, however if you copy/paste from another outliner into Fargo, or import via OPML, it's possible headlines won't have this attribute.
It's possible if you have two headlines with exactly the same created attribute that the Find command could get confused.
In its first release Find would stop when it reached the end of the outline. If what you were looking for was above you, it wouldn't find it.
Now when it reaches the end, it starts over at the beginning.
Find and Find-again
This feature has been waiting until we could figure out how to capture Cmd-F and Cmd-G, instead of having them be caught by the browser.
Perhaps now we have a way to do that. I'm using a package called keypress.js. It works on my machine, Chrome on the Mac.
So for this release the question is this -- when you press Cmd-F (or Control-F on Windows or Unix) do you get a dialog asking for a string to search for?
When you press Cmd-G does it do another search from the cursor position?
Thanks to Tal Safran for the clues.
Compatibility
There may be issues in some browsers with the keystroke invocations, if so, use the menu commands.
Works well in Chrome and Safari, not so great in Firefox..
Find command documented
Invisibly...