* Start editing in Chrome
* It becomes long so copy-paste to Atom and edit there
* Copy-paste back to Chrome
To avoid this, I have then be using https://chrome.google.com/webstore/detail/wasavi/dgogifpkoil... to edit directly in Chrome but thought that it would be better to use a real editor rather than a subset, which is why I created this package.
I have an editor opened almost all the time, so pressing a shortcut and being able to edit directly there without copy-pasting around is actually saving me some time compared to my previous workflows.
But I don't see the advantage of editing text areas with atom, which presents an extremely similar text editing experience compared to the experience the text area already provided. On the other hand, moving to Vim to edit a particuarly long comment or what have you makes more sense because I get to use the crazy keybindings I've drilled into my fingers.
I have to take issue with your notion of "full featured". Atom is a fine editor with plenty of features but it's orders of magnitudes short of emacs.
Well, that's just rude. Atom is a customizable, programmable, featureful text editor. You can certainly believe that Vim is better, but you shouldn't think that on the spectrum from browser textarea to Vim, Atom is close the textarea side.
I suspect there are use cases where this makes sense, and, obviously, Atom is a more powerful editor than a browser textarea, though the key bindings may be similar.
If you are editing a gist or inserting a code snippet in a comment then editing in Atom would be nice because you get syntax highlighting, snippets, auto-complete.
What a cool idea.
I have some bugs open on the project and maybe someday I can switch from Vim to Atom comfortably.
I also hear that the It's All Text! author is lazy... every time I go home to the family. ;-)
Are you saying that you're its developer, and that you're not going to maintain it anymore?
That would certainly make me sad :(
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.
* 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.
For eg., you compile an email in Gmail, but edit it using Markdown in Atom (or whatever editor); the final content gets rendered as HTML. Effectively you are sending HTML email that was composed and edited in Markdown.
I never understood the appeal of markdown. Why would this be beneficial to you?
You want to use Atom's Markdown preview of a reddit comment or a github issue or anything else that takes Markdown.
You want autosave of a comment/input in case you accidentally close the tab, navigate away, or restart your browser.
You want to write code in a comment/email.
You want to use more advanced editing commands, things like undo-tree.
I find myself wanting simple, distraction-free plain text with no UI cruft for any writing more than a few sentences.
Personally I'm using either the Write Space extension for Chrome or Sublime today, but it seems like the author has the same use case, and with the added convenience of auto sync.
Things like GitLab, GitHub, Bugzilla, Wikis, etc.
You have a comma separated list of strings like
"one", "two", "three", "four"
and need to turn them into Markdown bullets
... an easy task for sublime or Atom
It happens rarely but when it happens, it hurts.
But I use many browsers, webapps reset the forms contents with JS etc. It's complicated.
Am going to use this for some aged web forms at work that have pretty hostile UX and that I often c&p into rather than bother trying to type.
There still isn't a good text editor that does regex find and regex replace (caret doesn't).
Every time I see a chromebook, I am reminded of those "Smart payphones", because they are as much of a computer.
They also support Sublime.
(I have zero experience with webkit to know if this is a reasonable undertaking.)
having been forced on a mac recently... just the fact i can't move my windows with <one key>+<mouse left button> is driving me crazy. and to add insult, the title bar that i have to hit to move windows is smaller then anything on browsers such as chrome and firefox.
i guess i saw something that reminded me of the cocoa/whatever-osx-UI on the the screenshots. but looking closer now, there is nothing other than atom and chrome, both have custom inconsistent UIs that do not hint the OS they are running on. you are right, it can be linux or anything else.
I personally use Divvy because Spectacle didn't exist when I first started using mac
This seems like a fun programming exercise with little real utility.
It would be really cool to have some kind of a bidirectional WYSIWYG for web design. Edit a text field in a Chromium window managed by Atom, and it makes the same change in your template file (or even JSX file). Edit something in your template, and the change is instantly painted to the browser window.
I know this wouldn't be trivial to implement, though.
this works today, really well. give it a shot.