1

Topic: The object about itself knows not everything, but owes itself .

There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. And the variable does not know and should not know about itself - input it parameter or the day off. But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant.

2

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant. The code  separately, algorithm - separately. Under the column of algorithm to build the graph of visual components, at creation to palm off the necessary parameters .

3

Re: The object about itself knows not everything, but owes itself .

Hello, Sinix, you wrote: S> the Code  separately, algorithm - separately. Under the column of algorithm to build the graph of visual components, at creation to palm off the necessary parameters . To get in variables flags ? So it also was to be avoided. To hang a separate class-otrisovyvatel? Ugly somehow.

4

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: S>> the Code  separately, algorithm - separately. Under the column of algorithm to build the graph of visual components, at creation to palm off the necessary parameters . SO> to Get in variables flags ? So it also was to be avoided. To hang a separate class-otrisovyvatel? Ugly somehow. Just here all is beautiful, though implementation will be more difficult. Present, it is necessary if to draw in different cases on a miscellaneous? You will push a heap of functions of drawing in a class dataful? I would look towards the unloved Visitor.

5

Re: The object about itself knows not everything, but owes itself .

Hello, V. Zudin, you wrote: SVZ> Just here all is beautiful, though implementation will be more difficult. SVZ> present, it is necessary if to draw in different cases on a miscellaneous? You will push a heap of functions of drawing in a class dataful? I now also have a sharing - the data and visualizers. More precisely even 4 classes at me. The class  (purely given), a class of the graph (purely given) - works with classes  and  in between, a class   and a class  the column. And so input  or output - it is stored only in a class of the graph. And it is correct. And the class   does not know about a class of the graph, he knows only about a class .

6

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> to Hang a separate class-otrisovyvatel? Ugly somehow. From the graph of the data which know nothing about  to receive the graph labeled . The information for  SO> it is ugly somehow. Well and what else variants? Not, it is possible to bypass each time the graph and to recover the information in the course of bypass, but for frequent update it is exact not

7

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: Visiter

8

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> I now also have a sharing - the data and visualizers. More precisely even 4 classes at me. The class  (purely given), a class of the graph (purely given) - works with classes  and  in between, a class   and a class  the column. And so input  or output - it is stored only in a class of the graph. And it is correct. And the class   does not know about a class of the graph, he knows only about a class . Then still variants: or to get different types of nodes for input / output variables, or to add in  knowledge of inputs / node outputs.

9

Re: The object about itself knows not everything, but owes itself .

Hello, Sinix, you wrote: S> Then still variants: or to get different types of nodes for input / output variables, or to add in  knowledge of inputs / node outputs. The question, actually, was not how to make that worked, because it not a problem. And how to make that  Something the variant with a flag for the draughtsman is not pleasant to me, but to see there are no variants. And if in all draughtsmen to push through the pointer on the graph, and in the column  the method which is spoken about type  by it is more beautiful?

10

Re: The object about itself knows not everything, but owes itself .

Hello, Sinix, you wrote: SO>>... And so input  or output - it is stored only in a class of the graph. And it is correct. And the class   does not know about a class of the graph, he knows only about a class . S> Then still variants: or to get different types of nodes for input / output variables, or to add in  knowledge of inputs / node outputs. Last it seems to me the most convenient. Someone initializes and launches , it is logical during this moment and to impart additional knowledge.

11

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: S>> Then still variants: or to get different types of nodes for input / output variables, or to add in  knowledge of inputs / node outputs. SO> and if in all draughtsmen to push through the pointer on the graph, and in the column  the method which is spoken about type  by it is more beautiful? I would push through the pointer not on the graph, and on " type " (which in combination can be the graph).

12

Re: The object about itself knows not everything, but owes itself .

Hello, V. Zudin, you wrote: SVZ> I would push through the pointer not on the graph, and on " type " (which in combination can be the graph). , and what for to manufacture it in the separate interface? Like it any more will not have successors, only the graph knows such things.

13

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SVZ>> I would push through the pointer not on the graph, and on " type " (which in combination can be the graph). SO> Hmm, and what for to manufacture it in the separate interface? Like it any more will not have successors, only the graph knows such things. Dependences to reduce. And everyone happens, suddenly it is required to take types  (and, probably, not only them) from other source. But it so, reinsurance. Personally this variant is pleasant to me most.

14

Re: The object about itself knows not everything, but owes itself .

Hello, V. Zudin, you wrote: SVZ> Personally this variant is pleasant to me most. Yes, perhaps, too it is pleasant to me. At least allows to avoid flags in , I do not love such flags-patches.

15

Re: The object about itself knows not everything, but owes itself .

SO> There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. And the variable does not know and should not know about itself - input it parameter or the day off. But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant.  you ( itself) parameter, instead of a variable. And the parameter already knows, input it, or the day off. By the way, it is very probable that at any stage it wants to separate model (Parameter) from its graphic representation (ParameterImage). Such MVVM, but not for the sake of , and on-business

16

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. And the variable does not know and should not know about itself - input it parameter or the day off. But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant. At first  in the graph, then the graph  in a picture. Not clearly, what for a variable itself . A MB in runtime simply to write  to a certain broad gull which then to transform to the graph?

17

Re: The object about itself knows not everything, but owes itself .

Hello, Ikemefula, you wrote: I> it is not clear, what for a variable itself . You offer the column the nobility what  as to yourself ?

18

Re: The object about itself knows not everything, but owes itself .

19

Re: The object about itself knows not everything, but owes itself .

Hello, kov_serg, you wrote: _> Make at a variable an input and an output. And the box with N inputs and M outputs is better. Funny, on my visualization I think all understand at once, where input, where days off. To understand your circuit, it is necessary to think long. Generally, I think developers UnrealEngine thought of convenience and . I repeat them Blueprint for own needs

20

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. And the variable does not know and should not know about itself - input it parameter or the day off. But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant. In clever and not so books was type such GRAPS pattern Informational Expert - duties to arrange to who has data for their performance. It to a word. I would solve your task differently. Any classes-draughtsmen which on an input receive a nodu/arch dataful. It is possible to develop/find component VectorDraw which draws group of primitives on a surface. The browser with svg a drawing the good candidate. I.e. I twist let will be declarative (a dial-up of the primitives fixed for ), instead of imperative (procedure which received  and drew it with the help gdi). At creation of your variables that who creates them, he creates a dial-up of primitives for visualization of a variable and fixes them to this variable. This creator allocates the graph and generally all. There will be at you classes variables/algorithms which know nothing about visualization, even the plane coordinates (if it is finite these coordinates are not necessary for the main algorithm). Also there will be aside groups of graphic primitives with links to your variables/algorithms on id. Will draw primitives VectorDraw.

21

Re: The object about itself knows not everything, but owes itself .

Hello, sr_dev, you wrote: _> At creation of your variables that who creates them, he creates a dial-up of primitives for visualization of a variable and fixes them to this variable. This creator allocates the graph and generally all. Such approach is bad, if it wants, for example,  system of the extension of functionality of this graph.  in plug-ins know and as  itself and what exactly  do. If visualization  any designer, then collects a step to the left, a step to the right - execution. It will be impossible to set any absolutely non-standard .

22

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. Here you lose the information on argument type considering it as simply variable. SO> and the variable does not know and should not know about itself - input it parameter or the day off. Really, the variable does not have direction, and at argument is. SO> but. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? To add a flag in   - not a variant.  from a class of a variable an argument class which will have a direction and draw arguments, having the full information. The function code  like should not exchange.

23

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> Hello, kov_serg, you wrote: _>> Make at a variable an input and an output. And the box with N inputs and M outputs is better. SO> it is amusing, on my visualization I think all understand at once, where input, where days off. To understand your circuit, it is necessary to think long. SO> generally, I think developers UnrealEngine thought of convenience and . I repeat them Blueprint for own needs I understood, you  to it

24

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: I>> it is not clear, what for a variable itself . SO> you Offer the column the nobility what  as to yourself ?  the renderer is engaged. To it on an input the ready graph arrives. The renderer is able  everything that is necessary. The graph should contain the necessary information what to compare style of display and other things to each element. I of years of 5 columns drew, ask

25

Re: The object about itself knows not everything, but owes itself .

Hello, SergeyOsipov, you wrote: SO> There is a certain visualization of algorithm in a type of the graph. This algorithm is a function with input and output parameters. Any parameter is simply variable. And the variable does not know and should not know about itself - input it parameter or the day off. But. Any variable itself  in a type  the column. And so input and output parameters differently themselves  should, but they in themselves do not know input they or days off. How ? Is such  as SOLID. In particular Single Responsiblility Principle. Your complexities just from that you do God Object - you mix logic of the algorithm and . Accordingly you should have a function. Which generally does not know about any drawing, to it the logic is important. There is an essence - . To which you say that for variables that for parameters, but which  on algorithm.  the column - will be a special case, probably successor from what or the abstract class. And then you will have an algorithm separately, drawing of variables, parameters, the graph - too separately.