[ANN] IntelliJad 0.2

IntelliJad 0.2 just got released into the repository. Changes are...
- some of the comments made by ORFJackal have been addressed
- the package exclusion help has been added
- transparent to-memory decompilation is now the default setting
- some cosmetic issues with the console have been addressed

0
2 comments
Avatar
Permanently deleted user

- I noticed that when you decompile a file to memory, the decompiled source file can be edited. I think it would be better if the file would be locked the same way as library sources are locked. It should be editable only after you copy (F5) the file to your project.

- There's a minor usability issue in the configuration window. If the output directory is empty, no error message is shown in the configuration window. The error "!The path to the output directory must be specified.!" is shown only in the IntelliJad Console after you try to decompile a file. There are two ways to fix this issue. Either give an error message in the configuration window (see the attached example) or use a sensible default, such as the project's source folder if the output directory is not specified. The latter way might be best.



Attachment(s):
intellijad-error-message-improvement.png
0
Avatar
Permanently deleted user

I noticed this message: http://www.intellij.net/forums/thread.jspa?threadID=269343&tstart=0#5197333
"while idea doesn't have basic things such as a profiler or a decompiler built in (how about the Eclipse decompiler plugin, which allows one to decompile on the fly while debugging, respecting the original line numbers and allowing one to step in decompiled code?)"

I don't know which Eclipse decompiler plugin he was referring to, but it might be a good idea to find out what it is and how does it work. It might help your development to have a look at how that plugin respects the original line number. And it would be good to check that your plugin will be as good as or better then the Eclipse plugin.

0

Please sign in to leave a comment.