I had a brief play around with the example, and pretty quickly came across bugs and unimplemented commands (for example: 'b', 'e' and 'O' are missing, but 'o' acts like 'O'). I like the way the cursor changes colour to hint at the current mode. However, what I'd really love would be a bookmarklet I could click to Vi-ify every on the current page. I've got "It's All Text" set up in Firefox to open s in gvim, but it's…
The Pentadactyl plugin for Firefox ( http://dactyl.sourceforge.net/pentadactyl/ ), which is a better-maintained fork of the well-known Vimperator, allows you to hit in any textarea or text input to enable Vim-style keybindings inline. opens the text for editing in an actual Vim instance, like the plugin you mentioned. Of course, Pentadactyl changes a lot about how the browser works beyond just text editing, so it may…
Web Vi
21–27 of 27 posts
Re: Web Vi
#22Re: Web Vi
#23The one thing that most vi-mode implementations don't get is that vi(m) is really about the possibility to configure every keystroke. Its not about "j" is "up" and "dd" deletes the current line.
But in seriousness, although I agree about the importance of configurability, I still find that things like "j is down" and "dd deletes the current line" are an important, integral part of the vi-philosophy.
Placing the most common tasks behind the easiest key-bindings for maximum efficiency and ergonomy is the idea that got me to try out vim in the first place.
I like that someone (Bill Joy and Bram Molenaar) has solved the most common issues in editor-usage in a great way leaving me to configure only some special cases.
Re: Web Vi
#24Keybindings are way off on non-qwerty keyboards.
Re: Web Vi
#25Here's another example of vi being completely exported to Javascript, but without the canvas element. http://gpl.internetconnection.net/vi/ What disappoints me about all these implementations is the absence of text objects, though. I love getting edition words or parentheses using commands such as caw and ci"
I'm the author of that vi.
What are "text objects"?
PS: "caw" and "ci" aren't in vi.
Re: Web Vi
#26I'm rather skeptical about text editors implemented on top of the canvas element. Mozilla has already tried that with Bespin project and it failed miserably (huge code base, poor performance, limited accessibility). Wouldn't it be easier to just use div element with contentEditable attribute? Currently contentEditable has limited API and a lot of inconstancies across browsers, but in the longer run it seems to be the…
I'm also skeptical about canvas, so when I implemented my own jsvi years ago (at http://src.internetconnection.net/vi and now at http://geocar.sdf1.org/vi ) I didn't use canvas. It works everywhere but chrome (which won't let me capture escape), and it produces the same results all the way back to MSIE6.
In retrospect, I would've had an easier time overriding keystrokes on a textarea.
Re: Web Vi
#27I had a brief play around with the example, and pretty quickly came across bugs and unimplemented commands (for example: 'b', 'e' and 'O' are missing, but 'o' acts like 'O'). I like the way the cursor changes colour to hint at the current mode. However, what I'd really love would be a bookmarklet I could click to Vi-ify every on the current page. I've got "It's All Text" set up in Firefox to open s in gvim, but it's…
The Pentadactyl plugin for Firefox ( http://dactyl.sourceforge.net/pentadactyl/ ), which is a better-maintained fork of the well-known Vimperator, allows you to hit in any textarea or text input to enable Vim-style keybindings inline. opens the text for editing in an actual Vim instance, like the plugin you mentioned. Of course, Pentadactyl changes a lot about how the browser works beyond just text editing, so it may…