Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several issues making Recaf more difficult to use than it should be #663

Open
zDEFz opened this issue Aug 20, 2023 · 3 comments
Open

Several issues making Recaf more difficult to use than it should be #663

zDEFz opened this issue Aug 20, 2023 · 3 comments

Comments

@zDEFz
Copy link

zDEFz commented Aug 20, 2023

Here are the issues I faced that keep me from working efficiently:

  • Lack of switching from decompilation to table view via shortcut
  • Lack of ability to create a new field
  • Lack of ability to duplicate a method
  • Lack of ability to work in obfuscated / illegal code when using the decompilation view
  • Lack of ability to bookmark classes / making comments
  • Lack of ability to change all classes file version at once (this is particularly interesting if you have newer code in older compilations). In the past I had to automate this via Autohotkey
  • Lack of open the assembly where the search result is at, while marking the result in the list.
  • Saving and then exporting a newly inserted bytecode often results in a partially NOP'ed bytecode. Reason unknown
  • Hangs, crashes after hours of working in the program, losing progress as a result

When I need to duplicate a method, I would require to open JByteMod, duplicate it, and then go to recaf.
When I want to create a new Field, I have to download DirtyJoe and run it through wine (yikes) and then create the UTF8 string, field and fieldreference or so.

@Amejonah1200
Copy link

Have you tried 3x?

@zDEFz
Copy link
Author

zDEFz commented Aug 20, 2023

Have you tried 3x?

I will update this post everytime I find more.

Findings

  • Lack of ability to add a Field in a Method (copy and pasting a existing one works)
  • Lack of ability to create a folder within the jar (for refactoring)
  • Lack of running a deobfuscator through a jar. e.g like https://github.com/java-deobfuscator/deobfuscator . Note that it requires a jdk+jfx set with jce, jsse, ace, rt jarfiles. This is especially helpful for obfuscated strings and works reliably
  • Lack of bookmarking system. Especially in convoluted setups kinda a must.
  • Lack of saving bytecode-snippets / java snippets for doing simple things
  • Lack of commenting bytecode (might be serving as a file outside the actual jar?)
  • Lack of class-specific logging
  • Lack of extraction of a class file
  • Lack of taking parts of the UI into fullscreen rather than dragging it. e.g logs

Controversial?

  • Lack of ability to work in obfuscated / illegal code when using the decompilation view

@zDEFz
Copy link
Author

zDEFz commented Sep 14, 2023

  • Add ability to immediately save to the jarfile we are editing.
    I don't know how many time it cost me, to save the bytecode, and the use the save as ... dialog.

My request has two parts in it:

  • Via shortcut, e.g CTRL+Shift+S for saving the current progress immediately to the currently opened file
  • To change the behavior to also immediately change the altered bytecode, without prior having to CTRL+S

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants