this repo has no description
fix typoes
Misuse of contractions.
See also:
- https://search.brave.com/search?q=it%27s+vs+its
- https://www.merriam-webster.com/grammar/when-to-use-its-vs-its
authored by
Felix Rabe
and committed by
Tim Culverhouse
a3b5b89a
84d6cb38
+6
-6
+5
-5
README.md
+5
-5
README.md
···
137
137
const count_text = try std.fmt.allocPrint(ctx.arena, "{d}", .{self.count});
138
138
const text: vxfw.Text = .{ .text = count_text };
139
139
140
-
// Each widget returns a Surface from it's draw function. A Surface contains the rectangular
140
+
// Each widget returns a Surface from its draw function. A Surface contains the rectangular
141
141
// area of the widget, as well as some information about the surface or widget: can we focus
142
142
// it? does it handle the mouse?
143
143
//
144
-
// It DOES NOT contain the location it should be within it's parent. Only the parent can set
144
+
// It DOES NOT contain the location it should be within its parent. Only the parent can set
145
145
// this via a SubSurface. Here, we will return a Surface for the root widget (Model), which
146
146
// has two SubSurfaces: one for the text and one for the button. A SubSurface is a Surface
147
147
// with an offset and a z-index - the offset can be negative. This lets a parent draw a
···
156
156
.surface = try self.button.draw(ctx.withConstraints(
157
157
ctx.min,
158
158
// Here we explicitly set a new maximum size constraint for the Button. A Button will
159
-
// expand to fill it's area and must have some hard limit in the maximum constraint
159
+
// expand to fill its area and must have some hard limit in the maximum constraint
160
160
.{ .width = 16, .height = 3 },
161
161
)),
162
162
};
···
173
173
.widget = self.widget(),
174
174
// We didn't actually need to draw anything for the root. In this case, we can set
175
175
// buffer to a zero length slice. If this slice is *not zero length*, the runtime will
176
-
// assert that it's length is equal to the size.width * size.height.
176
+
// assert that its length is equal to the size.width * size.height.
177
177
.buffer = &.{},
178
178
.children = children,
179
179
};
···
230
230
use the event loop of their choice. The event loop is responsible for reading
231
231
the TTY, passing the read bytes to the vaxis parser, and handling events.
232
232
233
-
A core feature of Vaxis is it's ability to detect features via terminal queries
233
+
A core feature of Vaxis is its ability to detect features via terminal queries
234
234
instead of relying on a terminfo database. This requires that the event loop
235
235
also handle these query responses and update the Vaxis.caps struct accordingly.
236
236
See the `Loop` implementation to see how this is done if writing your own event
+1
-1
USAGE.md
+1
-1
USAGE.md
···
12
12
Everything after this can be left up to user code, or brought into an event loop
13
13
to be a more abstract application layer. One important part of handling the
14
14
events is to update the Vaxis struct with discovered terminal capabilities. This
15
-
let's Vaxis know what features it can use. For example, the Kitty Keyboard
15
+
lets Vaxis know what features it can use. For example, the Kitty Keyboard
16
16
protocol, in-band-resize reports, and Unicode width measurements are just a few
17
17
examples.
18
18