(translated by Google translator)
I added a new screenshot to my OneDrive (#08).
https://1drv.ms/f/s!AnoSlTzMqlL6jNo8-mr8...Q?e=Rv5dFf
The screenshot shows a tooltip that shows the value of the new "CodeBlockNumber" parameter that I created for each piece of SB code in the diagram.
It's very easy to create custom parameters for chart shapes.
To do this, you must select the shape and press "Ctrl + M" on the keyboard ( or select "Edit Data" in the "Edit" menu ).
Since the Diagram itself is an xml file and can be specially saved in xml format, our Utility will be able to find figures with SB code, copy the text of this code and collect it into one text file of the source code of the future SB program.
But the most valuable thing in this information is that THE DIAGRAM CAN BE ANYTHING
.
- It can contain code fragments written in any other programming languages.
- This could be a "Mind Map" Diagram, which contains fragments of Instructions for a person's future actions.
- This could be a Process Flow Diagram.
- This could be a project of a report, where the Diagram displays the logical sequence of the report, and hidden text fragments contain specific information for each section.
In all these cases, AFTER FINISHING the planning of the sequence of actions using the Diagram, we will receive at the output one finished document, which contains the text fragments specified in the Diagram, arranged in the sequence we need.
That's why I want to teach as many people as possible to use Diagrams to create Algorithms in Small Basic.
Because a person who knows how to use Diagrams to create an Algorithm for his future program will be able to create an Algorithm for his future actions
.
An action plan for achieving a complex goal created using a Diagram will inevitably be better than an action plan created simply in the mind.
This means that there will be more positive results. That is, at least a few people on the planet will become smarter.