more words, remove superfluous code

Author: willmcgugan

docs/blog/posts/release1.0.0.md

@@ -8,13 +8,42 @@ authors:
   - willmcgugan
 ---
 
-Version 1.0 announcements often come with a happy hour and merch.
-Well we haven't got any merch.
 
+I've had the fortune of being able to work fulltime on a FOSS project for the last three plus years.
 
-## The Compositor
 
+!!! tip inline end "Textual Demo"
+
+    [![Textual Demo](../images/textual-demo.svg)](https://github.com/textualize/textual-demo)
+
+
+Textual has been a constant source of programming challenges, often frustrating but never boring.
+The challenges arise because the terminal "specification" says nothing about how to build a modern User Interface on top of it.
+The building blocks are there.
+After some effort you can move the cursor, write colored text, read keys and mouse coordinates, but that's about it.
+Everything else we had to build from scratch: from the most basic [button](https://textual.textualize.io/widget_gallery/#button) to a syntax highlighted [TextArea](https://textual.textualize.io/widget_gallery/#textarea), and everything along the way.
+
+I wanted to write-up some of the more interesting solutions we came up with.
+The 1.0 milestone we just passed makes this the perfect time.
+
+If you haven't followed along with Textual's development, here is a demo of what it can do.
+This is a Textual app, running remotely, served by your browser:
+
+??? textualize "Try in Textual-web"
+
+    <div class="textual-web-demo" data-app="demo"></div>
+
+I cheaped out on the VMs &mdash; so if the demo is down, you could run it locally (with [uv](https://docs.astral.sh/uv/)):
 
+```
+uvx --python 3.12 textual-demo
+```
+
+
+
+## The Compositor
+
+The first component of Textual I want to cover is the *compositor*.
 The job of the compositor is to combine widgets in to a single view.
 
 We do this because the terminal itself has no notion of overlapping windows in the way a desktop does.
@@ -39,18 +68,18 @@ Textual's way of handling this is inherited from [Rich](https://github.com/Textu
 Anything you print in Rich, first generates a list of [Segments](https://github.com/Textualize/rich/blob/master/rich/segment.py) which consist of a string and associated style.
 These Segments are only converted into text with [ansi escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code) at the very last moment.
 
+
 Textual works with same Segment object.
-Widgets all produce a list of segments, which are further processed by the compositor.
+Widgets all produce a list of segments, which is further processed by the compositor.
 
 !!! tip "Switch the Primitive"
-
-    I hope I've earned the opertunity to dispense unsolicited pearls of wisdom.
+    
     If a problem is intractable, it can often be simplified by changing what you consider to be the fundamental atomic data and operations you are working with.
     I call this "switching the primitive".
 
 ### Thinking in Segments 
 
-In the following illustration we have an app with three widgets; the "screen" (in blue) plus two floating widgets (in red and green).
+In the following illustration we have an app with three widgets; the background "screen" (in blue) plus two floating widgets (in red and green).
 There will be many more widgets in a typical app, but this is enough to show how it works.
 
 
@@ -73,10 +102,9 @@ It would appear something like the following:
 --8<-- "docs/blog/images/compositor/cuts0.excalidraw.svg"
 </div>
 
-Those lines are produced when the widget is rendered and consist of a list of segments.
+We can't yet display the output as it would require writing each "layer" independantly, potentially making the terminal flicker, and certainly writing more data than neccesary.
 
-We want to combine these lists into a single list that covers the width of the terminal.
-That way we can update everything in a single write.
+We need a few more steps to combine these lines in to a single line.
 
 
 ### Step 1. Finding the cuts.
@@ -96,25 +124,28 @@ This will produce smaller lists of segments, which in the compositor code we ref
 --8<-- "docs/blog/images/compositor/cuts2.excalidraw.svg"
 </div>
 
+These chops have the property that nothing overlaps, which is important for the next step.
 
 ### Step 3. Discard chops.
 
-Only the top-most chops will actually be visible to the viewer, so we can discard any chop that isn't at the top.
+Only the top-most chops will actually be visible to the viewer.
+Anything not at the top can simply be thrown away.
 
 <div class="excalidraw">
 --8<-- "docs/blog/images/compositor/cuts3.excalidraw.svg"
 </div>
 
 ### Step 4. Combine.
 
-Now all that's left is to combine the top-most chops in to a single list of Segments.
-
-It is this list of segments that becomes a line in the terminal.
+Now all that's left is to combine the top-most chops in to a single list of Segments. It is this list of segments that becomes a line in the terminal.
 
 <div class="excalidraw">
 --8<-- "docs/blog/images/compositor/cuts4.excalidraw.svg"
 </div>
 
+this is done for ever line in the output.
+At the end of it we have a list of segments for each line, ready to be converted in to escape sequences and written to the terminal.
+
 ### What I omitted
 
 There is more going on than this explanation may suggest.
@@ -124,4 +155,3 @@ Additionally, the compositor can do partial updates.
 In other words, if you click a button and it changes color the compositor can update just that button.
 
 The compositor does all of this fast enough to enable smooth scrolling, even with a metric tonne of widgets on screen.
-Surprising fast, given it is essentially number crunching, which isn't considered Python's forté.

src/textual/_layout_resolve.py

@@ -1,6 +1,5 @@
 from __future__ import annotations
 
-from dataclasses import dataclass
 from fractions import Fraction
 from typing import Sequence, cast
 
@@ -18,13 +17,6 @@ class EdgeProtocol(Protocol):
     min_size: int
 
 
-@dataclass
-class Edge:
-    size: int | None = None
-    fraction: int | None = 1
-    min_size: int = 1
-
-
 def layout_resolve(total: int, edges: Sequence[EdgeProtocol]) -> list[int]:
     """Divide total space to satisfy size, fraction, and min_size, constraints.