LCARS Text editor in Raylib This is the continuation in the series of LCARS app development:
LCARS Elbow LCARS Frame This time I focused on implementing a text editor from scratch in Raylib.
This is for something like the personal log / Captain’s log use-case.
Full screen version available here
Features Mouse over text area to allow editing text Insert text - only at the end for now… Will work on a gab buffer or something in the future to allow moving the cursor and edit text anywhere.
LCARS frame in Raylib Continuation from last post about designing the LCARS elbow. I continued with making the full frame and add some interactivity to it.
Full screen version available here
Github Code Repo
LCARS Elbow designer in Raylib Just a fun little project for designing LCARS elbows. Click ’d’ key for debug view. Code: https://github.com/saftacatalinmihai/lcars/blob/main/lcars.c
This is a tale of software architecture decision-making in large companies.
The setup As part of my job as a software architect, I had to design a solution which involved the integration between 2 systems: let’s call them A and B. They were part of a new instant payment processing flow that was beeing developed. System B had a legacy integration mechanism that was no longer supported at the architectural level.
๐ Re-Creating Star Trek’s LCARS Computer With Modern LLMs A hands-on experiment in autonomous tool-building agents
1 ยท Why LCARS? For decades science-fiction fans have watched Star Trek officers converse with a ship-wide computer LCARS (“Library Computer Access/Retrieval System”). LCARS could:
answer arbitrary questions by searching internal databases; execute real-world actions by routing commands to subsystems; politely say why it couldn’t comply when limits were hit. In 2025, large language models (LLMs) plus tool-calling APIs make that dream feel within reach.
Add I’ve added a new tldraw tool called Stream Component (left-most icon: </> in the toolbar, shortcut key S). You can click or draw a rectangle to add a stream component to the canvas.
The component is not initialized at first - you need to select the component type from the drop-down menu. This UI will be improved to allow more discoverability, show descriptions of components, etc.
After selecting the component type, it will be initialized (started in the backend) and begin running immediately, waiting for inputs on its input port(s).