Hi Reuben,
we could imagine the following:
if the Folder gets minimumWidth/minimumHeight attributes, then this could be the
indicator for the VM to not send initially all pages (or another explicit flag).But the GDC needs at least an idea how large the biggest page of the folder is,otherwise clicking on several pages will lead to a resize of the form.
We really see a need of this technique because some customers blow the whole client with "monster forms"..In good ol' 4GL days one could open a sub window in the same current window and hence display the information only when needed.
I believe we need something similar for genero, this could be done in the overhaul of the multiple dialogs in direction master/detail forms (the ability to merge a separate detail .per form into a master form at run time via place holders in the master form, this would also prevent 1 big all in one monster form). However nothing has been decided yet.
Having the flag for the VM to prevent sending all pages including minimumWidth/
minimumHeight seems faster doable but also has not been discussed in detail here.
Kind Regards, Leo
Leo,
Thanks, I was thinking along the lines of specifying HEIGHT,WIDTH for a FOLDER, and if the page contents exceed specified height, width then the contents of a page are displayed inside scrollbars. Similar to how a form can be rendered if it is bigger than the screen. I suppose it depends upon which is the lesser evil, scrollbars inside a folder page versus form resizing.
The other place I have seen for potential performance improvement is if something is hidden. In that case I would've thought most of the info would not need to be sent to the GDC. I tried to improve the folder/page performance by hiding the parent VBOX layout container of each page, and unhiding it when the page was selected but still the data of each page was sent to the GDC.
Reuben