|
|
|
|
|
|
by lyall
10 days ago
|
|
|
The layout is done entirely in DOM. The layout engine calculates the line breaks, tracking, expansion, etc. then applies the layout using HTML spans with the appropriate attributes applied. There’s generally one span per line, but that can change for more complicated lines! I invite you to inspect the demo page in your browser’s dev console if you’re particularly curious. And yes, I did use LLMs for the implementation, both Fable 5 and 5.6 Sol specifically. I would not have been able to achieve anywhere close to the current result unaided. My patience and expertise would’ve been exhausted long before getting anywhere especially interesting. My philosophy with LLMs is to try to use them to achieve levels of quality and polish that would’ve been previously unreasonable. I hope this project is a demonstration of that. |
|
|
> My philosophy with LLMs is to try to use them to achieve levels of quality and polish that would’ve been previously unreasonable. I hope this project is a demonstration of that.
This philosophy has been growing on me - a coworker framed it as “nuance melts away with LLMs”
I recently wanted to render a 100+ page document in an interactive WYSIWYG editor using a single stroke font and join the letters to form single stroke cursive words that appeared handwritten.
The permutations of rulesets that governed connections between letters (I.e. how does t connect to c, and do you need to lift the pen to make that connection) amplified by the randomness injected into the strokes and line width/angle (handwriting doesn’t have uniform letters or lines!) would have been intractable previously.
But, with an agent harness, I could do 3 or 4 examples of what “right” looked like - give it the ability to generate and screenshot test cases to see the output of its work - and it could grind through a reasonable ruleset for about $20 in spend.