Skip to content

Commit

Permalink
deploy: ecc1e59
Browse files Browse the repository at this point in the history
  • Loading branch information
hecrj committed Mar 18, 2024
1 parent ee4a8c5 commit 6f40e12
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion print.html
Original file line number Diff line number Diff line change
Expand Up @@ -553,7 +553,7 @@ <h1 id="the-runtime"><a class="header" href="#the-runtime">The Runtime</a></h1>
<p>In the previous chapter we built the classical counter interface using iced and The Elm Architecture. We focused on each
fundamental part—one at a time: <strong>state</strong>, <strong>messages</strong>, <strong>update logic</strong>, and <strong>view logic</strong>.</p>
<p>But now what? Yes, we have all the fundamental parts of a user interface—as we learned during
<a href="first-steps.html">our first steps</a>—but it is unclear how we are supposed to bring it to life.</p>
<a href="architecture.html">our dissection</a>—but it is unclear how we are supposed to bring it to life.</p>
<p>It seems we are missing <em>something</em> that can put all the parts together and <em>run</em> them in unison. <em>Something</em> that
creates and runs the fundamental loop of a user interface—displaying widgets to a user and reacting to any interactions.</p>
<p>This <em>something</em> is called the <strong>runtime</strong>. You can think of it as the environment where the feedback loop of a user
Expand Down
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion searchindex.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion the-runtime.html
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ <h1 id="the-runtime"><a class="header" href="#the-runtime">The Runtime</a></h1>
<p>In the previous chapter we built the classical counter interface using iced and The Elm Architecture. We focused on each
fundamental part—one at a time: <strong>state</strong>, <strong>messages</strong>, <strong>update logic</strong>, and <strong>view logic</strong>.</p>
<p>But now what? Yes, we have all the fundamental parts of a user interface—as we learned during
<a href="first-steps.html">our first steps</a>—but it is unclear how we are supposed to bring it to life.</p>
<a href="architecture.html">our dissection</a>—but it is unclear how we are supposed to bring it to life.</p>
<p>It seems we are missing <em>something</em> that can put all the parts together and <em>run</em> them in unison. <em>Something</em> that
creates and runs the fundamental loop of a user interface—displaying widgets to a user and reacting to any interactions.</p>
<p>This <em>something</em> is called the <strong>runtime</strong>. You can think of it as the environment where the feedback loop of a user
Expand Down

0 comments on commit 6f40e12

Please sign in to comment.