Differences

This shows you the differences between two versions of the page.

--- mistudio:getting_started:project_structure [2026/06/20 13:29] – [Overview] tputman
+++ mistudio:getting_started:project_structure [2026/09/18 15:54] (current) – tputman
@@ Line 1: / Line 1: @@
 ===== MIStudio Project Structure =====
-This page explains the basic structure of a MIStudio project.
+This page explains the basic structure shown in the MIStudio project tree.
 ==== Overview ====
-MIStudio uses projects and applications to organize screens, graphics, data connections, and system behavior.
+MIStudio uses a project tree to organize the main parts of a project. The project tree helps users find project files, images, drivers, targets, components, and applications.
-Understanding these basic terms makes it easier to navigate MIStudio and understand how an application is organized.
+Understanding the project tree makes it easier to navigate MIStudio and understand where project resources are organized.
-{{:mistudio:getting_started:pasted:20260620-132347.png?300|MIStudio project tree showing project structure}}
+{{:mistudio:getting_started:pasted:20260620-133654.png?800|MIStudio project tree showing project structure}}
 //MIStudio project tree showing common project sections such as User Files, Images, Drivers, Targets, Components, and Applications.//
@@ Line 15: / Line 15: @@
 ==== Project ====
-A project is the main container for a MIStudio system.
+A project is the main container for an MIStudio system.
-A project can hold one or more applications, along with the graphics, logic, data connections, scripts, and configuration needed for the system to run.
+In the project tree, the project appears at the top level. The sections under the project organize the files, resources, configuration, components, and applications used by the project.
-For example, a project might represent a dashboard system, a tool interface, a production monitoring application, or another industrial user interface.
+==== User Files ====
-==== Application ====
+The User Files section is used to organize project-related files that are included with or used by the project.
-An application is a workspace inside a project.
+These files may support the project but are separate from the main application screens.
-Applications are often used to organize different screens or parts of a system. For example, one application might show a main dashboard, while another application might show detailed equipment status, charts, alarms, or controls.
+==== Images ====
-==== Graphics ====
+The Images section is used to organize image resources for the project.
-Graphics are the visual parts of a MIStudio application.
+Images can be used by graphics, buttons, displays, or other visual parts of an application when supported by the selected graphic.
-Graphics may include labels, boxes, indicators, meters, charts, buttons, images, and other display components. These graphics are used to build the screens that users see and interact with.
+==== Drivers ====
-==== Data Connections ====
+The Drivers section is used to organize driver-related project configuration.
-MIStudio applications can connect graphics to data sources.
+Drivers are part of how an MIStudio project can communicate with external systems or data sources, depending on the project setup.
-When data changes, connected graphics can update automatically. For example, a value from a machine, database, server, or simulated data source can update a display, indicator, chart, or control.
+==== Targets ====
-==== Logic ====
+The Targets section is used to organize deployment or runtime targets for the project.
-Logic defines how parts of the application work together.
+Targets help define where or how the project may be deployed or run, depending on the system configuration.
-Logic can be used to move data, respond to user actions, process values, or connect one part of the system to another.
+==== Components ====
+The Components section is used to organize reusable project components.
+Components can help organize project pieces that may be reused or managed separately from a single application screen.
+==== Applications ====
+The Applications section contains the applications inside the project.
+An application is where screens, graphics, controls, and related application behavior are built. A project may contain one application or multiple applications, depending on how the system is organized.
+Visual content is created in the [[mistudio:design_editor:start|MIStudio Design Editor]], while data sources, connections, and application logic can be configured in the [[mistudio:logic_editor:start|MIStudio Logic Editor]].
 ==== How Users Experience the Structure ====
-In MIStudio, users usually interact with an application visually. They may open MIStudio from an icon, view dashboards, watch live values update, click controls, or move between screens.
+Users usually work inside a project by opening applications and working with the graphics, controls, displays, data sources, and logic inside those applications.
-The project and application structure works behind the scenes to organize those displays and connections.
+The project tree organizes the supporting parts of the project so users can find resources, applications, and configuration sections more easily.
 ==== Getting Started Flow ====
@@ Line 64: / Line 76: @@
   * [[mistudio:getting_started:create_project|Creating a Project]]
   * [[mistudio:getting_started:create_application|Creating an Application]]
-  * [[mistudio:graphics:start|MIStudio Graphics]]
+  * [[mistudio:design_editor:start|MIStudio Design Editor]]
+  * [[mistudio:logic_editor:start|MIStudio Logic Editor]]