Random thoughts in no particular order or validity

AngularJS has been rewritten. Should be thinking Angular?

I see Angular has dropped two way binding due to performance limitations. So maybe it's not
the best choice in my 
particular case.

I can see how it could work for a simple app.

To replicate an app with 100's of tables, loads of forms etc and maintain application logic
would surely require a 
comprehensive specification. If such a spec is not derived directly from the original code then
a huge manual effort 
would be required to create it. That sounds like a rewrite.

My question then is how to take a form spec and automagically convert it into a web form. What
does the form spec look 
like? Sounds like a forms API. So far I've attacked the reading of pdox form specs into classes.
Next step is to 
generate something to be loaded by code in the browser.

If one were starting from scratch with a new app it makes sense to build entirely in such a
framework as Angular, but 
that's not what I'm trying to achieve, but I can see there may be something useful there.

- Bernie

On 13/4/18 11:48 am, Larry DiGiovanni wrote:
> Bernie van't Hof wrote:
> 
>> No, just the UI part displaying tables and forms, capturing input.
>> The actual communications is immaterial, could be anything. (simple) Event driven interface
already there and working.
> 
> Last month, I was musing over the possibilities of simulating Paradox forms with AngularJS. 
You can bind an angular 
> Resource to a table via a REST API with just a few lines of Javascript (and the REST API).
> 
> So I could show you how to mimic basic navigation and data entry using angularjs data binding. 
But I don't think that 
> would translate directly when using Websockets, because AngularJS databinding is rooted
in HTTP methods 
> (PUT/GET/POST/DELE).
> 
> I'm certain that angular.io (or any of a number of other JS frameworks) can handle data
binding via Websockets, but I am 
> not familiar with that approach at present.
> 
> -- 
> Larry DiGiovanni
>