RE: How can I make the JDE smaller ?
>So I have two questions : >1) Is there a way to disable all the new functinnalities >(speedbar, eieio, semantic ...) ? No, latest JDE-version need all these packages! >2) If it is not possible, where can I find some old JDE 2.1.* >versions ? ftp://ftp.sunsite.auc.dk/projects/jde >I know the new functionnalities are wonderful (yes, I believe it) >but I just want : >- syntax coloring >- auto indentation >- compile menu and compile error to source links >So, please, tell me if you know how I can get a >"light JDE version". I know I am not the only one in this case. Hmm, i think for only these tasks you don´t need any JDE because all these goals you can reach very well with the standard java-mode of cc-mode and the standard compile-features (compile, next-error etc.) of Emacs... Klaus
RE: compile error to source links
>I would like to understand how the "compile error to source links" feature works. I am trying to integrate "make" into JBuilder IDE and I want to do implement this feature just like JDE. Can > someone point me to the JDE source where this feature is implemented. This is actually not done by the jde, look at the file compile.el. Javier
Re: How can I make the JDE smaller ?
- Original Message - From: "Nicolas Regnault" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 12, 2001 11:17 AM Subject: How can I make the JDE smaller ? > hello all, > > I am a JDE user since two years. Since a few days, I was > using the 2.1.4 version : very good. I have upgraded to > the 2.2.7.1 with all the new requirements. What a bad > surprise : everything is really slower. My emacs needs > 1 minute to be launched. When I open a source file, I can > go to the coffee machine ... > I have seen some messages in the mailing list archive that > deal with this, but answers only deal with emacs itself. > So I have two questions : > > 1) Is there a way to disable all the new functinnalities > (speedbar, eieio, semantic ...) ? > 1. Setup the JDE to load on demand rather than at Emacs startup. See the JDE installation instructions on the website for info on how to do this. 2. Customize jde-imenu-enable off. 3. Customize jde-auto-parse-enable off. 4. Add (senator-minor-mode -1) to your .emacs file. (I will make senator mode optional in the next release.) 5. Compile the eieio package. 6.. Get yourself a faster computer. - Paul
Method Navigation
This is an idea I have for quickly navigating to a method declaration in a Java class. Searching for a method declaration in the current buffer is one of the activities I perform frequently. I am aware of five ways to accomplish this task. 1. use standard emacs search capabilities 2. use jde classes menu 3. use ecb methods buffer 4. use find-tag 5. use speedbar Here's why I don't like any of the above options. Ecb and the jde classes menu require the mouse. Mouse usage is inefficient. Find-tag requires frequent updating of the tags file and requires knowing and correctly spelling the full method name. Searching usually results in multiple hits due to method calls. The speedbar shows variables and method names and takes up too much screen real estate. Are there other ways to more efficiently locate a method? Probably, but what I am looking for is described below. I would like to see the list of methods for the current buffer in the minibuffer by pressing some C-[some key]. While the list is presented in the minibuffer I can narrow the list of methods names that I am interested in by typing a portion of the method name. Once I have the method name that I am interested in at the head of the list I can select it with the enter key. Selecting the method name takes me to the method declaration in the current buffer. This is similar to what is provided by ido.el and iswitchb.el packages which provide fast buffer and file switching. Is there anything like this in existence today? If not, does anyone think this would be a good addition to the jde?
RE: Method Navigation
try M-x senator-jump Javier
RE: compilation buffer in different frame
I'm not a lisp expert, somewhere I found a way that works for me:
(setq special-display-buffer-names
'("*compilation*" "*grep*"))
to configure size and position of a new frame you can use something
like this:
(setq special-display-frame-alist
(append (list '(top . 480 ) '(left . 200) '(height . 20) '(width .
100)
'(menu-bar-lines . 0) '(minibuffer . t))
For xemacs it's slightly different:
(let ((plist '(height 20 width 100 unsplittable t
default-toolbar-visible-p nil menubar-visible-p nil)))
(setq special-display-buffer-names
`(("*compilation*" ,@plist
Hope this helps
> -Original Message-
> From: Mark Mynsted [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 13 July 2001 01:49 AM
> To: [EMAIL PROTECTED]
> Subject: compilation buffer in different frame
>
>
> Is there a way to have the compilation buffer come up in a different
> frame? I often have several buffer windows open on my current frame
> at the time I do a compile. The compilation buffer pops up in my
> current frame and alters the layout and number of windows open.
> --
> Sincerely yours;
>
> Mark Mynsted
>
> VHA Management Information Systems Client Services
> 972.830.0592, internal x1592
>
>
> /"\
> \ / ASCII Ribbon Campaign
> X Against HTML Mail
> / \
>
>
Finding class at point based on imports?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey. I have tried going over as many JDE functions as possible but I can't find any that fit. When given a classname without it's package (IE String vs java.lang.String) I want to resolve the full package name with respect to the import statements in the current buffer. Just to avoid duplication of effort... is their a function which can do this for me? Didn't see one. If necessary I can write a jde-import-resolve function. Kevin - -- Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] ) Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596 There are 6 billion people living on this planet, 5.4 billion have not yet chosen an Operating System -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt iD8DBQE7Tk4kAwM6xb2dfE0RAkbMAJ4szyDxx9mqnvkU70dF2R3NxffNdQCgpRkW YJpSO6oFFpyelZEltuX9s6s= =YtHe -END PGP SIGNATURE-
jde-overview.el
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This provides an overview of Java buffers in the format of:
//JDE overview for file:
/projects/reptile/src/java/org/openprivacy/reptile/SequenceDispatchEngine.java
29: package org.openprivacy.reptile;
52: public class SequenceDispatchEngine {
60: public static void dispatch( HttpServletRequest request,
61: HttpServletResponse response,
62: ParameterPasser params ) throws ServletException
{
88: public static String dispatch( ParameterPasser params ) throws Exception {
Have fun...
;;; jde-overview.el --- Obtain an overview of Java buffers.
;; $Id: jde-overview.el,v 1.1 2001/07/13 12:36:21 burton Exp $
;; Copyright (C) 2000-2003 Free Software Foundation, Inc.
;; Copyright (C) 2000-2003 Kevin A. Burton ([EMAIL PROTECTED])
;; Author: Kevin A. Burton ([EMAIL PROTECTED])
;; Maintainer: Kevin A. Burton ([EMAIL PROTECTED])
;; Location: http://relativity.yi.org
;; Keywords:
;; Version: 1.0.0
;; This file is [not yet] part of GNU Emacs.
;; This program is free software; you can redistribute it and/or modify it under
;; the terms of the GNU General Public License as published by the Free Software
;; Foundation; either version 2 of the License, or any later version.
;;
;; This program is distributed in the hope that it will be useful, but WITHOUT
;; ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
;; FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
;; details.
;;
;; You should have received a copy of the GNU General Public License along with
;; this program; if not, write to the Free Software Foundation, Inc., 59 Temple
;; Place - Suite 330, Boston, MA 02111-1307, USA.
;;; Commentary:
;;
;; JDE overview provides a quick "overview" of a Java class from its Java
;; source. This overview provides misc information defined in the source file
;; including class and method declarations. The main benefit is that since the
;; overview is based on the source file it's format is not modified from how it
;; was entered.
;;TODO:
;;
;;
;; - support java interface methods.
;;; Code:
(defvar jde-overview-buffer-name "*jde-overview*" "Name of the temp buffer.")
(defvar jde-overview-current-class-or-interface nil "If the currently parsed
file is a class the value will be 'class' and if it is an interface it will be
set to 'interface'.")
(defun jde-overview-class-at-point()
"Get an overview for the class at the current point."
(interactive)
(save-window-excursion
(jde-open-class-source)
(jde-overview))
(display-buffer jde-overview-buffer-name))
(defun jde-overview()
"Show an overview of the current Java buffer."
(interactive)
(save-excursion
(jde-overview-init)
(beginning-of-buffer)
(jde-overview-insert (format "//JDE overview for file: %s\n" (buffer-file-name)) 1)
(jde-overview-do-package)
(jde-overview-do-class)
(let(method-start method-end regexp)
(if (string-equal jde-overview-current-class-or-interface "class")
(setq regexp "[ ]+public [^{;=]+{")
(setq regexp "[ ]+public [^{=]+;"))
;; should contain ;=
(while (re-search-forward regexp nil t)
(setq method-start (match-beginning 0))
(setq method-end (match-end 0))
(jde-overview-insert (concat (buffer-substring method-start method-end) "\n\n")
(jde-overview-line-number method-start
(jde-overview-fontify)
(display-buffer jde-overview-buffer-name)
(set-buffer jde-overview-buffer-name)
(jde-overview-mode)))
(defun jde-overview-do-package()
"Do the overview entry fo the current package."
(assert (re-search-forward "^package .*;" nil t)
nil "Could not find package statement")
(jde-overview-insert (concat (buffer-substring (match-beginning 0)
(match-end 0))
"\n\n")
(jde-overview-line-number (match-beginning 0
(defun jde-overview-do-class()
"Do the overview entry for the current class."
(let(start end)
(assert (re-search-forward "public \\(class\\|interface\\)" nil t)
nil "Could not find class")
(setq jde-overview-current-class-or-interface (match-string 1))
(setq start (match-beginning 0))
(assert (re-search-forward "{" nil t)
nil "Could not find end of class")
(setq end (match-end 0))
(jde-overview-insert (concat (buffer-substring start end) "\n\n")
(jde-overview-line-number start
(defun jde-overview-init()
"Perform any necesary initialization."
(save-excursion
(set-buffer (get-buffer-create jde-overview-buffer-name))
(toggle-read-only -1)
(erase-buffer)))
(defun jde-overview-fontify()
"Highlght the buffer where nece
Re: Probl;ems with JDEbug
At 09:46 PM 7/12/2001 -0400, Scott Goldstein wrote:
>I've searched the archives and can't find an answer.
>
>Here's my setup:
>
>(custom-set-variables
>'(jde-bug-jdk-directory "c:\\Development\\jdk1.2.2")
>'(jde-use-font-lock nil)
>'(jde-db-debugger (quote ("JDEbug" "" . "Executable")))
>'(jde-bug-vm-includes-jpda-p t))
>(custom-set-faces)
>
>I set a breakpoint and then, from the JDE menu, I choose Debug App and I get
>the following messages:
>
>Fontifying *JDEbug*...
>Fontifying *JDEbug*... (syntactically...)
>menu-bar JDE Debug App
>Fontifying *JDEbug*...
>Fontifying *JDEbug*... (regexps)
>menu-bar JDE Debug App
>Process *JDEbug* not running
>
>If I try to debug from the JDEbug menu, I choose Start Debugger and then
>Launch Process and I get the following:
>
>Fontifying *JDEbug*...
>Fontifying *JDEbug*... (syntactically...)
>menu-bar JDEbug Processes Start Debugger
>Fontifying *JDEbug*...
>Fontifying *JDEbug*... (regexps)
>menu-bar JDEbug Processes Start Debugger
>Debugger started successfully.
>Process *JDEbug* not running
>
>The class that I'm trying to debug is in the source buffer.
>
>Any ideas?
>
1. Read the section on setting up JDEbug in the JDEbug User's Guide.
2. Use JDE->Help->Submit Problem Report when asking for help.
- Paul
Re: compile error to source links
Where is compile.el. I checked the emacs lisp directory and xemacs-packages directory. I could not find it. I am using XEmacs 21 Anand - Original Message - From: Javier Lopez To: Anand Narasimhan ; [EMAIL PROTECTED] Sent: Thursday, July 12, 2001 8:44 AM Subject: RE: compile error to source links >I would like to understand how the "compile error to source links" feature works. I am trying to integrate "make" into JBuilder IDE and I want to do implement this feature just like JDE. Can > someone point me to the JDE source where this feature is implemented. This is actually not done by the jde, look at the file compile.el. Javier
RE: compile error to source links
> Where is compile.el. I checked the emacs lisp directory and xemacs-packages directory. I could not find it. I am using XEmacs 21 In the distribution of Emacs I am using is in emacs-root/lisp/progmodes/compile.el Javier
RE: compile error to source links
At 03:30 PM 7/12/01 -0400, Javier Lopez wrote: > > Where is compile.el. I checked the emacs lisp directory and > xemacs-packages directory. I could not find it. I am using XEmacs 21 >In the distribution of Emacs I am using is in >emacs-root/lisp/progmodes/compile.el > Depending on how emacs was installed, there may only be compile.elc and not compile.el. The .elc file is a compiled version of the .el file, and not human-readable. In that case, you would have to find an emacs distribution that includes the lisp sources. Troy >Javier
