Well, JDGui doesn\'t seem to handle case sensitivity. Ad.class is the main entity class, but in the source you have there is only ad.class.
JDO is a de-obfusticator, not a decompiler. You use it as a pre-processor to a decompiler. It takes care of case names in the class files and multiple method names that are identical. So I think we should use *both* .
JD is more modern that JAD. But there\'s still some things that JAD does better. In the hand-work I\'ve done I\'ve mostly used JAD (partly because it was written by an IBMer!) but pulled in from JD when it had a better interpretation. I think settling on one is the only sane way to proceede. I like that you can route name via a .csv file. So I\'cool with JDGui if you find that most convienent.
JDO is a de-obfusticator, not a decompiler. You use it as a pre-processor to a decompiler. It takes care of case names in the class files and multiple method names that are identical. So I think we should use *both* .
JD is more modern that JAD. But there\'s still some things that JAD does better. In the hand-work I\'ve done I\'ve mostly used JAD (partly because it was written by an IBMer!) but pulled in from JD when it had a better interpretation. I think settling on one is the only sane way to proceede. I like that you can route name via a .csv file. So I\'cool with JDGui if you find that most convienent.