configuration data 201 may be all provided at once or may be provided at different times during the custom view construction process in one embodiment the configuration data 201 is declarative the type of configuration data 201 might not be standardized but may differ according to the type of custom view to be generated there are a variety of view construction modules 202 that might each correspond to a particular custom view type there might be numerous view construction modules 202 available to the custom view generator 210 however in fig2 there are only four view construction modules 202 a 202 b 202 c and 202 d illustrated the ellipses 202 e represents however that there may be fewer than this number or more that this number u2014 perhaps many more referring to fig3 a view construction module 300 is schematically illustrated the view construction module 300 includes various parameters that might depend on the type of custom view that the view construction module 300 may correspond to in this specific example the view construction module 300 is illustrated as including five parameters 301 302 303 304 and 305 however the number of parameters may differ according to the custom view and according to the degree to which that custom view has been parameterized accordingly the ellipses 306 represents that there may be other types of views as well the parameters of the view construction module 300 may be populated by the configuration data 201 if the view construction module 300 is to be used to generate a custom view the logic 310 of the view construction module 300 may then be used with the various populated parameters as inputs to define underlying behavior of the view for instance if.