[MahmoudFayed]

The design and programming concepts are related to programming, which is part of the software name Programming Without Coding Technology (PWCT). While coding involves writing textual code directly, Visual Programming Languages (VPLs) like Scratch and PWCT still require knowledge of programming concepts and problem-solving. However, they simplify the implementation process by reducing syntax errors and providing a graphical user interface (GUI) that can be in any human language. Visual components increase the level of abstraction, potentially reducing development time.

PWCT2 is influenced by:

1- Lava visual language - Using the TreeView

2- Forms/3 - Using the Data-Entry forms

3- Scratch - Blocks, Colors, and Translation

4- Visual Basic - Form Designer

5- Envision - Rich comments & Interactive Visualization

6- PWCT1

6.1 Graphical Code Replacement (GCR) method instead of drag and drop

6.2 PWCT1 - The Time Machine (Run programs in the past & Play programs as a movie)

PWCT2 introduces more features compared to PWCT1, such as importing Ring code, inserting steps, and more.

[smaudet]

> potentially reducing development time

See this is where this falls over.

Syntax highlighting + autocomplete already handle this, and where this actually works against your language, you have the problem every GUI has, inflexibility.

A "coding" language can evolve, structures change, be expressive or verbose. Much like a language.

I doubt your UI can benefit from these abilities, whereas an IDE already provides visual cues etc. that reduce this development time, while preserving the expressiveness of the language.

So, it probably does not reduce the development time, because the tools already solved this problem, and you just have a more clunky verbose, harder to develop language instead.

And the types that aren't coding in the first place are still going to struggle with things like edge cases, etc., so this isn't really democratizing anything either.