Patrick that all makes complete sense, and I'll guess our experiences
are quite similar.
I want to stay using jEdit, but some of the bugginess and lack of
features (i.e. refectoring) causes me to start looking around.
I was frustrated with Java bean getters and setters a while back. I've
heard of no one who likes to type all that code out for POJO after POJO
(except maybe one jedit user on this forum.) I didn't like the way
jEdit did it out-of-the-box. After asking around, I found a bunch of
ways to do it. And, that caused me to customize a macro to do it just
how I wanted. That has sold me on jEdit for a bit longer. I love the
fact I can twist my editor into a balloon.
The time may come, however, that jedit and plugin development doesn't
keep up with demand of features and reliability. And, as ide's get
more powerful, demand will get stronger. I want to hear from people
why jEdit is BETTER than the ide's. What makes is better than xxx ide
for you? Or, are you thinking of jumping ship?
Blah blah. I'm not in a hurry to move off on jEdit. As I said, I'm
just looking for a community spirit sort of reset.
Thanks for your response
--- Patrick Wright <jedit_users@...> wrote:
> Interesting question. What I learned from my past experience was that
> every developer should have a standard output, and that it should be
> invisible to the other developers. If someone is using their own
> choice of
> tool, whatever it is, and their files are noticeably different from
> (or look unusual when loaded in other IDEs), people gradually get
> For example, code formatting should be common across the team, you
> things like
> - spaces vs tabs
> - position of braces
> - spacing within the file
> Code formatting issues can be avoided by going through a list of
> formatting questions (depending on your language, there should be
> standards available to work off of). If you are using Java, there are
> several code formatters available for jEdit that are pretty
> But, for example, I use JavaStyle for formatting Java, and there is a
> in placing the <p> symbols within JavaDoc blocks in the current
> It kind of stands out (though it's not illegal HTML). I would watch
> for those things.
> Also, some IDEs, like NetBeans, generate code for you and there are
> blocks that should not be edited (because NB may regenerate them).
> kind of thing I've had to watch out for.
> Similarly, if you are using a different compiler than the rest of the
> group, I find it a good idea to use the group's compiler before
> in code. I've found some slightly different behavior on the jikes
> about 5% of the time than what I found with javac.
> Personally, I usually keep a copy of NetBeans around for laying out
> components and generating listener stubs. I use jEdit for most of the
> normal coding, however.
> Generally I stick with jEdit these days exclusively because I am sick
> all the configuration that goes along with being productive in an
> finding where settings are, etc. I tried Eclipse briefly and backed
> mainly for that reason.
> One thing I would point out is that, for jEdit at least, some of the
> useful plugins are not completely up-to-date and there are bugs.
> Personally, I try to keep track of these. If something is not working
> I am on a team project, I want to know what I can rely on (or how I
> make it work). That way, if I am under pressure to deliver, I won't
> saying, "Oh, I can't do that in the editor, there's this bug..." I'm
> criticizing the work of the plugin developers, just need to keep in
> what I can do or not do in jEdit.
> To summarize, in my experience it wasn't a problem if there were no
> Good luck
> Good luck!
> This Newsletter Sponsored by: Macrovision
> For reliable Linux application installations, use the industry's
> setup authoring tool, InstallShield X. Learn more and evaluate
> today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> jEdit Users' List
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.