I removed width and high as parameters, improved and shorten some actions.
I'm testing that application through LAN (so it's relatively fast).
If I have only Actions in initialization process:
First loading - 3,7s
Other loadings - 4,0s-5,0s
If I switch some all repetitive and time-taking Actions to Services in initialization process:
First loading - 3,8s
Other loadings - 4,0-5,5s
I think we can say there's no much difference.
If you could look at 'Browser Side' version (only Actions - no Services) that would be really helpful. Maybe there are some other tricks to save time:
Just for the record, below is attachment with Services:
Now some explanations:
In whole init process there are 5 main inits:
- SetMainDivWidth - it only sets the width of mainDiv <------- not important - the shortest action
- FillTHEAD - fills header of the table <----------- short as well - not important
- FillTBODY - fills Body of the Calendar <------ it takes a lot of time (about 11s-16,7s in DebugMode)
- InsertActiveBoundariesFromColumnStructure - It draws job activity lines (the navy blue ones) <---not so long comparing with others - 8,5s-11s
- InsertEventDivsFromColumnStructure - inserts eventDivs <-------- it's the biggest one - 29,20s-40s
I discovered that using 'Convert Number To Text' with format trigger is taking relatively a lot of time (about 7ms-14ms) - but cause of repetitive Actions it takes more and more time)
Other thing is that Style thing we discussed.
I think that would be good improvement for Tersus if HTML elements could have <Style> attribute but not as Text like now, but as Data Structure. Then developer could add Text DataTypes like <width> <height> etc.to that Structure - then whole structure would be mapped straight to CSS - then there's no need to use many Concatenations with ';' or 'Set Style Attribute' like I do now for changing elements.
For best results, use the Firefox browser..