Product: Mingcedar Studio DESIGNER

Learning paths: getting started, reuse and development | Mingcedar Studio

Choose a path, complete a working screen, then consult field references and advanced tutorials.

Published 2026-10-25T12:48:42.67088892Z Updated 2026-10-26T19:56:55.667266081Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="learning-paths">Start here: Learning paths: getting started, reuse and development</h2>

Choose a path, complete a working screen, then consult field references and advanced tutorials.

<h3 id="learning-paths-item-1">Evaluating the product: understand the delivery boundary</h3>

<p>Draw in PowerPoint, add behaviors and templates, export HTML / SVG / JS, and load the package in Mingcedar. The plugin authors screens; the host supplies data and controls access. PowerPoint native animation and presentation playback are outside the exported behavior contract.</p>

<p class="doc-step-result"><strong>Expected result</strong> Identify the authoring environment, runtime requirements and required features before starting a project.</p>

<li><a href="/en/ppt/manual/foundation/">Responsibilities and environment</a></li>

<li><a href="/en/ppt/manual/capability-reference/">Capability and method reference</a></li>

<li><a href="/en/ppt/manual/export-and-publish-screen-package/">Export and delivery scope</a></li>

</ul>

</article>

<h3 id="learning-paths-item-2">First-time user: author and publish a screen</h3>

<p>Create a screen with page variables, name components, bind behaviors, then export and publish. No PLC is needed; publishing and runtime checks require Mingcedar.</p>

<p class="doc-step-result"><strong>Expected result</strong> Two buttons switch the indicator and text; reloading restores the initial state. Then proceed to live Tag displays.</p>

<li><a href="/en/ppt/manual/windows-install/">Installation and licensing</a></li>

<li><a href="/en/ppt/manual/first-screen/">Create your first screen</a></li>

<li><a href="/en/ppt/manual/text-tag-text/">Connect a live Tag</a></li>

</ul>

</article>

<h3 id="learning-paths-item-3">Experienced author: reuse without mixing parameter types</h3>

<p>Use template placeholders for design-time differences, runtime variables for current-page state, and page parameters for navigation context. A Tag-name string is an address; reading it and writing to it are separate operations.</p>

<p class="doc-table-hint">Scroll horizontally to view the full table</p>

<thead><tr><th scope="col">Need</th><th scope="col">Mechanism</th><th scope="col">When it takes effect</th></tr></thead><tbody>

<tr><th scope="row">Reuse the same pump for PUMP01 / PUMP02</th><td><PLC> / <DEVICE> template fields</td><td>Configure each template instance before export</td></tr>

<tr><th scope="row">Switch a target while the page stays open</th><td>Page Script variable and a supported expression field</td><td>Runtime evaluation</td></tr>

<tr><th scope="row">Open details for the selected device</th><td>Navigation parameters and GetPageParameter</td><td>Destination page opens</td></tr>

<tr><th scope="row">Show a filtered table</th><td>Page Script function returning an array</td><td>Table data evaluation</td></tr>

</tbody></table></div>

<p class="doc-step-result"><strong>Expected result</strong> Two instances use different targets, and a parameterized page accepts only the intended devices.</p>

<li><a href="/en/ppt/manual/design-reuse-guide/">Choose a reuse and parameter method</a></li>

<li><a href="/en/ppt/manual/recipe-template-bit-write/">Template bit-write recipe</a></li>

<li><a href="/en/ppt/manual/recipe-page-parameter-input/">Parameter-driven Input</a></li>

<li><a href="/en/ppt/manual/recipe-parameterized-table/">Parameterized Table</a></li>

<li><a href="/en/ppt/manual/recipe-popup-selection/">Select in a popup and return a result</a></li>

</ul>

</article>

<h3 id="learning-paths-item-4">Developer: check scope, contracts, and failure paths</h3>

<p>Page Script is shared within one page; Setup Script prepares one behavior’s values. Expressions must return immediately. Declare every candidate dynamic Tag name for export; host permissions and confirmation still apply.</p>

<ul>

<li>Verify missing parameters, unrecognized devices, bad quality, target switching, and denied writes.</li>

<li>Saving in the editor, passing export validation, and completing a host write are three different checkpoints.</li>

<li>Use the custom-page SDK when a purpose-built application needs capabilities beyond the built-in templates.</li>

</ul>

<li><a href="/en/ppt/manual/script-scope-and-parameter-passing/">Script scope and parameters</a></li>

<li><a href="/en/ppt/manual/capability-reference/">Runtime methods and limits</a></li>

<li><a href="/en/hqserver/manual/custom-page-tutorial/">Custom-page SDK tutorial</a></li>

</ul>

</article>

</div>