9fc302f2   
   From: marcov@stack.nl   
      
   On 2008-08-11, Jim Leonard  wrote:   
   > The code (TV not withstanding!) is very large, as it contains a lot of   
   > routines to detect various graphics cards, processors, and speeds.   
   > Since only 1% of these routines will ever get run on any one machine   
   > (e.g. the Pentium/CPUID routines never run if the CPU gets detected as   
   > a 386, etc.), they don't all need to go into memory at once, so I will   
   > definitely be using the overlay manager for those.  My concern is   
   > whether or not TV elements can also be overlaid.  I assume trying to   
   > overlay the mouse routines would be disastrous, as they are interrupt-   
   > driven, but is there anything else I should definitely NOT overlay?   
      
   I think core TV is pretty monolithical, but I guess in TP that's sub 100k.   
      
   Since anything popped up via a menu or key can probably be in an overlay,   
   you could overlay nearly anything you customize (custom dialogs, but e.g.   
   also non core TV widgets as the calculator).   
      
   Limiting the number of distinct widget types keeps memory down too.   
   (smartlinking). Avoid very complex widgets as file open and treeviews, which   
   are larger than the rest.   
      
   How to overlay the stuff you actually program depends on how it works. If   
   detections are guided by a series of dialogs, is different from just running   
   detections in batch and then presented in a result screen.   
      
   In the former case you bundle in each ovl the detections and the forms (e.g.   
   that make choices or provide intermediate results), and in the latter you   
   run the detections, and then load all custom dialogs in a presentation   
   dialog.   
      
   Note that IIRC, TV allows to stream dialogs to file, to avoid having to have   
   code in the binary to create dialogs. (with a lot of dialog, the streaming   
   code is way smaller than the dialog creations-in-code)   
      
   P.s. In case you _really_ need to use some memory, use a 64-bit FPC :-)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)