wink wink, nudge nudge...
So who will be the first to find the codename for the next version?
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
Please sign in to leave a comment.
Robert Sfeir wrote on 30/09/05 06:45:
Actually - a KICK FREAKEN ARSE OpenAPI -AND- kick arse Struts/Hibernate
plugins.
The plugins don't need to be shipped "with" IDEA, but shiped via the
plugin manager. More work on the OpenAPI would be great to allow these
further plugins.
What I miss most is support for AspectJ. I'm currently not using aspects
although they would be VERY helpful for both performance and stability.
I know I'm not the only one ... I think that now is the time to
implement it, because in it's latest development version AspectJ can be
implemented using annotations and full Java 5 support.
Appart from that feature, I agree that it would be best to focus on
stability, performance and usability improvement for the next major version.
>> Seriously though... how about very few new features with lots of solid
>> improvements in the area of:
>>
>> 1- Usability
>> 2- Speed
>> 3- UI
Here we go...
"Michael Riess" <mlriess@gmx.de> wrote in message
news:dhira8$trj$1@is.intellij.net...
>
>
>> Robert Sfeir wrote:
>>
>>> Seriously though... how about very few new features with lots of solid
>>> improvements in the area of:
>>>
>>> 1- Usability
>>> 2- Speed
>>> 3- UI
>>
>>
>> Sounds like a very good idea. For the last several major releases I've
>> wished for an x.1 release which focuses on polishing and rounding out the
>> existing features (such as @Nullable and @NotNull which has many
>> outstanding requests that wouldn't be that difficult to implement),
>> adding new minor features and fixing bugs. Unfortunately I guess
>> adding new major features is what sells new copies...
Hello Rambabu,
RT> Hello Robert,
RT> Plugins support only basic functionality not advanced. All
RT> commerical
RT> IDEs (JDev, Netbeans, Eclipse + myeclipseide ...) support the struts
RT> development.
so? :) come on we're not going to get into the they did this and we do
that... these IDEs are sorely lacking in refactoring too, does this mean
jetbrains should put less effort into that too?
R
Perl support. Lets stop messing around here.
Nick Pratt wrote:
Nah, we need COBOL.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001
OK, since we have gone off the deep end, how about adding lisp support so I can reuse all my old emacs customizations/extensions... 8^)
Don't stop messing! The mess is quite interesting and being informal it better
shows (IMO) what's really interesting to the IDEA users comparing to let
say JIRA.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
That's 2 requests for lisp support. I believe that makes a majority:)
"Ralph Saunders" <no_mail@jetbrains.com> wrote in message
news:1587151.1128107517073.JavaMail.itn@is.intellij.net...
Michael Riess wrote on 30/09/05 20:00:
AspectJ support was started, but then put on hold. But from what I've
seen, AspectJ moved towards annotations, and a whole slew of alternative
AOP frameworks came into play.
What -would- be good, is an OpenAPI AOP Framework which provides support
for say SpringAOP, AspectJ (which may include a language and compiler
plugin), JBossAOP plugin etc.
"Rambabu Talasila" <rambabut@gmail.com> wrote in message
commerical
the struts development.
No any sense to support Struts at this point, it is over the
hill. Support for JSF/Spring (though I don't use them but I
believe that I will have to) will be a HUGE marketing plus.
I personally would prefer Wicket support, especially there
is no much to support, just to map pages to classes and HTML
custom attributes to object hierarchy.
Michael.
Couldn't agree more - I've stopped creating JIRA entries, simply because the ones I've already raised are still there and have been since release.
If anything I would say that the most recent EAP builds are less stable and perform worse than the initial release, and I wasn't impressed with that! When I can actually use the J2EE deployment reliably, along with CVS integration without crashing, then I'll be happy.
+1.32 billion
Direct manipulation instead of dialog boxes:
- alt-click on a word to select it as a symbol rather than as text. Then you could rename it (and all usages would of course get renamed). If the symbol was a parameter, you could delete the symbol and the method's signature would change (and of course all usages would be changed). Or drag the parameter to a new position. Or alt-click some blank space in the parameter list to add a new one.
- drag and drop classes between packages in the file view
- alt-drag a class to copy it.
- alt-drag a method up to the editor tab list, pause over the editor you want, it comes to the foreground, and you can drop the method where you want in that class.
- alt-drag a variable from inside a method to inside the class to convert it from a variable to a field
- alt drag a method to the name of the current class' parent class in the class definition ("foo extends bar") to move the method up a level
I could go on and on, but I'm sure you get the idea. Go through and see how many dialog boxes you can replace with direct manipulation. (You can leave the dialog boxes there, because sometimes they might be easier to use, and they certainly are more obvious for beginners.)
I would love this! It would be great if I didn't have to move my hand away from my
trackball during a refactoring operation!
Just remember all of the people who don't like to move their hands away from the keyboard
and provide keyboard shortcuts as well. I personally have a hard time remembering all of
the key combinations, but I've been around the forums long enough to know that if you
provide a feature that is not available using only the keyboard, there will be a lot of whining.
I would agree as well. Where I work, several developers have made the switch (albeit, reluctantly) to Eclipse because they've found IntelliJ too unstable to use. (Though it's been pretty stable in my own use)
David