Slashdot Mirror


Jedit, Jext & J: Java-based Editors Compared

An anonymous reader writes "There are times when I want a lean, mean editor and times when I enjoy a good, bloated editor packed with wizards. We compare the programming editors Jext and J to Jedit and offer a revised opinion of the best Java for Linux."

23 of 97 comments (clear)

  1. jEdit rules! by bryanthompson · · Score: 2, Interesting

    I luve jEdit. When you get a set of plugins for it you really like, there's no beating it. of course... I haven't used one since i started using jEdit, so there may be something better these days.

  2. A few comments about jedit by sosedada · · Score: 5, Informative

    I was reluctant to try out a java based editor (I'm a C++-er all the way :), but nedit was acting strangely as packaged in Mandrake 9.0, so I gave it a shot.

    I really like the hyper-searching and the tabbed windows. There are a few annoyances such as the order it uses when you switch to the next buffer (uses opened order rather than Z order), but my main complaint lately has been speed. It has become quite a hog, probably due to too many cool plugins. I'm using the latest java from Sun. Perhaps I'll try one mentioned in the article.

    All in all, I've been using it for about a month and I don't think I'll give it up.

  3. i am not compelled by amorico · · Score: 5, Insightful

    Summary:
    J: interesting and--Oh look! shiny php object!
    Jext: tricky installation, but nothing interesting in the five seconds I spent reviewing it.
    jEdit: reviewer liked this one the most, but was biased from the beginning.

    Whatever. Why waste the time to even write a review if you are not even going to take the time to go into depth? The reviewer complains about bloated IDEs like eclipse or netbeans and then does not even point out why ANY of the reviewed editors are a compelling choice over an IDE. Eclipse and Netbeans make enterprise deployment, unit testing, and building a lot easier because they were created with that in mind. They only implement editing functions to the extent that they support iterative development cycles and integration with software engineering tools. Do the editors support automatic code copmletion based on classpath and in-scope variables? If I wanted souped up text editor I would use emacs or vi, whiach are FAR better than this j* stuff. An editor is great when you are developing alone, but when you are part of a team of developers, things like CVS integration, code style enforcement, and automation of repetitive build tasks are essential. How do any of these editors fare in that respect? You'll never find out in this review.

    -a

    --
    "The plural of anecdote is not data." -- Roger Brinner
    1. Re:i am not compelled by jilles · · Score: 3, Informative
      You really should check out Jedit. It has plugins for all the things you mention and much more.

      To highlight a few things:
      • syntax colouring for at least 60 languages built in (could be more by now)
      • Plugin support for nearly every programming related task you can think of (debugging, style checking, refactoring (was not finished last time I checked)?, code completion, code fragment insertion, project management, catching output from console, testing, ant integration, ...).
      • Even without plugins it is still a good editor that can support various keybindings of other popular editors (vi and emacs I think)


      Understandably, people are biased against java client software. However, Jedit is worth the 10 seconds it takes to launch it. Aside from emacs, I don't think there are many editors which are that extensible and have that many extensions.
      --

      Jilles
    2. Re:i am not compelled by Mr.Ned · · Score: 3, Informative

      For my meager and small perl programs, I've switched from vim to jEdit. Just a really nice program. Syntax highlighting is very good but not quite up to par with vim. Little things are still missing, like coloring newlines/tabs differently than text. Bracket auto-completion/auto-formatting that highlights which bracket is being closed lets me work more efficiently. There's a nifty collapsable blocks setting that will 'minimize' a block, enabling me to get a better overview of what is happening.

      jEdit also has a plugin-architecture with quite a library of plugins, including a mini-console, CVS integration, save over FTP, and a slew of Java-centric ones that look as though they would be useful.

      In short, jEdit isn't an IDE but it will help you out in terms of "CVS integration, code style enforcement, and automation of repetitive build tasks." And it's not just for Java.

    3. Re:i am not compelled by Anonymous Coward · · Score: 3, Informative

      > Little things are still missing, like coloring newlines/tabs differently than text.

      Get the WhiteSpace plugin through the plugin manager. It lets you pick separate colors for spaces, tabs, other whitespace, space from folds, and paragraph separators.

    4. Re:i am not compelled by bwt · · Score: 2, Insightful

      Eclipse and Netbeans make enterprise deployment, unit testing, and building a lot easier because they were created with that in mind.

      jEdit has plugins that do just about anything you might want in that area: CVS, jUnit, Ant, java parsing, coding standards, in-process compilation, XML parsing, XSLT transformations. It's "hypersearch" capabilities are the best I've seen.

      You can script jEdit in Beanshell or Jython. The "Commando" feature is as amazing as it is hard to decribe (you define XML to present GUI wizards for launching commands).

      I would use emacs or vi, whiach are FAR better than this j* stuff.

      BS. I'm so tired of hearing how great emacs and vi are. Both SUCK. Both have a completely unacceptable learning curve and are examples of the kinds of of arcane user interfaces that should be *ridiculed*, not advocated. Many people making fun of MS for clicking "Start" to shutdown had to hit shift-ZZ to save their file. And that's as console applications.

      Hello, it's time to get with-it and edit text in a GUI. And don't talk to me about "when I telnet into a box I can't use a GUI". Freaking learn the -X option on ssh or better yet, use an editor that supports remote editing. And don't talk to me about gvim.

      People that like them have some kind of desparate psychological need to justify the endless hours of torment they spent years ago learning them. To these people I suggest using jEdit in VI key-binding mode (oh, and pocket protectors are no longer in style).

  4. Why I gave up Emacs... by dmorin · · Score: 3, Interesting
    XML. I was never happy with the XML modes I could find for Emacs. And, as a Java geek, I'm doing alot with XML these days. So I decided to give JEdit a try when I heard that it had good plugin extendability. It's XML support is quite nice.

    But! That's the only reason I use it. When I need to write Java code I still go with Emacs and the JDEE package from Paul Kinnucan which gives me everythign IDE-like I could ever want.

  5. Windows has better editors/IDEs by kruetz · · Score: 4, Interesting
    Unfortunately, I dislike all three of the above editors in favour of JCreator - a Win32 IDE for Java. I KNOW this article is about editors for Linux, but hear me out on this one.

    JCreator is small, fast and has all I want in an IDE. It is written in C++ and behaves very much like VisualStudio, which is great if you're a windows programmer. Personally, I run dual boot CRUX 1.0/WinXP and if I'm gonna write a good amount of Java code, I choose XP and JCreator, because JCreator feels so much faster than any Java-written IDE/Editor. JCreator is freeware (there is a Pro version for as little as US$35) and I'd love to see a Linux version - I have emailed them about it and it's not gonna happen anytime soon. Damn.

    But anyway, there is a big difference between JCreator and Java editors for Linux. I'd like to see a JCreator-like project at SourceForge or something, because I'd definitely use it. (I'm not gonna contribute myself - I'm already working 60+ hrs a week). Does anyone else feel the same way?

    --

    This sig intentionally left bla... dammit!
    Who's got the whiteout?
    1. Re:Windows has better editors/IDEs by KDan · · Score: 2, Insightful

      First feature from their site's "Features" section:
      Selection margin with line numbers. JCreator gives you the option of viewing line numbers in the selection margin.

      When the feature list starts with this, I start to get worried. Looking at the rest I see that was justified. There is no mention of refactoring tools, and though of course I can't really comment since I haven't used JCreator, from the feature list it seems very similar to Gel, which is also free and windows-only.

      The idea of an IDE is not just a nice Java-oriented editor. You're right to switch from vi to JCreator and not to Eclipse or NetBeans, cause those are far more than editors. I hate the way Eclipse is so slow and unresponsive compared to my good old KDE apps, but "as-you-write" compilation, the refactoring tools, JUnit tests integration, seamless and easy integration of jars for code-completion even if you don't have their sources, etc... all these make IDE's come out miles ahead of straight editors or "editors+IDE-like-frills".

      I'm just waiting for the time when I have a faster computer so that Eclipse runs a bit more smoothly (P3 550 sucks), but I've tried many other methods and proper IDEs are definitely tops.

      Daniel

      --
      Carpe Diem
  6. You don't know jedit by xagon7 · · Score: 3, Informative

    ...there are NUMEROUS plug-ins for ANT, JUnit console, editing macros, and even EMACS emulation. YOU should know what your are talking about before you open your fingers. JEdit is well one its way to being a fantastic programmers editor. The editor is EXACTLY the same on a MAC, Linux box (any type), or Windows. Just get the latest version and try for your self. It is especially snappy with the 1.4_01 jvm, and go to the plug-in manager and BAM, tons of stuff. Have fun!

  7. Re:Text editors by toga98 · · Score: 2, Funny
    The fact that we still use these beasts to develop software says a lot about our industry

    You mean that software developers need to edit text?

  8. Re:Text editors by KnightStalker · · Score: 3, Insightful

    Hm. You can draw pretty lines in UML all day long, but at some point the behavior that UML is representing has to get turned into ones and zeros that your processor can execute. Even if you have large libraries of predefined modules, you still will not have any sort of flexibility -- unless you whittle those libraries down to the level of source code.

    And I think I'd rather use a text editor to type "for(int i=0; i<10; i++) { ... }" than drag a "Loop" module into my diagram and fill out a dialog box.

    --
    * And remember, it's spelled N-e-t-s-c-a-p-e, but it's pronounced "Mozilla."
  9. So what's wrong with text? by 0x0d0a · · Score: 3, Interesting

    Okay, I had to look this one up. It seems that EUML is pretty much what it sounds like -- some companies trying to build a really high level language -- fine, that I'll understand -- using UML, which comes off as a bad idea. Frankly, the whole thing smacks of a "solution without a problem" being aimed at corporate purchasers who think "UML == good, so EUML == good".

    First, I'm not a tremendous fan of UML. While the next generation of languages may hit within a decade, I'm not holding my breath, and I rather doubt that they'll be based on UML.

    Second of all, I don't see why you dislike text so much. You can have the benefits of EUML without going to some mouse-based development environment. A text-based system would work fine as well.

    Third, text is well understood by now. Text is stored in a standard format, and there are extremely powerful tools available to process it. Furthermore, it survives interchange fairly well, deals well with different output devices, and can be printed easily. There are a number of excellent, extensible text processing systems like emacs.

  10. Re:gvim ? by KDan · · Score: 3, Informative

    It's not java based, so you either have to go through no end of hassle to make it work on your windows box, or get used to "one editor for *nix, one editor for *blows".

    JEdit, on the other hand, runs fine and exactly identically on both linux and winblows. No need to get used to having one set of feature under one OS and another under the other.

    Daniel

    --
    Carpe Diem
  11. Re:gvim ? by Anonymous Coward · · Score: 3, Informative

    Ummm, you can get Vim for Win32. I use it all the time just as in Linux. It's not a cygwin port, either, it's a legitimate Windows program. See here.

  12. Re:Text editors by jilles · · Score: 2, Interesting

    I'd have to agree. Using ascii to store highly complex structured information is rather foolish. It results in all sorts of problems with respect to consistency, correctness, etc.

    We have much better ways of storing and editing structured information these days.

    --

    Jilles
  13. Re:Editors written in Java? by jilles · · Score: 2, Informative

    It seems that your sysadmins need to get a clue. Don't blame their victims.

    Setup the server in such a way that client computers can easily access files on it (e.g. by running samba). Running stuff locally is almost always faster so there must be something preventing the developers from doing so effectively (I suspect an overzealous attitude towards windows clients). Remove that cause and your problems are gone.

    The sysadmins are costing your company money at the moment because they prevent a development team from working with the tools they need in an effective way.

    --

    Jilles
  14. Fonts for Programming by n3bulous · · Score: 2, Interesting

    Fortunately, the Verdana font looks fine in Jext without anti-aliasing, so that's what I use

    Do people really use proportional fonts when writing code???? I use andale mono or Lucida Console, myself. I love that the code looks cool with proportional fonts, but nothing ever lines up properly.

    --
    "The area of penetration will no doubt be sensitive." ~ Spock
  15. IntelliJ IDEA by zjbs14 · · Score: 2, Informative
    If you've got some money to spend, the best IDE for any language I've used it IntelliJ IDEA: http://www.intellij.com/idea/. After using it, nothing comes close.

    --
    No sig, sorry.
  16. jEdit is still rough around the edges by Trinition · · Score: 2, Informative
    I've been using jEdit off and on for a year now, most recently very seriously. jEdit is still quite ugly in some areas, but quite nice in others: Nice:
    • 100% Java
    • Nicely done Win32 laucnher
    • Tons of plugins
    • Nice and easy way to install/update plugins
    • Concise, Java-based installer
    • Configuration is extensive
    Not so nice:
    • No javaWebStart link available
    • Icons are ugly
    • Toolbars/docking is very fixed and wasteful
    • No hex editor! (not even a decet plugin)
    • Configuration organized haphazardly
    Disclaimer: I use jEdit as a text editor, not an IDE
    1. Re:jEdit is still rough around the edges by insac · · Score: 2, Insightful

      May I add that they've created an excellent "stand-alone syntax highlighting text editor JavaBean." (jedit-syntax at sourceforge)?

      I wanted to add "scripting support" to my application, but I wanted to have syntax highlighting (so it looked more professional :-)

      I had to change 5 lines of my code and I had my syntax highlighting editor.

      A really useful component and an excellent example of "component-based reuse".

      P.S.: maybe it's just a bit off-topic, but since we're developers I guess it's still an useful info.

      --
      This message doesn't need a sig
  17. Re:the best of Java for Linux ? by MillionthMonkey · · Score: 3, Informative

    A 'Hello World' applet run using appletviewer. Ok cpu usage is at 0.0% which is to be expected since the applet doesn't do anything once it's painted the display, but look at RSIZE. 13.4M.

    Yeah, that's the VM overhead, so?

    And you can expect that number to blow out pretty quickly as the code is extended to make it do something useful.

    I assume that adding features in your favorite language actually causes memory use to shrink?

    Hello World in C has a resident size of 304K. Granted that's just using printf to output to a console but it's still a dramatic difference.

    Actually, 304K seems like a hell of a lot of memory to lose for a Hello World in C.