Member Avatar for Rafael

Web languages — HTML, CSS and JavaSscript are the best choice for kids and for amateur programmers, because they are very simple, and with them you can create many interesting things: sites, mobile and desktop applications, web servers and robotics — what else an amateur programmer needs for happiness?

Visual programming!

Visual programming frees programmer from monitoring correctness of syntax program syntax, it is useful at beginning of training. This is the next stage in development of text-based programming languages.

And programming on the touch screen!

I suggest using the touch screen to create applications. You can create applications on the tablet, for example, lying on couch, or walking in park. I developed a new way of working with text on a touch screen, based on Flexbox.

But in the usual web programming there are two problems:

1) Web languages have a many of unnecessary features. To create real good programs you do not need to know these languages completely. In the beginning you can master core, the basic features. The rest you can learn later or never use.

2) In the professional web industry, besides knowledge of these languages, you need to know many other tools. To learn them you need to spend a many of time and effort. But kids do not need these complex tools, they need simplicity. The amateur programmer does not need to conform to industry standards.

We must clearly understand the beauty of web languages. The programming tool can be and should be simple.

Let's distinguish three areas of programming:
1) professional industry — complex standard tools and stress
2) teaching kids, at school or alone — minimum of stress and complexity
3) amateur programming — creating necessary programs for yourself

The second and third group of programmers can use one simple tool that I propose. Programmers from the first group may not understand the meaning.

Based on HTML, CSS and JavaSscript languages, I developed three visual programming languages for kids, and for all amateur programmers (like me) who need minimal programming complexity. So simple was not yet there.

I redesigned web languages, cut off all unnecessary and allocated a core sufficient to create normal web applications.

See more:

Online visual code editor:

Video lessons:
https://www.youtube.com/channel/UCqi6Xn4TNWdplZwM2LmNeLA/videos

  • 2 Contributors
  • 1 Reply
  • 477 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by LearnTheNew

Dani AI

Generated

outlines a practical path: keep the web stack small, make a visual/touch editor, and preserve what matters for later learning. That approach works well when the goal is confidence and transferability. For hobbyists and school learners the editor should teach fundamentals, not hide them; for pros the editor should be a bridge, not a dead end. 's acknowledgement shows the idea resonates.

A suggested beginner "core" to expose in a simple tool: HTML structure (doctype, html, head, body, headings, p, links, images, forms); CSS essentials (box model, selectors, Flexbox, responsive units); JS basics (variables, functions, event listeners, querySelector, simple DOM updates like textContent, and console.log for debugging). Include semantic attributes and basic accessibility (labels, alt) from the start so habits form early.

Editor and touch-workflow ideas that scale from kids to amateurs: a block-orientated canvas that maps one-to-one to real HTML/CSS/JS, a property inspector for selected elements, live preview and a single-file export option, an easy toggle to view plain code, and robust undo/redo. Use Flexbox as the page-layout primitive inside the editor and make touch gestures reliable by using pointer events and disabling default touch behavior where needed. Small example (layout + touch hint):

<div class="row">
<div class="box">One</div>
<div class="box">Two</div>
<div class="box">Three</div>
</div>

<style>
.row { display:flex; gap:8px; touch-action:none; }
.box { flex:1; min-width:40px; padding:12px; background:#eee; }
</style>

Keep a few cautions visible: progressive disclosure is key — reveal complexity only when needed; avoid embedding eval or running untrusted code; and always provide a way to view the raw code so learners can transfer skills to standard tools. Designing for the three groups ('s professional / teaching / amateur split) means defaults for simplicity and optional advanced panels for growth.

Member Avatar for LearnTheNew

Thank to refering

Edited by happygeek because: fake sig deleted (again, and again...)
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.