Should they make it so you can deploy on any framework you want...sure, that would be cool, but its not really why people choose Servoy....IMHO.
jcarlos wrote:#1. currently, there is a whole lot of demand for front-end design/production and a scarcity of resources, so you might have trouble finding good people who are free and available to help you build the front-end. Servoy takes that problem away -not to mention the cost to develop a front-end.
#2. David: the Velocity Report plugin/Velocity Web client can help you. Configure it, and you'll get just JSON objects that you can use. You did't need to wait for Servoy 8. Velocity can be your data proxy of Servoy's foundsets and records!
3 levels of headless client instantiation (per solution):
application (one headless client to rule them all!)
pool (just like the REST plugin, but much better!)
session (one headless client per HTTP session)
In session mode, your session is stateful
(Actually it can be stateful also in any mode...
juan.cristobo wrote:Are you planning to include sample webcomponents and sample NG solutions in the installer?
david wrote:
Servoy's code for this piece is here: https://github.com/Servoy/sablo. No license listed.
david wrote:It turns out that the core functionality is implemented agnostic to any client-side framework and NG Client just consumes the functionality with some not-so-elegant client-side code. It gets the job done but some API-esque wiring would help clean up this code.
david wrote:
Server-side Servoy forms function to set up a model/foundset. Form has a datasource, the fields you put on the form are the allowable data fields the client can see.
Form items provide additional meta information to the client such as data formatters, calculations, i18n keys, tagging, UI parameters, etc.
david wrote:Forms also provide services such as when a button is pushed, code on the server is run and a response is sent to the client.
david wrote:When an NG Client connects, a session is created and (all?) forms in your app have a state per session. Data broadcasting happens between sessions where the foundsets share the same visible foundset index(es). I assume all CRUD operations but edit is the only one I've tested so far.
david wrote:All of this communication goes back and forth from clients and server via websockets as JSON. If a field is edited, only the data for that field is sent over the wire, not the whole record. Quite compact for most operations from what I've seen (initial connection response sends a lot of unnecessary Angular stuff is one exception).
david wrote:If a solution requires login, websocket endpoints are not created until you login.
david wrote:
A neat trick is that you can return any JS object from a form method (serialization to JSON happens automatically) and the client websocket.onmessage handler picks it right up. So not only can you trigger foundset methods but you return your own data structures over the pipe. (Note to self, test sending arguments to form methods.)
jcompagner wrote:as an example this is a basic set of components that we made using bootstrap: https://github.com/Servoy/servoy-client ... components
Users browsing this forum: No registered users and 3 guests