I'm not trying to fan the flame at all, but I did want to mention why I'm using emacs for all my actionscript development. I tried eclipse with asdt and the cvs and subversion plugins, and don't get me wrong, they're nice, but I found that the keybindings didn't match my taste, and I couldn't customize them to work right. If you're used to using emacs, your fingers don't ever have to leave the keyboard to use the mouse, which can vastly improve your development speed. And then there was the issue that there didn't appear to be a recenter buffer command, which I find very helpful. So I thought I'd write one. Many hours later I gave up, because with all the eclipse platform layers I found it difficult to get started.
Emacs is easy to customize, if you know lisp (which I learned years ago at school), and it runs on multiple platforms and even across ssh terminals. It took me about an hour to get it to work well using ant for building, as one example. Yes, that's built-in with eclipse (or you can use as2ant), but my main point is that it's easy to extend. I wouldn't recommend emacs to anyone who is just starting and looking for a flash editor (FlashDevelop would be much more appropriate), but if you've used emacs before, you should just know that it's quite possible to use it for actionscript development (and austin's blog has some great info on how to do it). The other thing I didn't like about eclipse is that even though I didn't use it that much, I would occasionally run into lockups and crashes. I think these were caused by the plugins and not the environment itself, but it still felt very much like opensource software. And like many java IDE's, it takes a ton of memory. --Brian On 12/30/06, Scott Hyndman <[EMAIL PROTECTED]> wrote:
On 30/12/06, hank williams <[EMAIL PROTECTED]> wrote: > Hi Marcell, > > Personally, I think its insane. > > Using one editor for everything gives you a lowest common denominator editor > rather that a best of breed for the language. Just a quick comment on this. You should really look into the Eclipse plugin system. I don't think it's quite as limited as you believe. Creating a new editor in Eclipse (such as FDT editor, which is completely disjoint from the JDT editor) gives you the flexibility to add any feature you can possibly imagine. No lowest common denominator because you don't have to share code with the rest of the system. All it takes is implementing a few interfaces and talking to the rest of Eclipse properly. Scott _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
