docs

Author: jamesdbrock

_modules/edifice/run_subprocess_with_callback.html

@@ -406,9 +406,9 @@ <h1>Source code for edifice.run_subprocess_with_callback</h1><div class="highlig
 
 <span class="c1"># Edifice run_subprocess_with_callback 2025 by James D. Brock</span>
 <span class="c1">#</span>
-<span class="c1"># This run_subprocess_with_callback module file depends only on the Python</span>
-<span class="c1"># standard library so it can copied and pasted into any project without</span>
-<span class="c1"># modification.</span>
+<span class="c1"># This run_subprocess_with_callback module depends only on the</span>
+<span class="c1"># Python standard library so this module file can be copied and pasted into</span>
+<span class="c1"># another project without depending on the Edifice package.</span>
 
 
 <span class="kn">from</span> <span class="nn">__future__</span> <span class="kn">import</span> <span class="n">annotations</span>
@@ -695,6 +695,12 @@ <h1>Source code for edifice.run_subprocess_with_callback</h1><div class="highlig
 <span class="sd">    `before the __main__ imports &lt;https://pyinstaller.org/en/stable/common-issues-and-pitfalls.html#when-to-call-multiprocessing-freeze-support&gt;`_</span>
 <span class="sd">    so that the spawn Process starts up faster.</span>
 
+<span class="sd">    Independence</span>
+<span class="sd">    ^^^^^^^^^^^^</span>
+
+<span class="sd">    This :func:`run_subprocess_with_callback` module depends only on the</span>
+<span class="sd">    Python standard library so this module file can be copied and pasted into</span>
+<span class="sd">    another project without depending on the Edifice package.</span>
 <span class="sd">    &quot;&quot;&quot;</span>
 
 

_sources/edifice.rst.txt

@@ -193,12 +193,16 @@ which has child Elements representing different parts of your application.
 Dynamic Rendering
 ^^^^^^^^^^^^^^^^^
 
-For dynamism, use conditions and loops in your :func:`@component <component>`
-render function.
-The conditions and loops can depend on **props** or **state**. For example,
+For dynamism, use Python control flow
+statements :code:`if` :code:`for` :code:`match` in
+your :func:`@component <component>` render function.
+The control flow statements can depend on **props** or **state**. For example,
 this :func:`@component <component>` will render input fields only while
 the **props** indicate that they are wanted.
 
+- When the :code:`want_username` **prop** becomes :code:`True` then the entire username subtree will be added.
+- When the :code:`want_username` **prop** becomes :code:`False` then the entire username subtree will be removed.
+
 .. code-block:: python
 
     @component

_sources/index.rst.txt

@@ -153,7 +153,9 @@ Edifice programs are written in Python.
 
 Because Edifice programs are only Python, binding to the
 UI is much more straightforward.
-Edifice makes it easy to dynamically create, mutate, shuffle, and destroy sections of the UI.
+Edifice makes it easy to dynamically create, mutate, shuffle, and destroy
+sections of the UI with Python control flow statements
+:code:`if` :code:`for` :code:`match`.
 Qt Quick assumes a much more static interface.
 
 Qt Quick is like DOM + HTML + JavaScript, whereas Edifice is like React.

edifice.html

@@ -554,11 +554,16 @@ <h2>Declaring Element Trees<a class="headerlink" href="#declaring-element-trees"
 which has child Elements representing different parts of your application.</p>
 <section id="dynamic-rendering">
 <h3>Dynamic Rendering<a class="headerlink" href="#dynamic-rendering" title="Link to this heading">#</a></h3>
-<p>For dynamism, use conditions and loops in your <a class="reference internal" href="stubs/edifice.component.html#edifice.component" title="edifice.component"><code class="xref py py-func docutils literal notranslate"><span class="pre">&#64;component</span></code></a>
-render function.
-The conditions and loops can depend on <strong>props</strong> or <strong>state</strong>. For example,
+<p>For dynamism, use Python control flow
+statements <code class="code docutils literal notranslate"><span class="pre">if</span></code> <code class="code docutils literal notranslate"><span class="pre">for</span></code> <code class="code docutils literal notranslate"><span class="pre">match</span></code> in
+your <a class="reference internal" href="stubs/edifice.component.html#edifice.component" title="edifice.component"><code class="xref py py-func docutils literal notranslate"><span class="pre">&#64;component</span></code></a> render function.
+The control flow statements can depend on <strong>props</strong> or <strong>state</strong>. For example,
 this <a class="reference internal" href="stubs/edifice.component.html#edifice.component" title="edifice.component"><code class="xref py py-func docutils literal notranslate"><span class="pre">&#64;component</span></code></a> will render input fields only while
 the <strong>props</strong> indicate that they are wanted.</p>
+<ul class="simple">
+<li><p>When the <code class="code docutils literal notranslate"><span class="pre">want_username</span></code> <strong>prop</strong> becomes <code class="code docutils literal notranslate"><span class="pre">True</span></code> then the entire username subtree will be added.</p></li>
+<li><p>When the <code class="code docutils literal notranslate"><span class="pre">want_username</span></code> <strong>prop</strong> becomes <code class="code docutils literal notranslate"><span class="pre">False</span></code> then the entire username subtree will be removed.</p></li>
+</ul>
 <div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="nd">@component</span>
 <span class="k">def</span> <span class="nf">MyApp</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">want_username</span><span class="p">:</span><span class="nb">bool</span><span class="p">,</span> <span class="n">want_email</span><span class="p">:</span><span class="nb">bool</span><span class="p">):</span>
     <span class="k">with</span> <span class="n">Window</span><span class="p">():</span>

index.html

@@ -507,7 +507,9 @@ <h3>Edifice vs. Qt Quick<a class="headerlink" href="#edifice-vs-qt-quick" title=
 <p>Edifice programs are written in Python.</p>
 <p>Because Edifice programs are only Python, binding to the
 UI is much more straightforward.
-Edifice makes it easy to dynamically create, mutate, shuffle, and destroy sections of the UI.
+Edifice makes it easy to dynamically create, mutate, shuffle, and destroy
+sections of the UI with Python control flow statements
+<code class="code docutils literal notranslate"><span class="pre">if</span></code> <code class="code docutils literal notranslate"><span class="pre">for</span></code> <code class="code docutils literal notranslate"><span class="pre">match</span></code>.
 Qt Quick assumes a much more static interface.</p>
 <p>Qt Quick is like DOM + HTML + JavaScript, whereas Edifice is like React.
 QML and HTML are both declarative UI languages but

objects.inv

@@ -591,6 +591,12 @@ <h2>PyInstaller<a class="headerlink" href="#pyinstaller" title="Link to this hea
 <a class="reference external" href="https://pyinstaller.org/en/stable/common-issues-and-pitfalls.html#when-to-call-multiprocessing-freeze-support">before the __main__ imports</a>
 so that the spawn Process starts up faster.</p>
 </section>
+<section id="independence">
+<h2>Independence<a class="headerlink" href="#independence" title="Link to this heading">#</a></h2>
+<p>This <a class="reference internal" href="#edifice.run_subprocess_with_callback" title="edifice.run_subprocess_with_callback"><code class="xref py py-func docutils literal notranslate"><span class="pre">run_subprocess_with_callback()</span></code></a> module depends only on the
+Python standard library so this module file can be copied and pasted into
+another project without depending on the Edifice package.</p>
+</section>
 </dd></dl>
 
 </section>