Len Trigg writes:
 > Paul Landes wrote:
 > > 1. I'd like to change the `jde' directory in:
 > 
 > I have no problems with changing the directory name.  It sounds like
 > you also intend to rename all the lisp functions to use jdee instead
 > of jde?  That would indeed be a large task, and how would you plan to
 > manage compatibility with external plugins and other code that depend
 > on current function names?

Maybe some day, but that would be a long term goal.  I'm more talking
about the more obvious things like names in documentation, the name of
the major mode (i.e. JDEE vs JDE in the mode line and `jde-mode' vs
`jdee-mode' if possible).  It would be much easier to go from JDEE to
JDE, but I don't suppose that's possible.  Or is it?  Any lawyers out
there?  Maybe this is worth reconsidering.

 > > 3. I'm estimating a month for the 2.4.0 branch.  We're adding patches
 > >    to this release, but I've also decided to add a lot of enhancements
 > >    that I've kept in my local library for years.  While it doesn't
 > >    seem like much has been done in the way of new features, this has
 > >    been the number one goal of mine for months and that's how long it
 > >    is taking.
 > 
 > Can you give us a list (teaser) of what extra features you have that
 > you are planning to include?  Can we help in any way?

One of the big ones is a replacement for `jde-open-class-source'.  It
will look at the list of imports and gives a better list of
candidates.  It tries to unify `jde-open-class-at-point' and
`jde-open-class-source'.  IMO, these should be the same core function
and `jde-open-class-at-point' should do the extra thing of importing
as a side effect (think advice).

There's also:

- Better quoting for beanshell code (i.e. support for double
  quote).

- Javadoc via browser support that iterates through a list of URLs,
  but in addition to the current behavior, continues to list traversal
  until an existing a URL is found/exists.

- Find/visit a resource defined on the classpath.

- Display/show the jar on the class path for which a class is defined.

- Goto a file and line number based on an exception stack trace.

- A jde-jeval catches beanshell errors and allows the client to deal
  with them as Emacs errors instead of just referring to *Messages*.
  It does this with beanshell eval wrapped around a try/catch.

- Reverse camel notation -> Hungarian -> SQL -> C Constant variable
  formatting conversions.

- Beanshell file definition visit/finding.  Beanshell files are viewed
  and treated like emacs library files in `load-path' and there are
  respective beanshell libraries that support this on the bsh side.

There is more, but these are some of the big ones.

-- 
Paul Landes
[email protected]

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
jdee-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-users

Reply via email to