|Subject:||Re: Qbe date parse results - final?
|Date:||Mon, 16 Apr 2018 22:32:02 -0400
|From:||"Larry DiGiovanni" <nospam@nospam>
stack, at least not easily.
You could modify your PHP code to follow a web services pattern. I suspect
frameworks that support data binding - at least via plug-ins.
I have built apps using AngularJS. I was dragged into it kicking and
screaming by my colleagues.
I like Angular, in that I can move lots of functionality to the server. But
the REST API is stuck in the request/response model. There may be plug-ins
for websocket support with AngularJS and Angular.io.
Angular does not directly handle type checking. If I pass in a 'customer'
type that has no 'address2' field, it'll consider address2 as null. I don't
like this. It also does not directly enforce domain constraints. If I pass
in 'employee.hireDate' as 'Fred', Angular is happy with that, unless the
code (or some widget) tries to use this as a Date. This sort of thing has
been a source of holy wars with said colleagues.
> My original choice of php similarly reflects my age, knowledge and
> experience. In hindsight it
> the reasons above that did not happen.
web service API in PHP, probably leveraging a lot of the code you already
> So... back to the current issue. How to implement a client side UI,
> without throwing the entire app to the client.
Not sure what you mean by 'throwing the entire app to the client'.
> It would be nice to get some help on the js side though.
have drop-in widget libraries that are independent of the framework. JQuery
is a treasure trove of widgets.
The original post in this sub-thread had more to do with my vision for
implementing strategies I am familiar with for application conversion. I am
still happy to help you pursue your vision if I can. I just don't have a
handle on an approach, at the moment.
because I do not like it.