[Neo] Nutzt niemand Eclipse?

[snneo]

Hi,

ich komm jetzt wieder nur, weil ich was will ;)

Das war schon immer so, dass die Pfeiltasten-Ebene 
(ka. welche Nr das wieder ist) 
bei Eclipse nicht funktioniert. 
Übrigens genauso bei einem der empfohlenen 10-
Finger Übungsprogramme, das auch mit Java geschrieben ist.
Ich habe mir damals, weil es da nicht funktioniert hat, 
mit C# ein einfaches 
Übungsprogramm geschrieben - als ich fertig war, 
habe ich es dann nicht mehr 
gebraucht.

Allerdings finde ich es schon seltsam, dass Neo mit Eclipse 
nicht funktioniert - 
übrigens auch nicht mit Total Commander, der sich 
doch einer recht breiten 
Beliebtheit erfreut. In NetBeans dagegen funktionierts, 
genauso wie in Minecraft.

Da ich bis jetzt nichts über dieses Problemchen 
gelesen habe, gibt es 2 
Möglichkeiten: ich mache irgendwas falsch oder 
niemand benutzt die Edit-Ebene.

Danke und Gruß

Re: [Neo] Qwpr layout

[Daniel Horz]

On 03/18/2013 04:24 PM, Jameson Quinn wrote:
> - Easy-to-learn coming from Qwerty; only 11 keys move, and 9 of those 
> remain on the same finger.

Few differences are actually harder to adapt to, at least in my experience.

> - Includes custom-built dead key layouts for over 1000 possible unicode 
> output symbols or combinations.
>   - That means it's usable internationally, not just German/English. 
>   For instance, there's easy access to "ç", "ñ", "¿", and similar 
>   characters, and even things like "ð" and "ž" are available.

http://wiki.neo-layout.org/wiki/Tote%20Tasten%20und%20Compose

There’s some tables in there in case you don’t want to read the whole
german text. And you can find „¿“ and „¡“ on Neo layer 4.

> I wouldn't expect anyone who's already converted to Neo to switch, but I'm 
> posting this here for greater publicity, and also because there's a few 
> things 
> I've done which may be of common interest:

I think the biggest concern German users will face with your qwpr is the
lack of umlaut keys. Even though they’re nowhere close to being
frequently typed it’s just bad for writing German.

How good or bad your proposal is for Egnlish from an ergonomical
standpoint I’m not the right one to judge :)

> - I've made a couple of comparisons of different keyboards: 
>   https://sourceforge.net/p/qwpr/wiki/Comparison/ and 

„ç“ and „ñ“ are actually included in Neo (dead keys). See above.


Cheers,
Daniel

-- 
jabber/mail/sip: dan...@vandenhorz.de

“For every problem there is one solution which is simple, neat, and wrong.”

pgp key:
https://daniel.vandenhorz.de/key.asc (5A6A89E3)



signature.asc
Description: OpenPGP digital signature

Re: [Neo] Qwpr layout

[wettstein509]

Hello Jameson,

by chance, I was browsing around the Colemak site yesterday, and saw
your «Dead keys and xkb — oh my.» post.  As I have no Colemak account, I
could not comment, but now I have the opportunity: Do not implement dead
keys as XKB levels or groups.  Use the Compose mechanism in libX11.
Searching the web for «.XCompose» should give you sufficient information
to get going.

Regards,

Andreas

[Neo] Qwpr layout

[Jameson Quinn]

First: I apologize for posting in English on a German board. I'm currently 
learning a bit of German but I haven't gotten much past "Das Mädchen isst 
ein Ei" so I suspect the average reader here has better English than my German.

I've made a new ergonomic layout called Qwpr 
(https://sourceforge.net/p/qwpr/wiki/Home/) which is similar to Neo in having 
a second shift level on capslock which allows accessing punctuation (for more-
ergonomic programming) and arrow keys. In fact, I was not aware of neo when I 
made this layout, so I actually independently invented these advances. Qwpr 
also has a few advantages that Neo doesn't:

- Easy-to-learn coming from Qwerty; only 11 keys move, and 9 of those 
remain on the same finger.
- Includes custom-built dead key layouts for over 1000 possible unicode 
output symbols or combinations.
  - That means it's usable internationally, not just German/English. 
  For instance, there's easy access to "ç", "ñ", "¿", and similar 
  characters, and even things like "ð" and "ž" are available.

I wouldn't expect anyone who's already converted to Neo to switch, but I'm 
posting this here for greater publicity, and also because there's a few things 
I've done which may be of common interest:

- I figured out some tricks for PKL. For instance, if you want to output 
control-→ for moving an entire word, you can use "*{}^{right}".
- I've made a couple of comparisons of different keyboards: 
https://sourceforge.net/p/qwpr/wiki/Comparison/ and 
https://sourceforge.net/p/qwpr/wiki/effortComparison/

I'd be happy to get any comments you might have.

Thanks,
Jameson

ps. If you look at the current version of the layout, the dead key for German 
accents like "ü" and "ß" is on altgr-shift-quote (⌥⇧"). I'm planning to move 
that to unmodified semicolon (;), but I haven't finished those changes for 
uploading yet. The good thing about semicolon as a dead key is that in normal 
typing (both programming and text) it's almost always followed by a whitespace 
character. Therefore, if you make it produce a normal ";" when combined with 
such characters, you can use it with the rest of the keyboard for dead keys. 
Also, because this is the key for ":", it is a natural mnemonic for 
umlaut/trema/diaeresis.