Interesting concept, like the fact you pushed further by going on a such complex example as a virtual keyboard! I think it really shows the potential.
Some thoughts coming to my mind: this could help JS framework that provide reactive DOM to easily express elements using a simple syntax. I tried once to play and create a home made reactive app, and it's a nightmare if you don't organize your in memory representation of the DOM elements, so maybe Webson can play a key role in it since reactive frameworks needs to keep track of changes (e.g. performing DOM diffing).
While walking the dog this morning (the time I get most of my best ideas) I was thinking about what you wrote. What you're suggesting is to shift the job of laying out a screen from code to markup - a low-code way of thinking. I think Webson would be quite good for that because of its modular block structure.
One thought led to another. My next project is likely to be a kind of IDE that allows a Webson script to be built in one panel (lots of menus and clickable choices) and the result instantly viewed in another. Again, the block structure makes this feasible as it's easier to avoid breaking the entire structure with a simple change. I'll do the acreen layout in Webson, of course, and the logic in EasyCoder, which has its own Webson plugin. This keeps my exposure to raw JavaScript to a minimum; a good thing since that's where most of the mistakes occur.
My best guess is this will take a few months, but it could be less. I'm retired so all this is a part-time hobby, which is far better than working to someone else's timescales.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting concept, like the fact you pushed further by going on a such complex example as a virtual keyboard! I think it really shows the potential.
Some thoughts coming to my mind: this could help JS framework that provide reactive DOM to easily express elements using a simple syntax. I tried once to play and create a home made reactive app, and it's a nightmare if you don't organize your in memory representation of the DOM elements, so maybe Webson can play a key role in it since reactive frameworks needs to keep track of changes (e.g. performing DOM diffing).
While walking the dog this morning (the time I get most of my best ideas) I was thinking about what you wrote. What you're suggesting is to shift the job of laying out a screen from code to markup - a low-code way of thinking. I think Webson would be quite good for that because of its modular block structure.
One thought led to another. My next project is likely to be a kind of IDE that allows a Webson script to be built in one panel (lots of menus and clickable choices) and the result instantly viewed in another. Again, the block structure makes this feasible as it's easier to avoid breaking the entire structure with a simple change. I'll do the acreen layout in Webson, of course, and the logic in EasyCoder, which has its own Webson plugin. This keeps my exposure to raw JavaScript to a minimum; a good thing since that's where most of the mistakes occur.
My best guess is this will take a few months, but it could be less. I'm retired so all this is a part-time hobby, which is far better than working to someone else's timescales.