Re: ecb question

[Andrew Hyatt]

I don't use ECB, but if anyone from that project is interested in
doing what Paul suggests, please email me with any questions you might
have about jde-xref.

Paul Kinnucan <[EMAIL PROTECTED]> writes:

> Paul Kinnucan writes:
>  > Berndl, Klaus writes:
>
> [snip]
>
>  >  > 
>  >  > But: IMHO the best would be to integrate JDEE for that. This could be done 
> like:
>  >  > 1. You select via popup-menu of the ECB-methods-buffer a method for being 
> search
>  >  >for occurences in current source-path/project
>  >  > 2. Then ECB jumps to this method in the source-buffer
>  >  > 3. Then JDEE should have a function 
> "jde-find-call-occurences-of-method-under-point"
>  >  >which does the search for the occurences with appropriate mechanisms - e.g. 
> with
>  >  >delegating this task to the beanshell - do not know if JDEE has already 
> such a 
>  >  >feature or when not how exactly this one could be implemented.
>  >  > 4. ECB would then only call this 
> "jde-find-call-occurences-of-method-under-point".
>  >  > 
>  >  > Question to Paul: Has JDEE already such a feature?
>  > 
>  > As of JDEE 2.3.3, for which a very stable beta is available at the
>  > JDEE web site, yes, thanks to the efforts of Andy Hyatt. See the
>  > "Cross-Referencing Classes" section of the "Searching Source Code"
>  > chapter of the "JDEE User's Guide" for information on how to build and
>  > use a method call cross-reference database for a Java project.
>  > 
>
> Hi Klaus,
>
> Some more information about jde-xref. It builds a cross-reference database by 
> parsing Java class files. It includes three functions for navigating the
> database:
>
> * jde-xref-first-caller (C-c C-v a) builds a list of callers of the method at point
>   in the current buffer and displays the first caller.
>
> * jde-xref-next-caller (C-c C-v n)  displays the next caller on the list built by 
>   jde-xref-first-caller.
>
> * jde-xref-display-call-tree displays a buffer containing a mouse-sensitive list
>   of the callers of the method at point. Clicking any caller displays the source
>   for that caller.
>
>
> It would be nice to integrate these functions with ECB, e.g., first-caller and
> next-caller should work for the method selected in the ECB's class window.
> Also, it would be nice to be able (optionally?) to add a call-tree window 
> to the set of windows that makes up the ECB desktop. That way, a user 
> could 
>
> 1. Select a method in the class window.
>
> 2. Select a "Show Callers" command from the ECB menu.
>
>A Callers window would appear in the ECB desktop.
>
> 3. Click a caller in the Callers window.
>
>Emacs displays the source of the call.
>
> - Paul

Re: Trouble Customizing Variable

[Andrew Hyatt]

Your error usually indicates your .emacs file was messed up - perhaps
it was missing a parenthesis somewhere, so when it came time to parse
your .emacs file to find the location to insert the customization, it failed.

Aaron Davies <[EMAIL PROTECTED]> writes:

> On Sunday, July 6, 2003, at 08:25  AM, Paul Kinnucan wrote:
>
>> Aaron Davies writes:
>>
>>> On Saturday, July 5, 2003, at 08:34  AM, Paul Kinnucan wrote:
>>>
 Aaron Davies writes:

> On Wednesday, June 25, 2003, at 02:01  AM, Aaron Davies wrote:
>
>> I'm having trouble customizing a variable, specifically
>> jde-javadoc-author-tag-template. When I type a new value in the
>> customization buffer and hit set or save, Emacs beeps at me and the
>> minibuffer says "End of file during parsing". What's wrong?
>>
>> I cannot reproduce this problem on my system: Windows Millenium,
>> Emacs 21.3.1, JDEE 2.3.3beta4. For example, I changed the
>> default tag to
>>
>> "* @author Paul Kinnucan"
>>
>> without any problem. Perhaps the problem is with the
>> particular template string you are trying to enter. If you send
>> me the exact template string that you are trying to enter
>> (preferably copied from the customization buffer and
>> pasted into your email), I will investigate further.
>
> Well, it seems to work fine now. I have no idea what changed. 
> Sorry to bother you.
> -- 
>  ____
> /  )  /  )
>/--/ __.  __  /  / __. , __o  _  _
>   /  (_(_/|_/ (_(_) / / <_  /__/_(_/|_\/ <__

RE: ecb question

[Paul Kinnucan]

Paul Kinnucan writes:
 > Berndl, Klaus writes:

[snip]

 >  > 
 >  > But: IMHO the best would be to integrate JDEE for that. This could be done like:
 >  > 1. You select via popup-menu of the ECB-methods-buffer a method for being search
 >  >for occurences in current source-path/project
 >  > 2. Then ECB jumps to this method in the source-buffer
 >  > 3. Then JDEE should have a function 
 > "jde-find-call-occurences-of-method-under-point"
 >  >which does the search for the occurences with appropriate mechanisms - e.g. 
 > with
 >  >delegating this task to the beanshell - do not know if JDEE has already such 
 > a 
 >  >feature or when not how exactly this one could be implemented.
 >  > 4. ECB would then only call this 
 > "jde-find-call-occurences-of-method-under-point".
 >  > 
 >  > Question to Paul: Has JDEE already such a feature?
 > 
 > As of JDEE 2.3.3, for which a very stable beta is available at the
 > JDEE web site, yes, thanks to the efforts of Andy Hyatt. See the
 > "Cross-Referencing Classes" section of the "Searching Source Code"
 > chapter of the "JDEE User's Guide" for information on how to build and
 > use a method call cross-reference database for a Java project.
 > 

Hi Klaus,

Some more information about jde-xref. It builds a cross-reference database by 
parsing Java class files. It includes three functions for navigating the
database:

* jde-xref-first-caller (C-c C-v a) builds a list of callers of the method at point
  in the current buffer and displays the first caller.

* jde-xref-next-caller (C-c C-v n)  displays the next caller on the list built by 
  jde-xref-first-caller.

* jde-xref-display-call-tree displays a buffer containing a mouse-sensitive list
  of the callers of the method at point. Clicking any caller displays the source
  for that caller.


It would be nice to integrate these functions with ECB, e.g., first-caller and
next-caller should work for the method selected in the ECB's class window.
Also, it would be nice to be able (optionally?) to add a call-tree window 
to the set of windows that makes up the ECB desktop. That way, a user 
could 

1. Select a method in the class window.

2. Select a "Show Callers" command from the ECB menu.

   A Callers window would appear in the ECB desktop.

3. Click a caller in the Callers window.

   Emacs displays the source of the call.

- Paul

RE: ecb question

[Paul Kinnucan]

Berndl, Klaus writes:
 > For Paul: There is a feature-request for JDEE at the end of this mail -
 > or at least a question about a feature...
 > 
 > Hello. 
 > first of all: Please always send to the ECB-mailing list! 
 > 
 > > Is ecb capable of showing me where a particular function is called/used. 
 > > If for example I am in the methods window can I find out where, in the valid 
 > > source paths, a given method is called...in what source file? Thanks.
 >  
 > No, currently not...in general this needs - to work really well - a "semantic"
 > database of all current classes and methods in a project so a tool (e.g. ECB)
 > can find only the right methods (e.g. polymorph methods has to recognized
 > to find only the correct one which is meant)...
 > 
 > ECB is a language independent tool so for itself it could only offer a simple
 > grep-find search of the current selected method in the methods-buffer. This
 > method would then be search with Emacs builtin grep-find in the whole source-
 > patch where current source-file reside. This would be possible and probably
 > not really hard...maybe a good idea...let me see...
 > 
 > Maybe with the semanticdb of the semantic-library a language-independent smart
 > and corrent mechanism could be implemented too...
 > 
 > But: IMHO the best would be to integrate JDEE for that. This could be done like:
 > 1. You select via popup-menu of the ECB-methods-buffer a method for being search
 >for occurences in current source-path/project
 > 2. Then ECB jumps to this method in the source-buffer
 > 3. Then JDEE should have a function "jde-find-call-occurences-of-method-under-point"
 >which does the search for the occurences with appropriate mechanisms - e.g. with
 >delegating this task to the beanshell - do not know if JDEE has already such a 
 >feature or when not how exactly this one could be implemented.
 > 4. ECB would then only call this "jde-find-call-occurences-of-method-under-point".
 > 
 > Question to Paul: Has JDEE already such a feature?

As of JDEE 2.3.3, for which a very stable beta is available at the
JDEE web site, yes, thanks to the efforts of Andy Hyatt. See the
"Cross-Referencing Classes" section of the "Searching Source Code"
chapter of the "JDEE User's Guide" for information on how to build and
use a method call cross-reference database for a Java project.

- Paul

ECB 1.95 released!

[Berndl, Klaus]

  ECB 1.95 is released!
 
 
 

What's new in the new release:
--
 
* Changes for ECB version 1.95
 
** ECB now displays the expand- and collapse symbols in the tree-buffers with
   image-icons - the same icons as speedbar uses. See the new option
   `ecb-tree-use-image-icons'.
 
** Adding hideshow to the popup-menu of the Methods-buffer.
   This popup-menu now offers two entries for hiding resp. showing the block
   of that token in the Methods-buffer for which the popup-menu was openend.
   This is done with the hideshow.el library.
   Thanks to Christoff Pale <  [EMAIL PROTECTED]> for 
suggestion.
 
** Horizontal scrolling of the tree-buffers by clicking the edges of the
   modeline with mouse-1 or mouse-2. I.e. if you click with mouse-1 onto the
   left (resp right) egde of the modeline you will scroll left (resp. right)
   with the scroll-step defined in `ecb-tree-easy-hor-scroll'. This is only
   for GNU Emacs because XEmacs has hor. scrollbars.
   
** Changed default keybindings:
   - C-c . r:  `ecb-rebuild-methods-buffer'
   - C-c . lc: `ecb-change-layout'
   - C-c . lr: `ecb-redraw-layout'
   - C-c . lt: `ecb-toggle-layout'
   - C-c . lw: `ecb-toggle-ecb-windows'
 
** Starting ECB is now possible via the "Tools"-menu
 
** ECB now requires speedbar version 0.14beta1 or higher. An automatic
   requirements-check is done by ECB. This is because now ECB has three
   dependencies to speedbar-code: Integrating whole speedbar in the ECB-frame,
   using speedbar-logic to parse files with imenu or etags and using the icons
   of speedbar for the ECB-tree-buffers.
 
** Fixed bugs
 
*** Now the "goto-window-..." menu-entries in the "ECB"-menu are working correct
if a speedbar is integrated into the layout.
 
*** Preventing etags-supported sources from being parsed (and saved) too often.
 
 
 
How to get it:
--
 
Sorry, it's too big to post the sources here...
 
If you are using ECB >= 1.80 then you can just call "M-x ecb-download-ecb" if
you are online. ECB will then download autom. latest and newest ECB and
install it for you.
 
Or go to the homepage at   http://ecb.sourceforge.net and 
download it from
there.
 
 
 
General description of ECB:
---
 
ECB stands for "Emacs Code Browser" and is a source code browser for (X)Emacs.
It is a global minor-mode which displays a couple of windows that can be used
to browse directories, files and file-contents like methods and variables. It
supports source-code parsing for semantic-supported languages like Java, C,
C++, Elisp and Scheme as well as for source-types supported "only" by imenu or
etags (e.g. perl, TeX, LaTeX etc.).
 
Here is an ascii-screenshot of what ECB offers you:
 
--
|  | |
| Directories  | |
|  | |
|--| |
|  | |
| Sources  | |
|  | |
|--| Edit-window(s)  |
|  |(can be splitted in two windows) |
| Methods/Vars | |
|  | |
|--| |
|  | |
| History  | |
|  | |
--
||
| Compilation-window (optional)  |
||
--
 
This is only one example-layout - ECB offers a lot of different layouts.
 
For more details go to   http://ecb.sourceforge.net/
 

Enjoy,
Klaus