Paul Landes wrote:
> I think others have answered this well, but basically it sets up
> variables like source and library [class] paths.
Thats what I have assumed as well, but it did not seem to work...
> You haven't configured environment correctly. It should only confirm
> the correct package.
... so I will start from the beginning with the configuration, again,
and se if I get it right this time.
> > - then required me to save the class manually
> Buffer saves are never assumed in Emacs--it's a design
Why is that?
In java one always have to specify package and class anyway, so as long
as that is confirmed it should be ok to let emacs automatically store it.
> > My thinking is that the project file already has the source root
> > directory, so the function should ask for the class name, with an
> The class name comes from the buffer file name minus the file name
The way I see it is that as a java programmer using an IDE, I should not
have to think of the IDE's own orinternal way of doing things, to get my
task done. Rather, the IDE should adapt to how the programming platform
So in java things are oriented around classes, packages, configuration
files etc. For example, when I need a parameter class, the only
questions I should need to answer to create and save the class is
the IDE should do the rest, such as finding the correct directory,
saving it etc.
> Using C-x C-f to open (create after save) a new file and tacking on
> ".java" seems as economical, particularly the way it fits in with the
> typical way other packages create new source files.
Not really, because thats only one part of the complete functionality I
am looking for.
I would like to have something like
where the following scenario represents the entire functionality I am
- (user wants to add a non exitent parameter class at point
in source code: class: RequestArgument
public void processArguments( [cursor]
- user: M-x insert-class-at-point
- func: ask for [packagename.]classname:
- func: create buffer
- func: insert class template with package names, class name etc
- func: locate correct directory for class
(based on info from project file and user input)
- func: save buffer
- user: edit new class code
- user: save
- func: switch to original source buffer and insert class name at point
- func: add correct import statement in original source file
- user: continues editing parameter
... processArguments( RequestArguments req, ...
I think its perferctly legitimate for the jde to have something like
this pre-fabricated, so the user dont have to do it.