David's suggestion came to light in response to the following warning in Servoy 6:
- Code: Select all
For performance reasons on the internet/WAN it is strongly suggested to place no more then 3 portals/tab panels on a form.
For performance reasons on the internet/WAN it is strongly suggested to place no more then 20 fields on a table view form.
david wrote:It seems to me that if you are going to get into the business of counting things and throwing up warnings, why not flag known offenders? Calcs, blobs, html/rtf fields, and related value lists in a table for starters.
Better yet, have a feature that highlights all the objects on a form with a color representing their render speed potential -- green, yellow and red. In a table of 40 columns, you'd instantly see which columns are most likely to cause speed issues.
Along the same lines, I'd love to see the performance page of Servoy server (which is brilliant) as a view in Servoy developer. Sort of like the profiler view except you see the queries that are generated for the interface showing. Clicking on an item takes you to the object that generates the SQL. This would save a lot of time as matching up performance page items to what is generating the SQL can be tedious.
I really like the idea of flagging performance issues. I just think that if you're trying to help newbie developers out (and we all have our newbie moments) -- I think it requires better solutions than generic warnings.
These are excellent suggestions from David. What do you think?
My vote: + 1
JC