/3 Improving Readability & Engagement – The Rich Library Integration (Solidsight v5, v6, & v7)

Search for a command to run...

No comments yet. Be the first to comment.
In this series, I will venture the down a path of development using various languages, mainly Python, and utilise AI for the majority if not all of the code generation.
Overview Versions 4 and 5 saw significant strides in workflow optimisation, making the SFA more practical and user-friendly. Efficiency and redundancy elimination became central to these iterations. Duplicates A key feature introduced was a robust du...
The Need for Rigorous Validation As Solidsight matured, accuracy became paramount. One key improvement was ensuring generated Mermaid diagrams were accurate and meaningful, addressing the occasional production of invalid placeholder diagrams by the L...

Rationale for Session Management As Solidsight's capabilities expanded, managing historical analysis data became increasingly important. The next logical step was introducing structured session management, allowing users to revisit previous analyses ...

Expanding the Tool's Capabilities Smart contract analyses can vary greatly in complexity and purpose. Realising this, I added support for multiple LLM models, allowing users to tailor analyses according to specific needs. This flexibility transformed...

Overview Versions 4 and 5 saw significant strides in workflow optimisation, making the SFA more practical and user-friendly. Efficiency and redundancy elimination became central to these iterations. Duplicates A key feature introduced was a robust du...

Although Solidsight was becoming powerful, its plain text outputs lacked readability. To address this, I integrated the Rich library, significantly enhancing the visual appeal and clarity of the command-line interface.
Rich transformed simple outputs into coloured, visually structured messages and tables:
pythonCopyEditfrom rich.console import Console
console = Console()
console.print("[bold green]Analysis Complete![/bold green]")
Initially, Rich caused display anomalies in certain terminals. Compatibility across different terminal emulators required additional tweaking.
Adding Rich significantly improved user interaction, facilitating clearer communication of results and easier debugging during development.
We will stop here, and I’ll see you on the next one.
pxng0lin.