I'll continue to maintain IAT! as long as it can work in Firefox.
Firefox is changing its security model for extensions to make it more like Chrome's. Eventually, it will be impossible for IAT! to work as a pure extension anymore.
Over the years, I've been working on IATED (https://github.com/docwhat/iated) which was meant to be a replacement for IAT! -- a sort of IAT! next generation.
IATED would be two parts: a server to open the editor and an extension that talks to it.
But I've become distracted and disheartened by figuring out how to make it as simple to install and use as IAT! yet remain secure.
Some issues:
* I know enough security practices to know I'm not even close to being an expert. IATED has the potential to do really bad things if insecure. Letting a malicious page read random files on your file system (or worse, write them!) is the obvous vector.
* I would want to support the same platforms: Linux, OS X, and Windows. But each platform has very different requirements. Windows users are going to be confused if IATED is purely command line driven, for example.
* What language should I write it in. I have several false starts, with the current 'master' branch being JRuby. But depending on the JVM seems horrible. 'golang' is pretty new and maybe the way to go. I'm not sure.
* I work on IAT! mostly alone, though xOneca has been a great help. Writing IATED by myself is discouraging. I'd love to have someone who knows about golang or Windows or security help me write IATED.
Anyway, that's roughly the state of IAT! and IATED at the moment.
I use backtick. It's great not having to reach for a control or alt key to change window.
It is a minor annoyance in markdown but in shell programming I use `$(...)` instead, since it can be hard to tell if a character is a backtick or a single quote.
The important bits are vim's built-in omnicomplete and neocachecompl
Omnicomplete by itself isn't bad. I haven't seen any excellent documentation explaining how it all works, but even without my .vimrc I use C-X-f a lot to complete filenames.
I don't like the suggestion. It enforces a 1:1 relationship between controller and model.
I'd rather have the model and the ORM be pulled apart and the model make this distinction.
Or create another class that knows how to safely pull values out of a params list and use it to create a model.
But it's bad enough that the controllers "look" like they belong to a model in default Rails generators. This creates a certain amount of laxity in programmer's thinking. It boxes their thinking in instead of letting their thinking go free.
Hi! I'm working on making It's All Text! work with Firefox 3.6. If you have troubles (such as right clicking on gumdrops) then turning on "Remove all bugs" actually does what it says, for a change. o_O
I looked at doing a chrome version of "It's all text!" but chrome doesn't have a way to launch an external application short of creating an NSPlugin. Which I'm not sure I want to have to support across all the chrome platforms.