are you saying my proposal doesn't fix my problem or are you saying that my issue isn't actually a problem?
Both.
It doesn't fix your problem and your issue is not a problem.
1. Your issue is not a problem:
In the first minute when you switch from a keyboard to another (with a different layout), you may indeed press a wrong key and insert a few characters into the document you are editing.
It happened to me when switching from a SpaceFN keyboard to a standard TKL. I ended up with a few " jjjj i" in my text.
I pressed Ctrl-Z (undo), re-focused on the fact that I was on a different keyboard, and that was all.
Any software that is not desperately obsolete allows to undo the last characters typed. Even a command line allows it (with backspace!).
The fact that your proposal allows to mistype the arrows without inserting spurious text is a very minor advantage of it.
And it is not even an advantage at all because...
2. You don't even fix the problem:
Navigating thru a document does not involve only the arrow keys.
The first thing you may have to do in a document is to press PgUp or PgDn. Or press Home or End.
You will have to put these functions on keys that generate characters. And you will get spurious characters in your document when you switch to a standard keyboard and forget about it.
Or you will have to use the modifiers on the other side of the keyboard, forcing the use of two hands for Home/End/PgUp/PgDn.
Or you will have to add an Fn key at the left of the keyboard.
4 keys are used for pressing cursors in my proposal: winkey, menu, ctrl, shift.
you can spam any of those keys all you want; you'll never accidentally insert an error into your document. As well, correcting any mispressed keys is only a single keypress MAX (press winkey to clsoe the start menu, press menu to get rid of the menu).
I suspect the reason you prefer your solution is that keeping your hands on homerow is priority #1. My solution is optimized to prevent errors that happen because of different keyboard layouts (when there is no AHK available). does everything make more sense now?
I don't know why you insist on this. SpaceFN has NOT been designed to keep the hands on the home row. It has been designed to use the space bar as a big Fn key, allowing the use of a totally standard layout (the typewriter cluster of a standard PC keyboard) for a 60% board that does all a standard full keyboard can do.
It just happens that it allows to keep the hands in the home position while navigating. If you put your right thumb on the space bar, you will notice that your fingers rest naturally and without effort where the navigation keys have been put in SpaceFN. The J key has also the advantage of having this little tactile bump that makes it easy to find without looking at the keyboard.
But the main thing is: manufacturers insist on adding useless Fn keys, when we already know that space can be used for that. I have not invented this. Matias has worked on the concept a long time ago, and space is commonly used as an additional Shift by many people (I think they call this SanS). Instead, we see Fn keys popping out in ridiculous places, and even eating the space bar, maybe trying to replace it because it is so conveniently placed under the thumb.
There is an obvious simplification waiting to happen here: if you are going to have an Fn layer, just use space as the Fn key. We know how to do this. It works very well.
EDIT:
let's be clear; I'm not here to push an 'agenda' or anything. like the topic says, this is for brainstorming about (plural) layouts. As you know, matias has been doing alot of work with 60% layouts. If any manufacturers large or small decide to be adventurous; it'd be nice if we had spent some time talking over new layouts before they decide to go into production or hit some other hard business commitment.
isn't it kinda pathetic that the entire keyboard market can't match up to the layout efficiency of apple's chiclet boards?
Maybe it's just me, but I don't find the Apple's small aluminum keyboard very efficient. I have one, I have used it for a while, but switching to a mechanical TKL later has been an incredible relief.
I don't know if Matias has done a lot of work with 60% layouts. He doesn't sell any at this time as far as I know. He said he had a design with dedicated arrow keys but I have seen nothing yet. After trying to design such a layout myself, I'm skeptical about it. You get either an overcrowded keyboard with ridiculous short Shifts (Minila, Pure Pro, ...) or an unjustifiable Fn layout with a poorly placed Fn key. Or both.
I agree that we need to work on a solution for 60% keyboards, because the manufacturers are unlikely to produce a good one. It should be clear now.
But when you suggest an idea, you expose yourself to a lot of criticism, justified or not.
Some time ago, before SpaceFN, I have suggested a layout for a 60% board with dedicated arrow keys, using exactly the same number and layout of keys as the typewriter cluster. In order to achieve this, I had to move one character. It has not been well received:
http://geekhack.org/index.php?topic=47888.msg1023617#msg1023617(I have just noticed that you had participated in this thread, I did not remember)
It was not an idea that I had a few minutes before posting. I had been thinking about it for days and even tried it myself with a software simulation.
So before you post an idea and defend it like you do, you'd better spend a lot of time validating it in private. Or just accept that you are brainstorming and that an idea that looked great on the surface does not stand the test of reality.