07-30-2024, 05:55 PM
(translated by Google translator)
Hi all.
Today I'm trying to use my OneDrive shared folder to display a large number of images.
If this is better than using a file hosting service, then tell me.
Here is the link: https://1drv.ms/f/s!AnoSlTzMqlL6jNo8-mr8...Q?e=Rv5dFf
In the first two images I want to demonstrate two ideas that make my charts different from other charts I see on the internet.
The first idea is to use containers.
A container allows you to place a list, another chart, text, or picture inside, and then collapse it into a small rectangle.
Therefore, the diagram may be smaller in size than the code text that the diagram represents.
The second idea is a RULE that determines the direction of information flow across the diagram.
According to this rule, information and events virtually move along the lines of the diagram.
Events exit from the icon of one object on the RIGHT and enter the icon of another object on the LEFT.
A line that enters an object from the left means calling a method of this object.
If an event occurs as a result of executing the method, the corresponding line comes out of the icon on the right.
The first screenshot shows three options for displaying properties and methods of objects.
The second screenshot shows a compact version of the diagram design. As you can see, methods and properties are hidden in collapsed containers, each of which can be expanded for detailed viewing.
Unfortunately, I haven't had time to do more yet.
But I'm trying.
Hi all.
Today I'm trying to use my OneDrive shared folder to display a large number of images.
If this is better than using a file hosting service, then tell me.
Here is the link: https://1drv.ms/f/s!AnoSlTzMqlL6jNo8-mr8...Q?e=Rv5dFf
In the first two images I want to demonstrate two ideas that make my charts different from other charts I see on the internet.
The first idea is to use containers.
A container allows you to place a list, another chart, text, or picture inside, and then collapse it into a small rectangle.
Therefore, the diagram may be smaller in size than the code text that the diagram represents.
The second idea is a RULE that determines the direction of information flow across the diagram.
According to this rule, information and events virtually move along the lines of the diagram.
Events exit from the icon of one object on the RIGHT and enter the icon of another object on the LEFT.
A line that enters an object from the left means calling a method of this object.
If an event occurs as a result of executing the method, the corresponding line comes out of the icon on the right.
The first screenshot shows three options for displaying properties and methods of objects.
The second screenshot shows a compact version of the diagram design. As you can see, methods and properties are hidden in collapsed containers, each of which can be expanded for detailed viewing.
Unfortunately, I haven't had time to do more yet.
But I'm trying.