Cache styles on smart client with application.overrideStyle
Posted: Wed Apr 22, 2009 2:18 pm
Case #207702.
Servoy does not cache styles on smart client when using application.overrideStyle().
We're not exactly sure the order of events, but the following seems to make sense:
1- We issue an application.overrideStyle('_FRAMEWORKS_','fw_MAC_leopard') command for whatever OS the client is running on at startup.
2- Servoy remembers that override
3- When a new form is loaded, Servoy overrides the style...but
4- It does this on the client
So everytime a new form is navigated to, the whole style file is pushed down to the client afresh (it is NOT cached at the client like a browser will do).
Our style average about 20k. So for each form viewed, that is 20k over the wire. Throw in a typical screen like a CRM with 3-5 forms in tab panels and we're at 100k. This produces a significant data transfer spike the first time the screen is loaded.
Servoy does not cache styles on smart client when using application.overrideStyle().
We're not exactly sure the order of events, but the following seems to make sense:
1- We issue an application.overrideStyle('_FRAMEWORKS_','fw_MAC_leopard') command for whatever OS the client is running on at startup.
2- Servoy remembers that override
3- When a new form is loaded, Servoy overrides the style...but
4- It does this on the client
So everytime a new form is navigated to, the whole style file is pushed down to the client afresh (it is NOT cached at the client like a browser will do).
Our style average about 20k. So for each form viewed, that is 20k over the wire. Throw in a typical screen like a CRM with 3-5 forms in tab panels and we're at 100k. This produces a significant data transfer spike the first time the screen is loaded.