Assuming I made no mistakes, then it should appear shortly.
The big changes are that it supports Firefox 4.0b7. In addition to that, I have fixed some of the problems with OS-X. In part because the ability to launch applications in Firefox is becoming more annoying with each release.
But not to worry! I’m working hard on IAT2.0. The next version will be broken into two parts: An editor server and the actual plugin.
Why do it that way? Well, it provides better control over the editor application. It also allows me to port it to Chrome (and possibly other browsers, like Safari).
The downside is that after installing IAT2.0, you’ll have to download an application and have it running.
I’d love to hear feedback on whether that is too evil or too much work. Or if it’s just fine and dandy. I’m working hard to try to make sure the editor server is easy to install and use, so hopefully I’ll minimize any problems.
why so much work? Your plug-in works fine in my FF portable since 1.4.2 (first installation). As editor I’ve integrated (also portable on the same stick) the nice little win32pad.exe. No problems!
Thank you for your work! Very helpful!
I have several reasons:
- The editor control is tough
- The amount of effort to keep the complicated execution and refresh checking code working as FF updates is annoying.
- Cross platform compatibility for the editor portion is tough.
- I want IAT to work on chrome and other browsers.
- IAT is too complicated
For me, as a developer, this is worthwhile. I’m just uncertain if the gains are worth it for the users of IAT.
If you can make this work in Chrome on Linux, that would be truly awesome. I can’t tell you how often I am working in Chrome and then have to launch Firefox just to use your handy extension. As a developer, being able to write ticket descriptions and comments in my editor of choice rather than a text area is solid gold.
This is a great extension and brilliant idea!
But I have problems to use it on my MacOSX(10.6.5)+FF3.6.12. It worked for a while when I downloaded and installed in the first time. After sometime all functions just don’t work, no icon beside textarea, no shortcuts. I tried to use different editor shell and others, but that didn’t help.
These days I’ve updated to latest version of 1.5, but it still don’t work. I think i’ll do some debug with source code to check wha’ts going on.
That’s really odd. Are there any messages in the console? You can turn on debugging messages by setting extensions.itsalltext.debug to true.
This is just on time. I was looking for IAT for Chrome, didn’t find it, read this post and everything is fine. Sort of. Is there a date on the 2.0 release? I’m kinda lusting for IAT on Chrome.
Great, can’t wait to use IAT for Chrome.
Thanks for the news
Hallo Christian, why so much work? Your plug-in works fine in my FF portable since 1.4.2 (first installation). As editor I’ve integrated (also portable on the same stick) the nice little win32pad.exe. No problems! Thank you for your work! Very helpful! Holger
Probably the easiest is to right-click on the edit button, and add a new extension, such as “.js” so gvim knows how to highlight the file.
Greate work, thanks. I’m looking forward to the one which can work on Chrome. Thanks!
If you are looking for an equivalent for Chrome / Chromium, some alternatives are available here: http://superuser.com/questions/261689/its-all-text-for-chrome