Isn't that the place of update object??
Looking at the definition of the Refresh Object script step: Updates the content, conditional formatting, and visibility state for the specified object. I think update object actually updates HTML and CSS depending on the data changed. However from what I understood when reading the WebDirect manuals each time you load a layout, the web server re-generates all the HTML and CSS on the fly which would definitely cause page load delays. My point is that there should be no reason to re-generate HTML and CSS for a layout when that has not been changed. So would it be possible to store in a solution file a cache of HTML/CSS for each layout published in WebDirect?
Dimitris Valachis wrote:
this could cause performance issues on complex layouts
Complex layouts are going to be a performance issue across the platform (FMP, FM Go, WebDirect) and exposed more on slower connections and slower technologies (like Go, FMP WAN access, WebDirect). So I think the biggest benefit will come from spending time to make those layouts less complex...
Or you could understand if the on the fly generation of HTML and CSS causes a performance degradation in WebDirect and maybe address it by allowing for the caching of souce generated code. I am not saying that with WebDirect you should not take into account simplifying your layouts. Would you consider starter solution layouts as being complex?