Textarea, You Are A Sunken Nothing
web.archive.org
web.archive.org
http://en.wikipedia.org/wiki/Dark_Avenger#Dark_Avenger.27s_v...
Sadly it doesn't yet work in Chrome, but the chrome team is working on it.
https://addons.mozilla.org/en-US/firefox/addon/4125/
(and mozex, which I used to use before that.)
It should be possible to write an edit-server for other editors that work with Edit with Emacs, if you are that way inclined...
Do a search for DefaultKeyBinding.dict, or just start with mine:
I searched all over, but I guess I just couldn't adequately describe what I was looking for to Google.
https://addons.mozilla.org/en-US/firefox/addon/4125/
'Edit textareas using an external editor, because it's all text!'
well, I haven't really thought about it, but, yes, textarea is pretty ugly. and try to make it better (with weird wysiwyg javascript libs) can end up worse. hail _why.
not in my firefox :(
It's coming in 4.0! They've added support for the CSS "resize" property, and set it to "both" by default. Just like WebKit.So yeah, but that's not actually a slam of FireFox, weirdly enough.
I was referring just to the street address part, though, which is almost always entirely freeform, or at least is up to complex and opaque rules that vary by city. This is what textareas are for: unstructured input of a string (not prose writing, but simply a string) that may require newlines in it.
Coming right after the street address field would, of course, be separate single-line input fields for the city, country, etc... but the street address itself should allow as many lines as you need.
And then, you get different countries. And shit hits the fan hard.
So was I. Every system my software communicates with has an "Address1" and "Address2" field. Ok, some only have an "Address" field. They don't except newlines and most of the time those fields are limited to 50, 100, or 256 characters.
House Name, Road, Village, Town, County, Country (if applicable) Post Code.
My address structure is:
Flat Number - Building, Road, City, Country, Post Code
Some multi-input address forms require that I enter both a city and a county, which in the case of Londoners means you end up putting London twice. The only important parts of the address (for most uses, including credit card processing) are recipient name, house/flat name/number (actually, not sure about this - it might not be necessary) and Post Code.
So why not just have explicit inputs for those fields which are always required, and allow a more fuzzy input for everything else in the form of a textarea? It also means you're more likely to be able to deal with addresses in countries that use slightly different systems.
First/Last name Card number Expiry Date Billing Zip
The rest of the fields on https://signup.37signals.com/basecamp/Plus/signup/new are unrelated to billing.
Worth noting that those extra billing fields like address and all that help cut down fraud (as well as signups...) so if your business is not b2b and relatively fraud-free, you probably should keep the extra fields for anti-fraud checks.
We have a 4 way browser war, yet no one wants to improve the basic textarea. W T F
I think Google might have the right idea; the new version of gdocs completely ignores the browser's built-in (broken) selection and editing abilities and instead uses pure JavaScript listening for mouse and key events.
Downside: Ctrl+i doesn't work on the Mac. Anyway, it makes my working for the man a little less disgusting.
Anyway, I'm not using the -f flag. If I do, MacVim won't push the data into the textarea. It works with :x Cmd+q, though.
Thanks again. That will be a great timesaver in the years to come(;