fbpx

TechEditor Application Structure

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
 

Application is a mini-program that can be executed directly in the TechEditor environment. With the help of applications, you can solve various scientific, engineering, technical problems, and automate the output of text and formulas in reports.

Each TechEditor application consists of:

  • modules
  • program file

Application modules

A module is the main structural unit of an application.

An application can consist of one or more modules. The number of modules in the application is generally not limited. Each module is a separate file that can be reused, copied, moved, emailed, and more.

An example application named Application1 from three modules Unit1, Unit2, Unit3:

TechEditor Application IDE - 3 units

How to organize application modules

There is no single standard for organizing modules. The developer can place all the application code in one module or split the code into multiple modules. For relatively simple applications that perform simple tasks (for example, one or more actions), usually one module is sufficient.

For larger projects, including applications with a user interface (windows, buttons, checkboxes, etc.), it is recommended to split the application into separate modules. In this case, the application acquires algorithmic "harmony" and the logic of the relationship between the individual blocks of the program can be traced more clearly.

From the point of view of debugging (finding errors), the modular structure of the application is also more convenient than the option with a script in one file.

For example, if your task is to calculate the strength of a beam, then you can organize the structure of the modules as follows:

  • input module
  • module with calculation formulas
  • calculation results output module

Main application module

The main one is the module from which the program execution starts. All other modules of the application are called as needed, in accordance with the logic of the program.

Any application module can be set as the main one.

References between application modules

Application modules can refer to other modules.

References means that the module code referenced by the current module becomes available to the current module. It is an essential modular (structured) programming concept that allows you to design your application architecture more efficiently and effectively, avoiding code duplication.

For example, if your program defines functions for calculating bolted connections for repeated access to them from different parts of the program, then it is logical to move these functions into a separate module (for example, BOLTS). After that, in other modules, it is enough to provide a link to BOLTS and use the functions in full.

It is recommended to think over the connection between modules at the stage of application design.

An example of an application in which the Unit1 module refers to the Unit2, Unit3 modules:

TechEditor Application IDE - uses units

Cyclic links

The organization of reciprocal links between application modules should be considered carefully.

In programming, there are situations when a developer in the current module A needs to refer to module B, but module B already refers to A. Thus, the environment cannot establish the primary and secondary references.

Such situations, as a rule, indicate an incorrect program architecture and require the developer to revise the link logic. The solution may be to move resources (procedures, functions, global variables, etc.) into a separate, independent module C, which can be accessed by both module A and module B.

TechEditor automatically detects circular links in applications and signals this to the developer:

TechEditor Application IDE - circular references in units

Application structure

Application files

Application data is stored in text files. The following extensions are used:

  • .TECAPP — TechEditor Application File
  • .PSC — module file
  • .SFM — module form file

An example of Application1 application with Unit1 module and Unit2 form module, saved on disk:

TechEditor Application IDE - file structure example

Please note that two files of the same name are created to save the form: a module file (.PSC) and a file with a form description (.SFM). You will learn more about this from the relevant sections of the Guide.

Displaying an Application in a TechEditor Document

The TECAPP file is the main application file. The name of this file is displayed in the document tree:

TechEditor Application IDE - app file structure

Application modules do not appear in the document structure and open directly in the Application IDE as needed.

English forum

Simple calculator in TechEditor in 10 minutes!

Ontario Building Code 2012 | Load combination (Free Application & Report Template)

Videoreview version 1.0

New articles

Dystlab™ — Project for Engineers

Dystlab™ is a trademark registered in the State Register of Certificates of Ukraine for Goods and Services Marks 26.02.2018, certificate No. 238304. Owner: entepreneur Artomov V.E., EGRPOU/ITN: 3003314690.

E-mail:
technot needed texteditoranother not needed text@dystlabdummy text.store

Telegram:
https://t.me/techeditor

 

Legal information