Whats Next - Summary

This is a brief summary of the following threads,




Put together - out of curiosity - the wishlist in no particular order but grouped.

Web Services
+ Consume Web Service - Consume Web Services easily (WSDP 1.4 Integration)
+ Create Web Service
+ Implement a Web Service specified by a WSDP (AXIS Integration?)

Gui Builder
+ Gui builder improvments. Set fonts, colors, icons, etc. A menu and tool bar builder

+ XML/JSP improvements
+ Improved GUI designer
+ JSP improvements

+ JSP 2.0 support
+ Multiple editor window support
+ IDE Modularisation for better plugin support
+ Basic code coverage support (EMMA plugin)
+ Peer review engine
+ Pattern Support / integration (possibly better coupled with ODN support below)
+ Integrated online developer network support (javapractices.com, javaalmanac.com, javaperformancetuning.com, jdoc.com, c2 wiki, etc)

Clear Features
+ Subversion Integration
+ Open API allowing scripting language support with at least 1 language example (Groovy)
+ Pluggable Language Support with pluggable refactorings for those languages
+ Basic SSC support for marginal support of various source control systems
+ Perforce integration equal to Idea 4.5 CVS integration
+ Project support for multiple modules in the same source tree
+ Shared/Remote file viewing by more than one IDE editor. Remote user may edit, etc. Remote file appears with a yellow tab in the tabbed pane.
+ Usability: Custom view filters, Views, Workspaces
+ Breakpoint Workspaces - saved sets of workspaces
+ Logging breakpoint shortcut - at a particular line print out/log the value of a particular expression Create a breakpoint, select its properties from the context menu. Tick the checkboxes "Suspend VM execution" OFF and "Log evaluated expression" ON and enter your expression.

Light/Easy Features
+ Recently used shortcut reference card.
+ Move to Java 5.0
+ Batch inspection, dependancy analysis, duplicates location, etc.
+ Explicit support for generated code - . Generated source directories would be excluded from intention analysis/refactoring.
+ Combine error highlighting settings and inspect tool profiles. Share profiles to other team members.
+ Create Custom Module types ie: Java, Web, Ejb, J2EE, etc.
+ Sample IntelliJ IDEA Plugin Templates - Create new IntelliJ IDEA Plugin Module

+ ANT: Project import from ANT
+ ANT: Queue multiple targets and execute in order
+ ANT: Download common ANT plugins (Plugin Manager Tabs = Installed, Available, ANT Plugins)

Minor Issues
+ All Enable/Disable all breakpoints in a file
+ Refactor: Move private/packaged class to its own source java file.
+ Usability: TAB reordering
+ Ignore intention at a specific place after it has been decided to ignore
+ Dont allow breakpoints when activation never possible.
+ Make a line breakpoint on a method a method breakpoint.
+ Fix focus being grabbed by IDEA on completion (configurable)
+ Fix focus/progress bar - Flashing once for every web/ejb/j2ee is not nice.
+ Backgroundable CVS operations
+ Usability: Window shortcuts to show/hide (alt-5 show/hide debug) (etc...)
+ Remember the selected module/tab in project properties.
+ Configurable File Synchronization Interval - or force sychronize for a particular file
+ Intention: Override method

+ Working/Fixed UNDO
+ Memory leaks: working with multiple projects and opening/closing them.

+ GUI blueprints recommendation / Swing guide
+ Completion/Code completion made accessible through OPEN API.
+ (1) IDEA had the concept of mode-specific keymaps that are only active while in that mode. Besides plugins, it would be nice if IDEA let you change the keys for each special-mode like completion, incremental-search, live templates, etc. You could also fix these while you're at it:
+ 12355 Auto-format of whitespace according to coding style
+ 12357 SmartKey Brace opening { and closing brace }
+ (2) IDEA needs the concept of modes and submodes so that plugins can determine the full context in callbacks.
+ (3) It should be easier to override the key handler for any character, and also be able to defer back to the default handler for that character.
+ Saner approach to bugrporting. Volume is high, important stuff slips through.

Comment actions Permalink

To get rid of the native2ascii "compilation pass" we have writter our own resource bundle that can read UTF-8 encoded files (or any other encoding: it looks for a emacs-style comment in the first line, like -- charset:shift-jis --). It seems so illogical that everything in java is based around unicode, but proporty files must be latin-1 encoded.

Comment actions Permalink

Miles away :)))

Comment actions Permalink

No , but why U want to do it after, It needs to be done before document saving, I think ?

Comment actions Permalink

My situation is totaly different - I'm editing the translated values quite frequently. Anyway, why it should be hard , when it can be easy - just check the SunONE studio editor.

Comment actions Permalink

lllopo wrote:

My situation is totaly different - I'm editing the translated values quite frequently. Anyway, why it should be hard , when it can be easy - just check the SunONE studio editor.

The problem I see is that you are becoming dependent on the tool. I.e.
such feature encourages you not to keep the source version, because you
can always edit the escaped version. And sometimes when you are on the
client's site that doesn't have IDEA installed it becomes a problem.
Also, some of your peers might like emacs (in fact here they use 'mule'
which is some emacs clone.)

Anyway - the obvious answer here is "if you don't like it - don't use
it" and I surely won't, so I should stop commenting on this thread :)

-- dimiter

Comment actions Permalink

After document saving content must be replaced with decoded content to allow edit file.


Comment actions Permalink

I'm not getting dependent on the tool, I just want the tool to keep easing my work in all aspects. So ... U're right - if U won't use it, don't comment it :)).

Comment actions Permalink

I see it like this :
in memory document (buffer) - decoded; on disk (saved) content - encoded. Am I wrong ?

Anyway, let's move this discussion in the plug-ins forums, ok ?

Comment actions Permalink

I'd like to see TODO working on all (text) file types.
Some sort of formatting capability for other source files would be very nice too -- e.g. JavaScript, HTML, etc.

Mike L.

Comment actions Permalink

Ok, 10x. I'll check it out.

Comment actions Permalink

- Refactor: Inline all deprecated methods

When deprecating a particular function I rewrite the function in terms of the new interfaces/whatever, if possible. Being able to scan a project and mass 'Inline All'... would be funky.

It would be important to be able to read the deprecated message attached to a deprecated method aswell as group refactorings by file, method, etc.

The option to keep the inlined method is also nifty. Sometimes you just want to get your code to a 'happy' state of affairs without breaking other dependancies/libraries that have not yet been refactored.

Comment actions Permalink

Being able to keep the original method might also be funky... typically those methods that you have no control over... 3rd party libraries, etc.

Comment actions Permalink

lllopo wrote:

Well, I think this is essential for an IDE that

supports J2EE/WEB programming ... and it's really
There's no JavaScript editor at the moment that knows
"intelligent" code
completion, code navigation, find usages, etc.
Jetbrains would have a real advantage over Eclipse
and the others with
such a feature, but it seems to me that "Subversion
Integration" has
much more lobby :(.


I wholeheartedly and completely agree. I have been searching for a decent JavaScript editor (and would even settle for a lousy one at this point). I see the lack of any intelligent JavaScript editor/IDE as a gapping market opportunity and such an inclusion in IntelliJ IDEA would, as someone mentions, be a huge feather in JetBrain’s cap. As a web application developer, I agree that IDEA needs to get JSP 2.0 support implemented, but I do not think that JS support should wait on such. Additionally, since the developers of JS functionality would need to know a whole different API/Specification list then the JSP developers, I would see this as being a different team anyways.

For those that argue “I don’t do much with JavaScript and therefore do not need this feature”, I would argue that the less JS editing you do, the more you need good JS support in the IDE (assuming you do some JS work). If you are not readily familiar with what an exact method or property is named, but know (or suspect) that such a method/property exists, code completion can help you find it in seconds rather then the minutes (or hours) it takes to look it up in a reference. And who hasn’t mistyped a function name, only to find it at testing time rather then via error highlighting?

A major plus if such a feature were implemented would be some equivalent of Javadoc; that is allow ctrl-Q to open a documentation reference window.

The list can grow, but code completion, syntax awareness, and error highlighting would be a great start.


Please sign in to leave a comment.