luckybilly/CC
CC
CC est un framework de composantisation Android et un outil de modularisation conçu pour transformer des applications monolithiques en composants indépendants. Il fournit un système pour lancer et déboguer des composants individuels en isolation pour réduire les temps de compilation et une couche de communication pour exécuter des fonctions à travers différents processus Android en utilisant une interface unifiée.
Le projet utilise un plugin de bytecode au moment de la construction pour enregistrer automatiquement les composants et les intercepteurs, supprimant le besoin de configuration répétitive manuelle. Il prend en charge la migration d'architecture incrémentielle, permettant à une base de code d'évoluer vers une structure composantisée progressivement sans nécessiter une réécriture complète.
Le framework gère le mappage des composants via des interfaces partagées et achemine les appels via un pipeline de requêtes basé sur l'interception. Ces capacités facilitent la gestion des modules découplés et l'invocation de services inter-processus.
Features
- Android Componentization - Provides a comprehensive framework for modularizing Android applications into independent components.
- Modularization Productivity Tools - Ships a system for launching and debugging individual Android components in isolation to reduce compilation times.
- Isolated Component Bootstrapping - Launches specific modules as standalone applications to allow testing and debugging without compiling the entire project.
- Inter-Process Communication Interfaces - Implements a unified interface for bidirectional communication between separate software processes.
- Bytecode-Based Registrations - Uses a build-time bytecode plugin to automatically register components and interceptors without manual configuration.
- Bytecode-Driven Component Registration - Scans for interface implementations and modifies bytecode to automatically register components and interceptors.
- Cross-Process Communication Systems - Provides a communication layer for executing functions across different Android processes using a unified interface.
- Component Isolation Environments - Enables launching and debugging of individual Android components in isolation for faster development.
- Isolated Execution Workflows - Allows launching and debugging individual components in isolation to avoid compiling the entire application.
- Remote Service Invocations - Executes functions across different processes using a unified interface to hide manual service binding complexity.
- Build-Time Bytecode Transformers - Utilizes a build-time plugin to modify compiled class files and inject registration logic.
- Incremental - Facilitates the gradual adoption of a componentized architectural pattern within an existing codebase.
- Android App Modularization - Transforms monolithic Android applications into modular components to improve maintainability.
- Interface-Based Decoupling - Connects callers to implementations through shared interfaces to decouple components while maintaining type safety.
- Incremental Modularization Strategies - Implements a strategy to convert monolithic applications into components incrementally.
- Incremental Decoupling Strategies - Supports the gradual transition from a monolithic structure to a modular architecture.
- Component Request Pipelines - Routes component calls through a series of interceptors to handle cross-cutting concerns.
