I’m pretty savvy with JS. But Firefox has it’s own rules when writing things that can access the “chrome” parts. I *think* that the main problems are in cache.js, which is what adds the button, writes out the md5-hash, etc.

Even worse, IAT doesn’t work with FF 3.6 and I don’t understand how to troubleshoot and fix what’s wrong. *sigh*

I’d love to port this to Jetpack or Google Chrome, but I’d need to write an NSPlugin to do the actual editor invoking — There are no ways to call out to the editor from within these environments that I can see.

And I really don’t want to write and maintain an NSPlugin.

I’d settle for a status bar icon that let me search for text areas on the current page. But as useful as IAT is, I simply can’t abide the performance hit.

Would it be possible to have an feature that would turn off IAT without having to to disable it, and which would allow re-enabling it as well.

As best as I can figure, it has something aggressively looking for text areas, but I haven’t tried really diving into it.

I have been told that IAT also causes bing.com to pause 5 seconds or so every load.

Ciao!

The main performance hit is when I focus on the window, though focusing on any text dialog seems to also have a delay before the browser is ready to let me type.

Since you mention tabs… I am also using the TreeStyleTab extension, could this interact with IAT?

Thanks,

-Peter

Interesting. I’m using the 3.5b4 and I haven’t really noticed this.

Some questions:

• What OS are you using?
• When you say focus on click, do you mean the whole browser or just when focusing for TEXTAREAs? The two times that IAT does something is:
  1. When you mouse over or click a TEXTAREA.
  2. When you change the tab.

Please let me know if there’s anything I can provide to further troubleshoot this.

Currently I’m using FF 3.5b4, and IAT 1.3.1.

Thanks,

-Peter

Here is the timeline.

1 – User hits edit.
2 – gvim session appears
3 – user edits file in gvim session, and writes the file out, exiting the editor
4 – the addon somehow causes the edit area to flash yellow, indicating the edit is received.
5 – something dumb happens like the browser crashes, or goes to a new page automatically and crashes without submitting the text, or the session is lost and some javascript causes the page to change.

Maybe I misunderstand and there’s really a step 6 where I restart the
browser following the Dumb Thing, and that causes it to delete all the temporary files? I don’t know what the timespan of these files is,
but I’d prefer it to be infinite.

Actually, it isn’t deleted. All the files are marked as “temporary” by firefox. If it crashes, temporary files aren’t cleaned up.

You should be able to right click on the “edit” button and select “Edit using previous ‘.txt’ content” (obviously .txt will be whatever extension you edited it as).

If something has changed so that temporary files are being deleted even after a crash, then I’ll take a look at it.

Ciao!

Unfortunately, ItsAllText doesn’t really clean this up all the way. If
ItsAllText hands the text back to the browser, and then the browser crashes,
ItSAllText has already deleted the data.

Can I disable the delete? I’m perfectly capable of cronning a cleanup.

-josh