I need to mock up a few dozen screens without a database behind them. In the next stage there will be data, so I don't want to waste time by doing temporary work.
Eventually groups of forms/ screens will common fields which I would store in a DB, The rest of the field would be different and I am considering storing them as json.
My preference would be to use a json structure to populate the mockup.
Any suggestions on doing the mockup screens, but retaining the effort put in, for later reuse?
I'm not sure how to understand your question.
You search for a mockup tool that somehow integrates or can output to TMS WEB Core forms?
As far as I know, such mockup tool does not exist
I wasnt looking for a tool. I was looking for hint, based on how your components work. I can create the json structure for instance with the data I need.
Can I assign this to edit controls such as editboxes, checkboxes and dropdowns?
Can I easily fetch data later from the server in a json format?
For VCl for instance, I could just a use a clientdataset and store the mockup data to a file, to be replaced by a datasource later on.
How visual data-binding works now, is your REST endpoints returning JSON arrays of records and load these array of objects into a TWebClientDataSet. There it becomes a dataset of fields of these records and you can bind this TWebClientDataSet to a DB-control via a TWebDataSource (similar as you would do in a VCL application)