Content deleted Content added
Christian75 (talk | contribs) Assessment: +Computing (assisted) |
KaptainFire (talk | contribs) →Data Flow versus Control Flow: new section |
||
Line 141:
3) The statement still needs to be cited. <small><span class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Ehosick|Ehosick]] ([[User talk:Ehosick|talk]] • [[Special:Contributions/Ehosick|contribs]]) 21:42, 15 April 2014 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
== Data Flow versus Control Flow ==
The article is of low quality and introduces a number of confusions. For instance, visualization is typically used to deal either with data flow or control flow. The article appears to be strongly biased towards data flow, completely leaving out control flow. This would be acceptable if it were not for the some of the examples. For instance, the top picture is about Scratch which is NOT a data flow visual language. I suggest to add some consistency using one of the following strategies:
1) remove picture to avoid inconsistency
2) replace picture with a control flow language picture, e.g., LabView
3) extend description to include data and control flow and provide two examples.
Also, one would expect a more detailed conceptual description of visual languages including some of the history which reaches far back, e.g., 1988. Visual Programming. N. C. Shu (Ed.). Van Nostrand Reinhold Co., New York, NY, USA.
|