How httpskwiksx/bridge-pattern works
This small Java example demonstrates the Bridge pattern: the demo creates shapes and rendering implementations, then calls each shape’s execute method to obtain formatted output. Shape subclasses delegate rendering through the Renderer interface, allowing Circle and Square objects to switch among vector, raster, and ASCII implementations without changing their shape state. Main.java also exercises a runtime implementation switch. The README is only a title, so the architecture is based on the sampled source; no external services or persistent state are shown.
Main entry points: Main.java Demo runner · Renderer.java Renderer interface · Circle.java Circle · Square.java Square
Components 8
Demo entry
- Demo runner
src/Main.java
Shape model
- Shape base
src/Shape.java - Circle
src/Circle.java - Square
src/Square.java
Rendering
- Renderer interface
src/Renderer.java - Vector renderer
src/VectorRenderer.java - Raster renderer
src/RasterRenderer.java - ASCII renderer
src/AsciiRenderer.java
Connections 13
- Demo runner → Circle: creates, executes
src/Main.java - Demo runner → Square: creates, executes
src/Main.java - Demo runner → Vector renderer: instantiates
src/Main.java - Demo runner → Raster renderer: instantiates
src/Main.java - Demo runner → ASCII renderer: instantiates
src/Main.java - Circle → Shape base: extends
src/Circle.java - Square → Shape base: extends
src/Square.java - Shape base → Renderer interface: stores, switches
src/Shape.java - Circle → Renderer interface: delegates rendering
src/Circle.java - Square → Renderer interface: delegates rendering
src/Square.java - Vector renderer → Renderer interface: implements
src/VectorRenderer.java - Raster renderer → Renderer interface: implements
src/RasterRenderer.java - ASCII renderer → Renderer interface: implements
src/AsciiRenderer.java