"Eric M. Ludlam" <ericludlam@...> writes:
> On 01/20/2012 06:49 PM, Philipp Haselwarter wrote:
>> Oh and please please, write more documentation on how to properly set up
>> cedet :)
>>> (info "(cedet) JDEE Target")
>>> @TODO - Add section on how to configure semanticdb-javap for
>>> extracting symbols and header info from .jar files for semantic.
> Indeed, that would be good. I am dependent on others for development
> environments I don't use myself. For javap, I did get it working
> suitably for Android dev, but never figured out system jar files, and I
> don't use JDEE either to know how to integrate the two.
> I think Joel may soon be in a position to add the right info here. ;)
>> just crossed my mind: maybe do a little screencast demo? that always
>> gives me the best impression of how a complex piece of software can
> I looked into that a couple years back, but I couldn't get the tool I
> found on Emacswiki to work after 1/2 an hour or so and eventually gave up.
> I would encourage anyone who wants to to give this a try. It can only help!
>> Making your IDE work by trial-and-error is a /very/ time consuming task.
>> That said, I know that writing documentation is, too. btw, thanks for
>> providing this wonderful library for Emacs!
> Since I don't write code for a living anymore, I usually just watch for
> things going by on the Mailing list that would make good topics, and try
> to get it added into the doc.
> I have found it difficult to remain motivated since I don't actually get
> to use CEDET much anymore, so if you learn something, consider providing
> a patch for the doc, and getting an FSF assignment!
>> Back at the topic:
>> Would this make completion for java's standard library available?
>> Actually, what is left in jdee that cedet can't do?
> As I understand it, JDEE uses beanshell, which introspects, and emits
> handy Emacs Lisp code. As such, it does well with system libs. What
> Joel has done, I think, is point semanticdb-javap-classpath at some
> system jar files. I hadn't tried this (I used the android system Jar
> file) but I don't know why it wouldn't work. The system jar, I'm sure,
> will emit every possible javap output syntax, so if something wasn't
> used with Android, I wouldn't have fixed the parser for it, and things
> won't parse well.
As a datapoint I toyed with using a Clojure REPL instead of Beanshell a
while ago. Clojure is better maintained than Beanshell was my thought,
also the impedance mismatch is less between Clojure and Elisp than
Beanshell and Elisp.
Ideally I wanted something that didn't require downloading dependencies,
but I didn't find a solution, so went with Clojure.
Another thing that might be interesting is tighter integration between
CEDET and Maven. I think maybe Malabar Mode is in that direction but
haven't looked closer.
> As far as features, JDEE has a lot of features related to build, debug,
> projects, and some pretty nifty java specific code helpers and wizards.
> Since CEDET is a utility, that really continues to belong in a tool
> like JDEE, and CEDET will continue to try and support such tools.
>> jdee does not seem to be quite up to speed with cedet anymore, making
>> 1.1beta work requires some fiddling (jde still uses
>> `senator-minor-mode', calls `semantic-add-minor-mode' with three
>> arguments…). So where's the compatibility going?
> Paul Landes has been recommending folks stick with an old CEDET Beta.
> Getting a tool like JDEE to work using either trunk, or newtrunk or
> Emacs integrated CEDET may be tricky since it uses a lot of features.
> I think JDEE just needs some TLC to bring it up to speed with newer
> CEDET. Moving it to support CEDET trunk is probably not too bad.
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> Cedet-devel mailing list