Page scripts, SDK and Python | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="script-layers">User guide: Page scripts, SDK and Python</h2>

Choose an interface by runtime location and data needs.

<div class="doc-card-list doc-tutorial">

<article class="doc-card">

<h3 id="script-layers-item-1">Page JavaScript</h3>

<p>Runs with the browser page to handle layout, interaction and presentation.</p>

<ol>

<li>Publish scripts and assets with the screen package. Page closure or navigation ends that page script’s lifecycle.</li>

<li>Use the page SDK and declare the required Tags and alarm scope when accessing host data.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="script-layers-item-2">Custom page SDK</h3>

<p>Provides authorized runtime values, writes, history, alarms, language and navigation to custom pages.</p>

<ol>

<li>Open the published page through a host menu and connect using the official SDK.</li>

<li>Declare read and write Tags. Writes also depend on current user permissions and target Tag settings.</li>

<li>See the SDK tutorial and API reference for methods, events and error handling.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="script-layers-item-3">Host Python</h3>

<p>Runs project logic through the Script service independently of an open operator browser.</p>

<ol>

<li>Manage files in Code, configure actions and events in Run, and inspect execution results in Records.</li>

<li>Manage project dependencies and custom shared packages in Settings → Python. Use third-party libraries through their native APIs.</li>

<li>Access Tags through hqcontrol.tags within the project’s scope and permissions.</li>

</ol>

</article>

</div>

</div>