Re: The future of JDE?

2001-08-10 Thread Paul Kinnucan

At 02:28 PM 8/9/2001 -0400, you wrote:
>> > Will JDE be the choice for tiny, simple, non-web-enabled apps?
>> > What will happen to it as Unix becomes KDE-ed and IBM will be
>> > spending an additional 2 billion dollars on its e-commerce
>> > suite (which includes VAJ)?
>>
>>Yeah, I'm sure that the JDEE and Emacs will all be relegated to
>>small little projects as the latest round of teenagers learning
>>how to operate a computer with joysticks want to code with just a
>>mouse.
>But you've got to admit that pointing the mouse on a var on the screen and 
>having its runtime value appear as a tooltip or in general print previewing 
>is fantastic! :)

I've already implemented this for an interface between Emacs and another
debugger. Putting the cursor on a variable displays its value in the Emacs
message area. I plan to implement a similar capability, based on a
generalization of eldoc, for JDEbug as well.

- Paul




Re: The future of JDE?

2001-08-08 Thread Daniel Hegyi

If I remember correctly they were referring to a switch for jikes that does 
this.

Regards,
Daniel


>From: "Matthew Sherborne" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Re: The future of JDE?
>Date: Wed, 8 Aug 2001 10:19:32 +1200
>
>I remember hearing that some users were already using incremental
>compilation in JDE a while ago.
>
>Someone said how to do it. It should be in the archives...
>
>


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp




Re: The future of JDE?

2001-08-08 Thread Matthew Sherborne

I remember hearing that some users were already using incremental
compilation in JDE a while ago.

Someone said how to do it. It should be in the archives...





RE: The future of JDE?

2001-08-08 Thread Molitor, Stephen

Well, perhaps I spoke out of turn -- I'm just a JDE user, not a JDE
developer, so I really shouldn't be speaking for the developers as to what
JDE is or is not likely to include in the future.  But, regarding the
incremental compilation issue, I thought the issue was that using the
beanshell would make compilation very fast, elimintating the need for
incremental compilation.   Here's what I dug up from the archive:

>On 06/12/2001 12:03:23 PM Paul Kinnucan wrote:
> 
> 
> This would not be difficult. I have been planning to use the Beanshell to
> compile files. This would eliminate the need to run javac, i.e., start up
a
> vm, every time you want to compile a file. Compilation would be virtually
> instantaneous since most of the javac compilation time is due simply to
> starting the vm.

If I'm wrong, and incremental compilation is very easy to do in JDE, then by
all means do it!  But it sounds like it might not be necessary.

However, my larger point was that the Emacs/JDE approach is to cooperate
well with external stuff.  Integrating with external EJB/servlet containers
is a good example.  Obviously, you still need an external EJB/Servlet
container on your server.  It also seems obvious, at least to me, that one
would want to test / develop with the same EJB/Servlet container.  We've had
problems at work because people are developing with the servlet container
that comes bundled with JBuilder (Tomcat), while we are using WebLogic 5.1
in production.  (Now, I'd be happy if we just switched to Tomcat, but that's
a different issue.)  I don't need my IDE to double as a servlet container!  

Also, I don't want to limit the discussion to strictly Java development.  I
develop mostly in Java at work, while still spending some time maintaing the
legacy C++ system, and doing some Perl stuff.  At home, I mess with Python
and Elisp, in addition to Java.  It's great to have one IDE that does all of
that!  I don't have to waste a lot of time learning a different IDE for each
language.  

Not that VAJ is bad -- if you like it, use it.  But, I am much more
productive in JDE.

Steve Molitor
[EMAIL PROTECTED]

Regarding 

-Original Message-
From: Daniel Hegyi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 08, 2001 3:32 PM
To: Molitor, Stephen; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: The future of JDE?


I disagree with the sentence "JDE is not likely to ... support incremental 
compilation, for example." I use both VAJ (my company is partially a 
WebSphere shop) and JDE (for nostalgic reasons (the good old college 
years...) and small codes.) Incremental compilation is one of the coolest 
things I've ever seen in a Java IDE. On my fundamental feature/favorites 
list it's now right up there with the most essential feature, syntax 
coloring!! If anybody has tried incr. comp., they get addicted to it and 
will never want to leave home without it.

Now, I've been told that incr. comp. is actually not that difficult to 
achieve for the JDE by piggybacking on the beanshell. And with ecb, 
compilation errors could also bee marked (by a small red x, lets say) in the

method tree.

Since we're on the topic: I realize that Emacs supports many-many modes and 
that it runs on Ux as well as Win. (BTW, I think that many of the big JAVA 
IDEs do as well, because they're written [partially] in Java.) But with IDE 
monsters appearing, such as VAJ, which has a whole EJB/Servlet test 
environment built in (no need for an EJB/Servlet server/engine - all built 
in) and funded with huge sums (for R&D and for the many-many hackers working

full-time to improve it) what do people think of the JDEs future role? Lets 
not consider the $ issue (I've never paid for SW in my life. :) ) and lets 
only talk about Java development. With fast and cheap PCs appearing with 
huge hard disks and RAMs, performance is becoming less of an issue for the 
swing-based monsters.

Will JDE be the choice for tiny, simple, non-web-enabled apps? What will 
happen to it as Unix becomes KDE-ed and IBM will be spending an additional 2

billion dollars on its e-commerce suite (which includes VAJ)?


Regards,
Daniel



>From: "Molitor, Stephen" <[EMAIL PROTECTED]>
>To: "'EXT-Syre, John'" <[EMAIL PROTECTED]>, 'Galen Boyer'  
><[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>Subject: RE: Discussion from comp.lang.java.softwaretools on VAJ.
>Date: Wed, 8 Aug 2001 14:21:35 -0500
>
>I agree with most of what John said, although I don't think VAJ is so bad. 
>I
>actually like a lot of things about VAJ, dislike others.  I only used it 
>for
>a short while, however.  I do know several excellent developers who swear 
>by
>VAJ; I'm much happier with Emacs/JDE.
>
>VAJ and Emacs/JDE have radically different philosophies, however.  It's
>really an apples / oranges comparison.  The Emacs approach is to work well
>with existing tools and the external environment - the Unix philosophy.  
>The
>VAJ approach is to provide a simple facade the hides all the complexi