Roadmap for 4.1?
I've seen somewhere that new EAP for 4.1 will start in a month or so.
What are key features to deliver for 4.1?
For me:
- AspectJ support
- Support for JSP 2.0 and JSTL 1.1
- well defined OpenAPI for appservers to enable close integration
What are your thoughts?
--
---
Michal Szklanowski
always developing new IDEAs
Please sign in to leave a comment.
One of the most useful features they could add to debugger is statement-level (as opposed to line-level) stepping. CodeGuide has this now and works pretty good.
+100!
Marcus Brito wrote:
Do you mean something like issue 23622?
Tom
Keith Lea wrote:
Agreed. For me, IDEA is all about the code and making it easier for me
to write and maintain code. I don't need J2EE support or AspectJ (have
you seen the code that generates?!) and if they rae implemented it would
be nice if they were plugins that could be uninstalled to save memory
and processor time (it seems that the memory requirements of IDEA 4.0
are double that of IDEA 3.0).
However, up-to-date Ant integration and support for popular CVS access
protocols (such as SSH2) are not to be dismissed.
Agreed.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
In article <5839141.1077186798059.JavaMail.itn@is.intellij.net>,
Sebastien Petrucci <no_mail@jetbrains.com> wrote:
Of course. Why would anyone want a product tailored to someone else? :)
Some of us realize that we can't get everything we want and that
sometimes, products we buy have features that are only useful to other
people. Some other people don't realize this and cry like children about
how IDEA sucks because it does things that other people want.
In article <8649002.1077194332477.JavaMail.itn@is.intellij.net>,
Rob Bradley <no_mail@jetbrains.com> wrote:
What would be the advantage of having the UI designer be a plugin, but
then making it come free with IDEA? What's the disadvantage of having it
built in?
I would hate for IDEA to become a stripped down base product with a slew of
plugins. Even if they are free to add.
That is one of the first things about Eclipse that I didn't like. In order
to do anything, you need to wade through the various lists of plugins and
find the ones that seem like they might be useful. I want my IDE to be just
that, an Integrated Development Environment, right out of the box. Even if
I don't use all of the features right away; if and when I do, they are all
there without having to go searching. The nice thing is that the features
that I don't use don't seem to get in the way either. They are quite easy
to either disable or ignore.
The more feature rich IDEA is, the larger their potential customer base.
The more people that buy IDEA the more people they can hire to support and
enhance the IDE.
Don't get me wrong, I do like the fact that plugins are possible and that
there are people out there who are willing to create and share them. They
are great for integrating things that the base IDEA development team hasn't
thought of yet or hasn't had the time to implement. I just think that the
IDE should include support for as many of the language and platform features
that it can. People complain about code bloat, memory usage, hard disk
space, ... But in reality, hardware prices keep dropping, memory and storage
space keeps getting larger and IDEA 4.0 on a new machine is at least as fast
as IDEA 3.0 on what was a new machine when it came out. And it probably
takes a lower percentage of the available space on a standard hard disk for
the same timeframe.
Just my 2 cents,
Tim
"Erik Hanson" <ehanson-lists@eh.cdeh.org> wrote in message
news:ehanson-lists-06E248.09455320022004@host98.intellij.net...
>
etc
that
when
your
>
Yes, that's a good point. I didn't think of the non-compete agreement. Although Jetbrains has been around several years now. It's got expire sometime in the near future, no? Not sure how long those things typically last.
And how enforcable are they? Especially if the people who signed them are russian not americans ?
Thanks for the link to Jude. It really is much nicer than the others I've seen.
On Tue, 17 Feb 2004 22:31:07 +0100, Michal Szklanowski wrote:
Full 1.5 Tiger support.
You wouldn't need to worry about complicated setup and protocols with Subversion support built-in. ;) So easy, install it on your server, add the module to Apache, install the client, and the rest goes through HTTP. No need for complicated protocol setup or extra ports on the firewall.
For folks with CVS already, just run "cvs2svn", and away you go.
For the main theme of this thread, my wish list is:
- JSP 2.0 support (incl. EL, JSTL, and tagfiles)
- JDK 1.5 support
JSF support should be possible through resolving taglib URIs, shouldn't it? IDEA 5 could go for the killer feature of visual editing of JSF, like Visual Studio's WebForms. Supporting JDK1.5/JSP2.0 keeps a good lead over Eclipse. I'd say that given that Java is used heavily on enterprise platforms, these are pretty useful features.
AspectJ support sounds good, but there are competing frameworks, such as Aspectwerkz and JBoss AOP. I would guess that while popular, these aren't the most pressing features to add. Maybe IDEA 4.2 ?
Yes, exactly that. CodeGuide currently does that in a very elegant way (with a subtle underline in the to-be-executed statement).
I haven't spotted a SCR for back-in-time debugging, so I filled one: http://www.intellij.net/tracker/idea/viewSCR?publicId=30349
One thing that isn't being (directly) mentioned - JSPX and TAGX (XHTML) formatting should be supported as well.
Maven support would be good too (the MavenConsole plugin that is available is OK, but doesn't work on non-Windows machines.)
Couple of fairly minor things I would like to see - 'close' controls on the editor tabs (see Eclipse and NetBeans 3.6), and a 'modified buffers' view would be quite useful.
Incremental compilation would be quite nice too, come to think of it.