How alekpet/comfyui_custom_nodes_alekpet works
Main Components
• Translation Nodes (ArgosTranslateNode, ChatGLMNode, DeepTranslatorNode, GoogleTranslateNode)
• Instruction Nodes (ChatGLM4InstructNode, ChatGLM4InstructMediaNode)
• Image/Media Nodes (PoseNode, PainterNode)
• Extras/Utilities (ExtrasNode, PreviewTextNode, ColorsCorrectNode, HexToHueNode)
• Code Execution/Experimentation (IDENode)
• Supporting Assets: For nodes that have additional resources (e.g., PainterNode and PoseNode), include subcomponents for their assets (JS, CSS, fonts, brushes) and libraries.
• Infrastructure and Dependencies: Highlight the use of configuration files (like config.json), package management (requirements.txt, pyproject.toml) and integration modules (JavaScript frontends, additional libraries in lib folders).
Relationships and Interactions
• For nodes like IDENode, indicate bi-directional communication since it can run both Python and JavaScript code dynamically.
Architectural Patterns and Design Principles
• Modular/microservices-like design where each node is a self-contained module with its own folder that includes code, configuration, and assets.
• Separation of concerns: the business logic in Python versus the presentation or interactive parts in JavaScript/CSS.
• Reusable components or libraries that are shared among nodes (e.g., the usage of fabric.js in both PainterNode and PoseNode).
Technologies and Frameworks
• Python is the primary back-end language for node logic.
• JavaScript, CSS, and additional front-end libraries (e.g., ace-builds and fabric.js) support interactive and UI functionality.
• Configuration management via JSON (config files) and package definition through requirements.txt and pyproject.toml.
• GitHub workflows and CI/CD pipelines (as indicated by the .github/workflows folder) that support auto-publishing/deployment.