I probably didn’t explain this very well.
Here’s an example: I’ve developed some software for a number of years (not using any web technology) where users need to create layouts/templates where they can select whatever fields they want and choose the fonts, format, styling, as well as currency and language etc. These templates are used to create lists and catalogues etc. In this situation it makes sense to store both the data and the templates in a database. I’m interested in a corresponding solution in Wappler.
I can do exactly what I want by inserting the template string using PHP - so it doesn’t make any difference to the client-side performance. I don’t see why it should necessarily make any difference performance-wise anyway, as you’re suggesting, even if it were possible to do this using Wappler/App Connect. The list of bindings will be evaluated in either case - whether they are hard-coded in the page (or at least by the time the page arrives on the client) or not. I suppose there would be an extra step as the string is retrieved from the database but after that, I wouldn’t have thought there would be much difference.
As I mentioned in another thread, it might be a little like using dmx-html
to tell Wappler to parse embedded HTML tags in the data. I haven’t noticed any performance issue when using this attribute. I have no idea if this would be very difficult to implement or perhaps something that would be quite simple - and can perhaps already be done.