Thomas Finneid writes:
> Phillip Lord wrote:
> > You're trying to do too much with JDEE and not enough with Emacs. A lot
> > of this is very general and not specific to java. It's provide by other
> > packages.
> Perhaps, I shall look for the functionality elsewhere. Can you suggest
> some place I can find it?
The IDEs I've seen around are:
- JEdit (this one is interesting)
> But there is a problem how some of it works and some of the
> functionality I want, is specific to java.
Have you thought of Eclipse plug-ins?
> My biggest problem with the emacs philosophy is that it is too difficult
> to figure out what functionality exists, where to find it and how it works.
The Emacs learning curve is painful. Emacs + Lisp is even worse.
However, the effort is rewarding. I hated lisp when I started with
it, however, now I prefer it to other languages.
You might want to start with the function apropos:
M-x apropos-command ^jde-gen RET
to learn about all the JDE code generation commands, which are
> > Thomas Finneid <tfinneid@...> writes:
> >> First of all I want better documentation of jdee, so I would like to
> >> reorganise and update the documentation. Plus I want to make it w3c
> >> compatible, since it does not work in Opera and is a little outdated.
> >> If anybody has any input on that, please let me know.
> > This would be great.
> >> - Better access and overview of all resources included in a project: src
> >> files, test src, build scripts, config files, libraries etc. The
> > ECB is the way forward here.
> >> - Essentially I want something like what eclipse has, the directory
> >> tree on the left side, which lists everything included in the project.
> >> It gives easy access to any resource in the project, independent of
> >> which directory its in and how complicated the name is.
> >> - Another solution could be something that search the entire
> >> project or something.
> > There are quite a few systems for doing this depending on exactly how
> > you want to search. I use find-dired and grep-find a lot for basic
> > searching.
> >> - Better movement between buffers and resouces
> >> - In eclipse there are window panes, that allows you to easily find
> >> one of your many current windows.
> >> - In jdee there is only buffers and they have to be selected by
> >> typing the name of the buffer, every time you want to switch. it does
> >> not have a good history function so it takes up to 20 seconds to switch
> >> to another buffer than the previous one.
> > ido.el makes both buffer and file switching very, very fast.
> >> - Better code completion, one that is faster, more accurate and, last
> >> but not least, more user-friendly. It should also support completing
> >> all included libraries etc.
> > JDEE does library aware completion. I use pabbrev.el (which I am fond
> > of, partly because I wrote it), which is dumb, works on text analysis,
> > but seems to work well. There are other options here.
> >> - Better compile cycle support, the
> >> whole code - compile - fix-bug - run
> >> cycle. It is probably there but I havent figured out how to set it up.
> > JDEE is rather tied to an underlying build tool. It can drive maven or
> > ant pretty well, and will the right thing with the output.
> >> The more advanced stuff is:
> >> - refactoring support,
> >> - mainly renaming and moving methods, attributes,
> > This it doesn't have.
> >> - code wizards
> >> - which help automate creating classes for specific purposes in the
> >> program. I know there is some support for it, but I feel its not
> >> complete.
> > Probably true; there could be more here.
> >> - what I specifically want is a function that does all the mundane
> >> operations related to creating, or including, a class, adding it
> >> to the project, storing it in the right directory/package etc. etc.
> > JDEE works the other way around; you put it into the right directory,
> > then it works out the package for you.
> >> - additionally help create other mundane methods or classes one needs,
> >> e.g. enum classes, parameter classes etc.
> > True.
> >> - javadoc access that works in all browsers
> > javadoc access comes from browse-url -- again this should work.
> >> finally I want all of this packaged into an install file that sets
> >> eveything up for me, easily, without a lot of reading and manual
> >> configuring.
> > Yes, this could help a lot. It's one area that Emacs as a whole is still
> > lacking. It's very powerful, but it can take a while to learn.
> > Phil
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> > Build the coolest Linux based applications with Moblin SDK & win great prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > jdee-devel mailing list
> > jdee-devel@...
> > https://lists.sourceforge.net/lists/listinfo/jdee-devel
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> jdee-devel mailing list