TABLE OF CONTENTS 1. PLANNER-VIEW 1. 2. PARTIAL PLANS THAT WE COMBINE 2. 3. CREATING A JOINT PLAN 3. 3.1 COPYING PARTIAL (*.TXT) PLANS TO THE TXT_IN SUBDIRECTORY 3.1 3.2 MERGER INTO A JOINT FILE 3.2 3.3 CREATING A FUNCTIONAL PLAN WITH TXT-PLANNER 3.3 4. SUPPLEMENTING THE OVERALL PLAN 4. 5. DATA SECURITY AND PROTECTION OF USER PRIVACY 5.
Date of last change (yyyy-mm-dd): 2025.09.26 1. PLANNER-VIEW The program enables logical grouping of partial (*.txt) plans, which must have the same activity structure at least at the first (1.st) level of naming and placing activities. In cases where a large number of organizational units participate in the planning of a larger task or project, the linear composition of partial plans is not sufficient. The program combines chapters that have the same designation in the partial plans at the first (1.st) level, i.e. they are comparable at this level. Therefore, the participating organizational units must respect the initially intended structure of the plan. 2. PARTIAL PLANS THAT WE COMBINE Partial plans are usually created with the TXT-PLANNER program, but this is not necessary. To ensure transparency, organizational units must select the option when using the TXT-PLANNER program to have the program add the designation of the organizational unit that owns the partial plan to the chapters. Partial plans that were created with the TXT-PLANNER program and are intended for merging with the PLANNER-VIEW program, may not contain: - TOC (table of contents); - calendar; - index. The PLANNER-VIEW program creates a common file, which is essentially a structured composite: - key components are marked on the first (1.st) level and are present in all partial plans; - contributions from organizational units are included on the second and other levels. The program builds a structured common file by merging identically marked chapters of the first (1st) level from the partial plans of the organizational units. The common file is only the basis of the common plan in the *.TXT format. The common file of partial plans is not yet a working common plan, because it does not have a calendar and bidirectional links between activities and the calendar. Only re-using the TXT-PLANNER program by adding a calendar transforms the common file into a working whole. It makes sense that the common plan is also indexed. 3. CREATING A JOINT PLAN 3.1 COPYING PARTIAL (*.TXT) PLANS TO THE TXT_IN SUBDIRECTORY Program PLANNER-VIEW combines partial plans collected in the TXT_IN subdirectory in a structured way. As tasks become more complex, users often add internal references to their plans. References (internal look_at: links) are omitted in the joint file due to the complexity of renumbering chapters. As demo files, we have chosen two index.txt files that describe the operation of two of our programs. Thus, we have provided multi-level numbering of chapters and an appropriate amount of text to realistically illustrate the operation of the program. So that the content of both files does not bother you, we suggest that you focus on structuring (numbering) the chapters and reviewing them using the index of all words. Demo input files: plan_01.txt: http://www.txt-utilities.com/txt-planner/planner-view/demo/txt_in/plan_01.txt plan_02.txt: http://www.txt-utilities.com/txt-planner/planner-view/demo/txt_in/plan_02.txt 3.2 MERGER INTO A JOINT FILE The program simultaneously creates a structured output file in four versions: - *.TXT file; - *.HTM file without index; - *.HTM file with index (optional); - *.CSV file intended for use in a spreadsheet. When merging into a common file, only numbered chapters are copied from partial plans. All output files are marked with the date and time of creation in their names. Indexing of *.HTM files is optional and is performed by the external subroutine htm_ndx_*.exe. The indexed file is accessible in the HTM_NDX\HTM_OUT subdirectory. The appearance of the file will not change due to indexing, and the index of all words is accessible by double-clicking on any word. Demo *.txt file, which will be used in the TXT-PLANNER program: http://www.txt-utilities.com/txt-planner/planner-view/demo/plan_view_2025_09_25_19_59_29.txt Demo *.htm file without index: http://www.txt-utilities.com/txt-planner/planner-view/demo/plan_view_2025_09_25_19_59_29.htm Demo *.htm file with index: http://www.txt-utilities.com/txt-planner/planner-view/demo/htm_ndx_01/htm_out/page_02.htm PROGRAM PLANNER-VIEW: http://www.txt-utilities.com/txt-planner/planner-view/planner-view.7z 3.3 CREATING A FUNCTIONAL PLAN WITH TXT-PLANNER For full functionality of the joint (*.txt) file in the TXT-PLANNER program, we select two options: - adding a calendar; - indexing. Demo of the indexed joint plan: http://www.txt-utilities.com/txt-planner/planner-view/demo/htm_ndx_02/htm_out/page_02.htm 4. SUPPLEMENTING THE OVERALL PLAN Minor changes and additions are edited in the input files (partial plans), which are in the TXT_IN subdirectory. The structure (numbering) of all chapters must remain unchanged. In the case of major changes, the partial plans must be reprocessed. The structure of the chapters on the first (1.st) level must remain unchanged, and the numbering of the remaining chapters is determined by program. The procedure is essentially a repetition of the entire process for creating a comprehensive plan: - copying partial (*.txt) plan without TOC and without index into TXT_IN subdirectory; - run program PLANNER-VIEW, without index; - run program TXT-PLANNER with calendar and index. The indexed file is accessible in the HTM_NDX\HTM_OUT subdirectory. The index of all words is accessible by double-clicking on any word in *.HTM file. 5. DATA SECURITY AND PROTECTION OF USER PRIVACY The program does nothing that could compromise data security and user privacy.
This document was structured using the TXT-INDENT program.
More info: www.utilities4promoting.com