Search Results for "javassist"

Javassist (JAVA programming ASSISTant) makes Java bytecode manipulation simple. It is a class library for editing bytecodes in Java; it enables Java programs to define a new class at runtime and to modify a class file when the JVM loads it. Unlike other similar bytecode editors, Javassist provides two levels of API: source level and bytecode level.

Booster is an easy-to-use, lightweight, powerful and extensible quality optimization toolkit designed specially for mobile applications. The primary goal is to solve quality problems with the increase of APP complexity, such as performance, stability, and package size, etc. Booster provides a collection of modules for performance detection, multithreading optimization, resources index inline, redundant resources reduction, resources compression, system bug fixing, etc. Using booster, the...

Jour is designed to simplify the use of Javassist for processing multiple classes. In short Jour is simple Aspect Oriented Programming AOP framework on top of Javassist.

...Gradle execution process, what is DSL, domain-specific language, common usage of Gradle, usage of Gradle advanced plug-ins, Gradle optimization for Android, using Javassist to the next floor, and problems encountered in Gradle development. Demonstration of plugin application in other modules. Plugin configuration and metadata.

Optimized version of MVP, using annotation generics to simplify code writing, using modular protocols to facilitate maintenance, APT process uses annotation parser to use JavaPoet. Complete the writing of repetitive modules, use ASpect+GradlePlugin to complete horizontal AOP programming+Javassist dynamic bytecode injection+Tinker to achieve hot repair+Retrofit to achieve elegant network operations+RxJava to easily play with data processing. In MVP, Presenter completely separates Model and View, and the main program logic is implemented in Presenter. Moreover, the Presenter is not directly related to the specific View, but interacts through the defined interface (we only need to pass parameters according to the interface when testing alone), so that the Presenter can be kept unchanged when changing the View. i.e. reuse! ...