Your comments suggest heavy use of client side, and you make it sound so simple!

The concept of client-side apps has gained momentum in recent years, but before that it was
difficult to achieve.

React, Angular, Blaze etc are (to an old bloke) all new (2013, 2010 and 2011 respectively),
react from Facebook and 
Angular from Google. When I started fiddling with this project about three years ago they were
not as well known as 
today. As far as I can tell they all suffer as app complexity increases, but then they are all
optimised for normal 
modern web design.

Have you actually built any apps using these technologies? How did you find them?

My original idea was to be largely server-side, which probably reflects my age more than anything
else. Hence the need 
for fast, asynchronous, bidirectional comms and stemming from that the choice of websocket,
itself a technology that was 
pretty unusable just a few years ago, but is now mature.

My original choice of php similarly reflects my age, knowledge and experience. In hindsight
it have been better to go 
javascript right from the beginning but for all the reasons above that did not happen.

So... back to the current issue. How to implement a client side UI, without throwing the entire
app to the client.

I don't see any magic bullets, so yes, I have my work cut out. But hey, it's all just a bit
of fun.

It would be nice to get some help on the js side though.

- Bernie

On 16/4/18 10:06 am, Larry DiGiovanni wrote:
> Bernie van't Hof wrote:
> 
>>  My question then is how to take a form spec and automagically convert it into a web
form.
> 
> What design pattern did you follow for your data persistence web service?
> 
> If you followed a standard design pattern (e.g., SOAP, REST, STOMP) then there is a Javascript
framework that supports 
> data binding against your service.
> 
> If not, then you might have your work cut out for you.  :-)
> 
> My Angular (1.6) recommendation was based on the observation that it is well suited to
code generation.  I suspect 
> Angular 2 is as well.
> 
> I don't know what web service patterns exist for Websockets.  Consequently I do not know
what Javascript data binding 
> frameworks would be of use.
> 
> -- 
> Larry DiGiovanni
>